Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: The Scrum Master's AI Prompt Library, with Joshua McDonald
In this BONUS episode, Joshua McDonald shares how he uses AI in the daily work of a Scrum Master, from team summaries and leadership updates to retrospectives and coaching preparation. The conversation is practical and grounded in one clear warning: AI can give Scrum Masters time back, but it cannot replace their judgment.
When AI Stops Being a Toy and Starts Saving Real Time
"It would have to be when it started to save me about one to two hours per day."
 
Joshua's turning point came when AI moved from curiosity to practical assistant. He began using tools like Microsoft Copilot to analyze reports, prepare communication, and package updates for different audiences. The value was not that AI did the thinking for him. The value was that it helped him reach useful coaching conversations faster, especially when working with reports on predictability, volatility, and cycle time.
Turning Flow Data Into Better Coaching Conversations
"It was able to pinpoint where the bottlenecks were, and where I should look."
 
One of Joshua's first high-value AI workflows combined screenshots of team metrics with exported Jira stories. Instead of spending half a day scanning acceptance criteria, transitions, and bottlenecks, he used AI to identify patterns and suggest where to look next. From there, he would ask follow-up questions from the perspective of a Scrum Master, using AI as a sparring partner to prepare coaching talking points before speaking with the team.
AI as a Communication Coach, Not a Replacement for Judgment
"I like to use AI as my coach to help me in my communication style."
 
Joshua is careful with sensitive communication. When he needs to bring data, feedback, or a difficult pattern to an individual or team, he asks AI to help him test the wording. He might ask how a message could land with someone who has reacted defensively before, or request phrases to avoid. In that sense, AI becomes a preparation space: a place to roleplay, refine tone, and make sure the human conversation starts from care rather than accidental bluntness.
A Weekly AI Workflow for Scrum Masters
"I use it pretty much at everything I create."
 
Joshua's weekly rhythm includes AI-generated summaries from standups, backlog refinement, and retrospectives. He uses templates that identify who shared which updates, what action items emerged, and what the team should be able to review later. For retrospectives, he keeps a prompt library on a whiteboard, with prompts adapted for Scrum teams, Kanban teams, and team interests. A hiking team might get a Big Bend retrospective; a car enthusiast might get a BMW-themed one. The point is not novelty for its own sake, but creating retrospectives that feel more connected to the people in the room.
The Prompt Library as a Scrum Master Asset
"I save them. I reuse them. I refine them."
 
Joshua does not treat prompts as throwaway text. He keeps them visible on a whiteboard, labels them by purpose, and refines them over time. That library helps him preserve the structure of useful workflows while adapting the output to the team and context. For Scrum Masters and agile coaches, this is one of the practical takeaways: a prompt library becomes part of the working system, just like a facilitation kit, retrospective catalog, or coaching journal.
Faster Is Not the Same as Better
"I don't lean on it to do critical thinking for me."
 
Joshua connects AI adoption to a deeper risk: using it to produce more work without asking whether that work matters. He validates AI output, checks the data, and stays responsible for conclusions. AI helps him get to an end point faster, but the Scrum Master still owns the thinking, the interpretation, and the impact on people. That distinction matters when teams are being pushed to adopt AI without clear guidance.
What Scrum Masters Should Try on Monday
"Have it coach you. Say, this is my role. This is what's on my agenda for today."
 
Joshua's recommended first experiment is simple: do a personal standup with AI. Share what you did yesterday, what you want to do today, and the challenges in front of you. Then ask AI to act as your coach and help you identify focus, priorities, and possible next steps. Within a week, a Scrum Master can see whether this creates more clarity, better communication, and more intentional use of time.
Learning AI Without Waiting for Permission
"Start there with basic AI fundamentals."
 
For Scrum Masters who are new to AI, Joshua recommends beginning with practical courses on platforms like Udemy, Coursera, or LinkedIn Learning. Then, connect with peers who are already experimenting with prompt creation. The goal is not to become an AI expert overnight. The goal is to understand what AI can support, what it should not replace, and how to build a prompt library that improves your own work.
About Joshua McDonald
Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.
 
You can link with Joshua McDonald on LinkedIn.

Kaloyan Chalakov: Great Product Owners Start the Conversation Instead of Becoming the Boss
In this episode, we refer to Product Owner anti-patterns and team and PO collaboration.
The Great Product Owner: Open Communication, Active Listening, and Feasibility First
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Start the open conversation and listen to the critical discussions." - Kaloyan Chalakov
 
Kaloyan describes the best Product Owner pattern as almost the opposite of control. A strong Product Owner comes to the team with the outcome, the timeline, and the stakeholder context, then starts a feasibility conversation. They ask what is possible, what is risky, what can be decomposed, and what the team needs in order to deliver. In Kaloyan's example, the Product Owner stayed focused on stakeholder communication while the team helped shape the work into something practical. Stakeholders were kept in the loop, risks were visible, and everyone could adjust plans early. The most useful behavior was not a personality trait, because every Product Owner is different. It was open communication and active listening, especially when the team raised uncomfortable technical or delivery constraints. Great Product Owners do not need the team to say yes to everything. They need the team to help them face reality early enough to make better product decisions.
 
Self-reflection Question: How often do your Product Owner conversations start with feasibility and shared reality, rather than commitment pressure?
The Bad Product Owner: Acting Like the Boss of the Team
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Tell me what exactly to do, and I'll do exactly what you're telling me to do." - Kaloyan Chalakov
 
The Product Owner anti-pattern Kaloyan warns us about is the Product Owner as the boss of the team. This shows up when the Product Owner assigns work, manages people, and controls every detail of delivery instead of focusing on product outcomes and customer needs. The consequence is a damaging loop. The team stops bringing their thinking and creativity, waits for instructions, and becomes task handlers. The Product Owner then feels overwhelmed because every decision and question returns to them, so they add more control. That control removes even more initiative from the team. Kaloyan connects this pattern to the Product Owner's real work: difficult conversations with customers, narrowing big requests into practical steps, and protecting focus on product value. When the Product Owner becomes the team's manager, both product discovery and team self-organization suffer.
 
In this segment, we refer to Product Owner collaboration.
 
Self-reflection Question: Where might your Product Owner role be taking decisions away from the team instead of creating clarity for better decisions?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Kaloyan Chalakov
 
Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.
 
You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: Building Scrum Master Success Around Trust and Unspoken Leaders
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Success for me is making myself obsolete in the team." - Kaloyan Chalakov
 
Kaloyan defines Scrum Master success in a way that sounds funny at first: forty hours a week to drink coffee and do nothing. But the point is serious. Success means the team no longer needs the Scrum Master for every decision, question, or conflict. They are self-organizing, self-managed within their context, and able to call for help only when it really matters. When Kaloyan joins a new team, he avoids setting big targets in the first three months. He observes, builds trust, and watches for what the team does not show openly. One of his key signals is the presence of "unspoken leaders," the people the team looks to when something difficult happens. He learned that pattern first in safety-critical maritime work, where trust in the people beside you is not optional. For Kaloyan, Scrum Master success starts with trust, grows through observation, and ends when the team can stand on its own.
 
Self-reflection Question: Who are the unspoken leaders in your team, and how are you helping them strengthen the team's self-management?
Featured Retrospective Format for the Week: Open Room Coffee Conversation
Kaloyan's favorite retrospective format is simple: no heavy gamification, no elaborate setup, just a mature team in a room with coffee or tea and a real conversation. The team uses a ball as the talking object. Whoever wants to raise a problem takes the ball, shares what hurt during the last sprint, and asks for help. The format is unpredictable, so the Scrum Master must pay close attention to small signals: is the discussion becoming personal, is a conflict rising, or is the team finding the root cause together? Kaloyan likes the format because it brings real issues to the surface quickly, and often the third person to speak has already helped others see their own concerns more clearly.
 
In this segment, we refer to Karin Tenelius on self-management.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Kaloyan Chalakov
 
Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.
 
You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: Coaching Organizations to Challenge the Beliefs Behind Agile Pressure
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"What's happening with the team is just the symptom of what's happening with the whole system." - Kaloyan Chalakov
 
Kaloyan brings a common Scrum Master challenge: a team under pressure from a Product Owner who starts acting more like a project manager. Planning turns into a list of tasks, Daily Scrum becomes a status report, and pressure flows from customers and market competition, through management, to the Product Owner, and finally to the team. In the conversation, Vasco and Kaloyan map the system and notice something deeper than pressure: the belief that a competitor's release will directly damage the company unless the team moves faster. That belief becomes the real intervention point. Kaloyan reflects that Scrum Masters can challenge assumptions, turn beliefs into testable hypotheses, and introduce alternative beliefs that reduce pressure instead of passing it down. The practical insight is powerful: do not fight pressure by adding more pressure. Look for the source, test the assumptions behind it, and design small conversations that change the system around the team.
 
In this episode, we refer to systems thinking and limiting beliefs.
 
Self-reflection Question: What belief is creating pressure in your organization, and how could you test it with one small conversation this week?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Kaloyan Chalakov
 
Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.
 
You can link with Kaloyan Chalakov on LinkedIn.

Kaloyan Chalakov: The Agile Team That Built Great Architecture But Forgot the Customer
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"You don't have to build it only because we can. We need to lead to a purpose." - Kaloyan Chalakov
 
Kaloyan worked with a technically strong team that could build impressive architecture, pipelines, and infrastructure fast. Sprint after sprint, they showed the quality of the technical system they were creating. But the hard question stayed unanswered: what customer problem were they solving? The wake-up moment came in a sprint review, when a client finally joined and told the team that the network and architecture were nice, but they did not solve the actual problem. The customer needed one small piece of functionality, and the team could not point to it. The room went silent. The Product Owner felt exposed, the team felt embarrassed, and Kaloyan saw the moment as painful but necessary. Because the mistake happened early, it became a learning opportunity instead of a product disaster. The team learned to connect technical excellence to product value, and to ask sooner whether their work solved the customer's real need.
 
In this segment, we talk about customer feedback and Sprint Review.
 
Self-reflection Question: What are you building because it is technically interesting, and how will you test whether it solves a real customer problem?
Featured Book of the Week: Start With Why by Simon Sinek
Kaloyan recommends Start With Why by Simon Sinek because it changed how he thinks before acting. The book pushed him to pause before solving a problem and ask what the real purpose is. He started applying that question in workshops, team conversations, and product discussions. When a team member asked why a leadership workshop included a specific activity, Kaloyan realized his explanation had not landed. Instead of pushing forward, he stopped, reset, and rebuilt the workshop around a clearer purpose. For Kaloyan, the "why" is not a one-time statement. It is a question to ask at every step, because people do better work when they understand how their part connects to the bigger goal.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Kaloyan Chalakov
 
Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.
 
You can link with Kaloyan Chalakov on LinkedIn.