Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Every week day, Certified Scrum Master, Agile Coach and Business Consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!

Using Cycle Time As A Storyteller, Not A Scorecard In Agile Retrospectives | Joshua McDonald 08/19/2026

Using Cycle Time As A Storyteller, Not A Scorecard In Agile Retrospectives | Joshua McDonald Joshua McDonald: Using Cycle Time As A Storyteller, Not A Scorecard In Agile Retrospectives 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: . "Metrics is not about telling people do better. It's about telling that story." - Joshua McDonald Joshua brings cycle time as his biggest current coaching challenge. The problem is familiar: when a Scrum Master points to a story with high cycle time, developers can feel blamed, even when the intent is learning. Joshua reframes the metric as a storyteller. Instead of asking why someone took too long, he asks what journey the story went through, where it changed hands, where it waited, and what the team now knows that it did not know at the start. He also describes practical tactics: warn people in advance before discussing specific stories, keep the language gentle, avoid forcing people to explain themselves publicly, and sometimes skip the metric conversation entirely when the team needs encouragement more than analysis. Metrics matter because they move coaching away from gut feeling and toward observable patterns. Used well, cycle time becomes a barometer for stress, bottlenecks, missing product owner review, and places where the team needs support. Self-reflection Question: How do you introduce metrics so the team becomes curious about the system instead of defensive about individual performance? [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. [The Scrum Master Toolbox Podcast Recommends] 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 . /episode/index/show/scrummastertoolbox/id/42445390

The Distributed Agile Team That Hid Problems Behind Follow-Up Stories | Joshua McDonald 08/18/2026

The Distributed Agile Team That Hid Problems Behind Follow-Up Stories | Joshua McDonald Joshua McDonald: The Distributed Agile Team That Hid Problems Behind Follow-Up Stories 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: . "They started to separate and call each other out, which is definitely not Agile." - Joshua McDonald Joshua shares the story of a 17-person distributed team spread across time zones, cultures, and communication styles. Some team members were direct and ready to challenge problems in public. Others preferred quieter, one-on-one conversations. Over time, those differences created a blame environment where people stopped asking for help and started hiding problems. Long-running work was closed and replaced with follow-up stories, then part two, then part three, until the real issue disappeared under Jira housekeeping. The result was not better flow, but delayed learning, missed upskilling opportunities, and a stressful team environment where quieter people stopped speaking in standups and retrospectives. Joshua explains what he would do differently now: split the team by communication patterns, listen to what each group needs, act as a mediator, and only bring the whole group together once people feel heard. In this segment, we talk about . Self-reflection Question: What signals tell you that people are hiding problems because the team environment does not feel safe enough? Featured Book of the Week: Never Eat Alone by Keith Ferrazzi Joshua recommends because it reframed networking as a relationship practice, not a transaction. The book helped him see that staying connected with people creates learning, support, and a safety net over time. He also mentions the Bible as a daily source for reflecting on respect, peace, and conflict resolution, especially because Scrum Masters often need more than process knowledge to help teams work well together. For Joshua, both recommendations point to the same deeper idea: our work improves when we treat relationships as something to maintain before we urgently need them. [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. [The Scrum Master Toolbox Podcast Recommends] 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 . /episode/index/show/scrummastertoolbox/id/42445425

When Your Agile Enthusiasm Creates Resistance, Start With Trust | Joshua McDonald 08/17/2026

When Your Agile Enthusiasm Creates Resistance, Start With Trust | Joshua McDonald Joshua McDonald: When Your Agile Enthusiasm Creates Resistance, Start With Trust 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: . "Don't assume they're as enthusiastic about Agile and Scrum as you are." - Joshua McDonald Joshua McDonald joins us from the USA with a failure story many Scrum Masters will recognize: stepping into a team and assuming the role, the expectations, and the Agile conversation were already understood. The team had worked with a hands-off Scrum Master before, so Joshua's attempts to facilitate events, talk about metrics, and bring more structure were received as interference. The pushback grew so strong he sensed people were talking to his manager about removing him. The turning point came when Joshua stopped leading with Scrum language and started rebuilding social equity through one-on-ones. He asked what he could have done differently, acted on the feedback, and reminded himself and the team to assume positive intent. His lesson is direct: when we join a new team, trust is the work before the work. Go slow, understand how people operate, and bring suggestions through relationships before bringing them to the whole room. Self-reflection Question: When you join a new team, what do you do first to understand their relationship with Scrum before you suggest changes? [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. [The Scrum Master Toolbox Podcast Recommends] 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 . /episode/index/show/scrummastertoolbox/id/42445435

The Agile Product Owner Who Runs Two Quarters Ahead of the Team | Wasim Osman 08/14/2026

The Agile Product Owner Who Runs Two Quarters Ahead of the Team | Wasim Osman Wasim Osman: The Agile Product Owner Who Runs Two Quarters Ahead 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: . The Great Product Owner: The Absolute User Who Works Two Quarters Ahead 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: . "The Product Owner needs to be the absolute user of the software—the user's journey so well defined in their mind that every engineer's question already has an answer, with context." - Wasim Osman Wasim's best Product Owner works ahead of the team without doing the team's work. Their product roadmap is well-defined at least two quarters ahead of the development cycle, so nobody is panicking against tomorrow's deadline. Designers and product people work on concepts months before development starts, which gives them room to show early ideas to engineers and gather feedback while there's still time to change course. Crucially, this PO is the absolute user of the software—so completely inside the user's journey that when an engineer asks "how does this connect to that module?", the answer is ready, with context. Wasim connects this to how his team uses AI today: the PO can run ahead, spin up prototypes, and iterate on the ideas without burdening the team with building throwaway work—while staying the voice of the customer. Self-reflection Question: How far ahead of your team is your Product Owner really working—and could they answer an engineer's design question today without going back to the drawing board? The Bad Product Owner: When Optimism Overrides the Data 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: . "They were optimistic without any data. We had the data—they were just being wishful." - Wasim Osman The worst anti-pattern Wasim has seen is the Product Owner whose optimism overrides the evidence. In one company, a customer asked for a delivery estimate, and the product team promised an aggressive date—"optimistic without any data," even though the data existed. When the engineering team sat down with the numbers, it was obvious the date was impossible, but that gap never reached the customer. The product team stayed disconnected from both the engineers and the customer, so expectations kept drifting from reality. Wasim, who held the data, finally bridged the two and told the product team the real timeline was several months later. They "lost their minds"—but by then it was too late to renegotiate gracefully. The deeper anti-pattern: features handed down without enough depth, so the moment engineering hits real questions mid-development, the PO panics and rushes back to the drawing board while development is already in motion. As Wasim says, "optimism just took over too much." Self-reflection Question: When was the last time optimism—not evidence—set a delivery date on your team, and who had the data that should have been in the room? [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. [The Scrum Master Toolbox Podcast Recommends] About Wasim Osman Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He's passionate about building technology that drives real business impact. You can link with . /episode/index/show/scrummastertoolbox/id/42344840

The Scrum Master as a Router, Redefining Success Through Efficient Communication | Wasim Osman 08/13/2026

The Scrum Master as a Router, Redefining Success Through Efficient Communication | Wasim Osman Wasim Osman: The Scrum Master as a Router, Redefining Success Through Efficient Communication 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: . "A big part of the Scrum Master role is to work as a router—handling a lot of conversations with a lot of different devices, even though the internet is coming in through one cable." - Wasim Osman For Wasim, success as a Scrum Master looks like a router in a house: many conversations, many stakeholders, all flowing through one point that has to prioritize, schedule, and stay on time. If the router slows down, everything downstream stalls—and the Scrum Master becomes the blocker. Early in his career he was overwhelmed juggling three or four engineering teams, so he built himself a personal Kanban board and ran his own quick standup every morning and again at the end of the day, just to see what moved, what stalled, and why. Getting organized with himself is when the work started to feel satisfying, because he stopped being the bottleneck. But he's honest about the hardest part: people rarely tell you to your face when you're slowing them down. The feedback is already there—you're just not hearing it. So you have to ask for it, react well when you get it (or people stop offering), and sometimes name the awkward truth first: "Our meetings used to be better—what happened?" That opening gives everyone permission to be honest. Self-reflection Question: If you're the "router" for your teams, where are you quietly becoming the bottleneck—and who would tell you if you were? Featured Retrospective Format for the Week: What Went Well / What Went Wrong / Outliers + Open Discussion Wasim's go-to retrospective is deliberately bare-bones: what went well, what went wrong, and—the part that makes it his own—what were the outliers, followed by open discussion. He added the "outliers" question years ago after noticing that team members kept raising points that weren't clearly good or bad, but were still significant enough to discuss. Outliers give people "a bucket for sharing information that has no polarity"—an early signal about the future, a quiet concern, something that doesn't fit the other two columns but matters. He sometimes pairs it with lightweight metrics: sprint completion rate, or tickets that sat too long in review or QA, surfacing patterns the team wouldn't otherwise notice. Self-reflection Question: What "outlier" signal has your team been sitting on—neither a win nor a problem yet—that deserves an open conversation before it becomes one? [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. [The Scrum Master Toolbox Podcast Recommends] About Wasim Osman Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He's passionate about building technology that drives real business impact. You can link with . /episode/index/show/scrummastertoolbox/id/42344620

How Agile Teams Can Start Adopting AI in Software Development | Wasim Osman 08/12/2026

How Agile Teams Can Start Adopting AI in Software Development | Wasim Osman Wasim Osman: How Agile Teams Can Start Adopting AI in Software Development 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: . "It's like my own software has a voice now. It's telling me—okay, you're going to build me like this? Have you considered this?" - Wasim Osman Wasim's biggest current challenge is one nearly every team shares: how AI is reshaping software development. He sees a clear split—developers rapidly adopting AI-driven development, and others "not downright rejecting it, but still taking their time." His warning is blunt: even when AI hallucinates and generates garbage code, it lets you deliver an order of magnitude faster, and the quality is only going to improve. The early adopters are heading somewhere the late adopters won't be able to reach. In practice, the resistance shows up as questions no one can answer: if I used to get every requirement nailed down before writing code by hand, what do I do with AI—just ask it for a one-liner and hope? Leadership often can't help, because they lack AI experience themselves. At Orkestra SCS, the head of engineering did holistic research into how companies (like AWS, with its AI-Driven Development Lifecycle) are reshaping the process, documented it, and shared it with every team. Feedback sessions and hands-on experiments followed, until they built a tailored version that fit how they actually work. The mindset shift that unlocked it: treat AI as a partner. Wasim describes his software "having a voice"—asking him questions he'd never think of, the way a pair-programming partner would, so the team explores the solution space instead of guessing at it. Self-reflection Question: Is your team treating AI as a threat to write around, or as a pair-programming partner that surfaces the blind spots you'd never find alone? [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. [The Scrum Master Toolbox Podcast Recommends] About Wasim Osman Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He's passionate about building technology that drives real business impact. You can link with . /episode/index/show/scrummastertoolbox/id/42363245

When a Scrum Team's Silence Becomes a Self-Fulfilling Prophecy | Wasim Osman 08/11/2026

When a Scrum Team's Silence Becomes a Self-Fulfilling Prophecy | Wasim Osman Wasim Osman: When a Scrum Team's Silence Becomes a Self-Fulfilling Prophecy 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: . "No team is interested in deliberately destroying their outcome or their team. Nobody does that on purpose." - Wasim Osman Wasim's team was building a SaaS product with real potential. They followed Scrum, shipped features fast—and quietly let the bugs pile up. When customers finally pushed back ("you built five features, four of them have bugs"), the team made a confident bet: one quarter for new features, then one month to fix everything. It didn't work. The bug-bashing month revealed deeper, structural problems that demanded refactoring, and the roadmap was already packed. Then the fixes got handed to a single team, who felt demoted from the "prestigious" work of building features. Resentment grew between the teams. At the height of that tension, the company was acquired by a waterfall-driven parent company. The head of engineering left, the chief architect and two senior engineers followed, and it became chaos. Wasim's hardest lesson wasn't about the acquisition—it was about voice. The engineers assumed waterfall was being forced on them and stopped pushing back; leadership assumed the engineers were fine with it. Nobody said what they actually thought, and the fear became reality. As Wasim puts it, there was "no captain on the ship." In this segment, we talk about how even conversations need to be iterative, and how a Scrum Master has to balance speaking up (so the team isn't rudderless) without speaking so much that the team stops voicing their own opinions. Self-reflection Question: Where on your team is an unspoken assumption quietly hardening into reality, and what would it take for you to name it out loud first? Featured Book of the Week: Difficult Conversations by Douglas Stone, Bruce Patton, and Sheila Heen Wasim's most-recommended book is . What stuck with him is a deceptively simple model: every hard conversation is really made of three conversations—the "what happened" conversation (the content), the feelings conversation, and the identity conversation (what the situation says about whether you're competent, good, or lovable). "When I first read it, I thought there can't be only three types of conversations," Wasim admits. "But once you've gone through the book, you can put any conversation into one of those funnels." He found it especially powerful in retrospectives: when the same issue keeps resurfacing, the real conversation is often about feelings, not action items—someone was never okay with an earlier decision, and that's why the follow-ups never happened. Self-reflection Question: In your last tense retrospective, which of the three conversations—content, feelings, or identity—was really driving the room? [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. [The Scrum Master Toolbox Podcast Recommends] About Wasim Osman Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He's passionate about building technology that drives real business impact. You can link with . /episode/index/show/scrummastertoolbox/id/42363275

From Finance to Scrum Master, a Deliberate Career Pivot | Wasim Osman 08/10/2026

From Finance to Scrum Master, a Deliberate Career Pivot | Wasim Osman Wasim Osman: From Finance to Scrum Master, a Deliberate Career Pivot 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: . "The homework should start a lot earlier than that. The person looking for a particular role should already be moving in that direction before they even start the journey." - Wasim Osman Wasim never planned to become a Scrum Master. He trained in finance and stock markets in the UK, but the pull toward software—and even 3D animation—had been there since he was young. When he realized the finance world wasn't for him, he made a move that looked like a detour and turned out to be a runway: he joined the people team at a tech company in Bangladesh, a branch of a New York-based firm. He didn't have the leverage to be picky, so he took the opportunity, learned how the engineering teams actually worked, and made himself useful. When the company started shifting from waterfall to agile and hosting Scrum certification events, Wasim was in the room organizing them. One day the head of engineering asked a "random question"—would he consider becoming a Scrum Master? For Wasim, it was an easy yes, because it was the direction he'd quietly been aiming at all along. He shadowed a senior engineer for a quarter, then took over a team of senior-most engineers who were patient with his mistakes. That patience built his confidence, and his willingness to keep his prior curiosity alive made the transition feel organic rather than forced. Self-reflection Question: What direction are you quietly moving toward right now, and what "homework" could you start today so the next opportunity feels organic instead of accidental? [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. [The Scrum Master Toolbox Podcast Recommends] About Wasim Osman Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He's passionate about building technology that drives real business impact. You can link with . /episode/index/show/scrummastertoolbox/id/42363290

From "Scrum Master Is the Secretary" to True Co-Leadership | Havva Sevay 08/07/2026

From "Scrum Master Is the Secretary" to True Co-Leadership | Havva Sevay Havva Sevay: From "Scrum Master Is the Secretary" to True Co-Leadership 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: . The Great Product Owner: The Co-Leader Who Mastered the PO Stances 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: . "Co-leadership means both sharing leadership in a lateral way, not a disciplinary way—the PO owns the technical part, the Scrum Master the organizational part." - Havva Sevay Havva's best Product Owner already understood co-leadership—and went further. He used the from Scrum.org as a feedback tool, asking the team to rate him on each stance (customer representative, company representative, and so on) with a percentage, then using that input to improve his skills deliberately. It's the same mindset Scrum Masters can adopt with their own stances: be aware of the options, get honest feedback, and adapt to the context, because the right stance changes over time. A great PO, in Havva's experience, treats their role as a skill set to be developed in partnership—not a title to defend. Self-reflection Question: Could the PO stances become a feedback tool in your team—and would you be willing to be rated on your own Scrum Master stances? The Bad Product Owner: "The Scrum Master Is My Secretary" 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: . "The worst is the PO who believes he's the product manager and the Scrum Master is the secretary. I said: I'm not your assistant, I don't bring your coffee." - Havva Sevay The worst anti-pattern Havva has lived through is the Product Owner who treats the Scrum Master as a secretary—there to share the screen, organize the meeting, and take orders. Havva confronted it directly in a one-on-one: this is upside down. My job is to teach self-organization, not to be your assistant. But she didn't stop at the boundary—she helped the PO understand her role and walked in his shoes too, even sending him to a Scrum Master training while she experienced his responsibilities. Her strongest recommendation: from the very first meeting with a Product Owner, talk explicitly about who does what, surface expectations, and agree how you'll work together. Don't assume they know your job—or that you know theirs. The way out of the "secretary" trap is : lateral, shared leadership built on time and trust. Self-reflection Question: Have you ever explicitly agreed with your Product Owner on who is responsible for what—or are you both operating on untested assumptions? [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. [The Scrum Master Toolbox Podcast Recommends] About Havva Sevay Havva is a people-focused organizational development expert with a Master's in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement. You can link with . /episode/index/show/scrummastertoolbox/id/42149805

Success Is Feedback, Not Metrics—And the Power of Standing in Someone Else's Shoes | Havva Sevay 08/06/2026

Success Is Feedback, Not Metrics—And the Power of Standing in Someone Else's Shoes | Havva Sevay Havva Sevay: Success Is Feedback, Not Metrics—And the Power of Standing in Someone Else's Shoes 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: . "My success is not metrics or numbers—that was my controller past. I measure myself through feedback, and through team satisfaction." - Havva Sevay As a former project controller, Havva could have defined success in numbers. Instead, she measures it through feedback and team satisfaction. As long as people keep talking to her—telling her how she can be a better Scrum Master—she considers that success, and she treats even hard feedback as learning. But the most striking part of her definition is the discipline of standing in someone else's shoes. When a developer suggested she'd give better advice if she understood programming, she took the —the hardest training she's ever done—just to feel the team's daily reality. Vasco connects it to coaching a team that builds tools for other teams: the role isn't to produce the system, it's to make the other teams' lives easier. Havva's takeaway for every Scrum Master: put your shoes in a different position. Understanding the work from the other person's perspective is what drives team success. Self-reflection Question: How do you measure your own success as a Scrum Master—and when did you last experience your team's work from their perspective? [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. [The Scrum Master Toolbox Podcast Recommends] Featured Retrospective Format for the Week: The Mario Kart (Gamified) Retrospective Havva's favorite retrospective format is gamification—she believes in the magic of playing, because it lets everyone relax, open up, and step out of the daily stress. Her go-to is a . Team members choose their character (Mario, Luigi, Peach, Bowser), then map the sprint onto the game: the star and speed mushroom for successes and who helped them, the bad mushroom for impediments, another icon for the solution. They praise each other by handing out stars, and close with a "Mario checklist" of action points for next time. Havva also adapts to the team—asking their favorite Nintendo game, board game, or even pen-and-paper RPGs like The Dark Eye (Das Schwarze Auge). The point: make the retrospective something people genuinely enjoy, and the honest reflection follows. About Havva Sevay Havva is a people-focused organizational development expert with a Master's in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement. You can link with . /episode/index/show/scrummastertoolbox/id/42150015

AI vs. Real People—Helping Teams Avoid Information Overload | Havva Sevay 08/05/2026

AI vs. Real People—Helping Teams Avoid Information Overload | Havva Sevay Havva Sevay: AI vs. Real People—Helping Teams Avoid Information Overload 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: . "It's still a tool. It can make mistakes, it can hallucinate. People don't really question it—and that's the danger." - Havva Sevay This week's coaching conversation tackles a challenge Havva—and many Scrum Masters—are living right now: AI vs. real people. For some, AI is a useful tool; for others, it's a magic oracle that solves everything and makes people replaceable. Havva sees the real risk in teams that accept AI's confident answers without double-checking, and in leaders who use AI to generate massive documents and dump them on teams as finished decisions. Vasco pushes the conversation into the practical: when a flood of AI-generated information, requirements, and tool changes lands on a busy team, how do you help them cope? Havva's answer is to step back and ask the human questions first—what is the epic? what does the stakeholder actually want? what do we really need right now? Then she pulls out a deliberately low-tech move: forget AI for one second. Her team uses the manually to separate what's important now from what can wait. AI is a great tool—but the filtering of what matters is still human work. Self-reflection Question: When AI floods your team with information and options, what is your practice for helping them separate what matters now from the noise? [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. [The Scrum Master Toolbox Podcast Recommends] About Havva Sevay Havva is a people-focused organizational development expert with a Master's in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement. You can link with . /episode/index/show/scrummastertoolbox/id/42171765

The Car Configuration Team That Spiraled Into Silence—and the Workshop That Saved It | Havva Sevay 08/04/2026

The Car Configuration Team That Spiraled Into Silence—and the Workshop That Saved It | Havva Sevay Havva Sevay: The Car Configuration Team That Spiraled Into Silence—and the Workshop That Saved It 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: . "First they tell you their opinion. Then they start shouting, getting emotional. And the third one is silence—and resignation. That's the worst part." - Havva Sevay Havva remembers a highly motivated development team working on a car configuration system so complex it began to wear them down. They asked for training. The Product Owner waved it off—they've had enough training, they should understand it. What followed was a three-stage spiral Havva now recognizes anywhere: first the team shares opinions and solutions, then frustration turns to emotion and shouting, and finally comes silence and resignation. The team even kicked the Product Owner out of their daily—a low point Havva calls the worst she has seen in her career. The turning point was a LEGO Serious Play workshop. By getting both sides to build how they wanted to work together, the Product Owner did active listening for the first time, recognized the team needed an experienced developer to guide them, and the relationship transformed. The lesson: Scrum Masters are the facilitators of those moments of coming together—and there need to be many, at every level. Self-reflection Question: Is a team you support moving through opinion → emotion → silence right now? What moment of coming-together could you facilitate before they reach resignation? [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. [The Scrum Master Toolbox Podcast Recommends] Featured Book of the Week: The Unfair Advantage by Ash Ali and Hasan Kubba Havva discovered and it reshaped how she thinks about her own style as a Scrum Master. The book argues that every person has advantages others don't—and the skill is recognizing and using them. Havva took that idea literally: she had trained in LEGO Serious Play, a method many dismiss as "for kids," and decided to make it her unfair advantage, promoting it inside her company until even upper management asked to use it. "I got the knowledge, so I used it internally," she says. The lesson for Scrum Masters: own your style, embrace what makes you different, and don't be discouraged when not every team responds to it. About Havva Sevay Havva is a people-focused organizational development expert with a Master's in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement. You can link with . /episode/index/show/scrummastertoolbox/id/42171565

When Doing Your Best Isn't Enough—The Scrum Master Lesson That Changed Everything | Havva Sevay 08/03/2026

When Doing Your Best Isn't Enough—The Scrum Master Lesson That Changed Everything | Havva Sevay Havva Sevay: When Doing Your Best Isn't Enough—The Scrum Master Lesson That Changed Everything 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: . "I didn't really acknowledge that the team is important, or what a team needs. I thought I was only focusing on getting the job done." - Havva Sevay When Havva took her first Scrum Master job, she knew the framework cold and she was highly motivated. So she did exactly what the framework told her to do—and failed. Frustrated, she kept asking herself the same question: why did I fail? I really did my best. The turning point came from a mentor who asked her something she hadn't considered: did you ever think about what the team needed? In this episode, Havva walks us through the slow, honest work of realizing she had been judging instead of listening, pushing instead of stepping back. Her mentor introduced her to —writing down what people actually said, not her interpretation of it—and to the discipline of silence. Becoming a better Scrum Master, she learned, is an everyday process that takes its time. We also explore how she stayed grounded: taking courses outside her bubble, networking, and learning from other people's experience. Self-reflection Question: When you face a team problem, are you observing what is actually happening, or are you already judging and rushing to the next step? [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. [The Scrum Master Toolbox Podcast Recommends] About Havva Sevay Havva is a people-focused organizational development expert with a Master's in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement. You can link with . /episode/index/show/scrummastertoolbox/id/42171840

The MIA Product Owner vs. The One Who Owned the Outcome | Danil Chernyshev 07/31/2026

The MIA Product Owner vs. The One Who Owned the Outcome | Danil Chernyshev Danil Chernyshev: The MIA Product Owner vs. The One Who Owned the Outcome 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: . The Great Product Owner: Communicating Value, Inviting the Right People 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: . "It's basic Scrum—but it's not basic." - Danil Chernyshev The best Product Owner Danil ever worked with was Jamie Spence, on a Master Data Management re-architecture at Canadian Tire. The goal wasn't only to upgrade a system—it was to rethink how a major retailer with many different banners should work across all of them. Jamie didn't write user stories; the BAs did that. What he did was communicate, in a super-clear way, the value expected at every step. He didn't attend every daily Scrum, but he was there whenever the team wanted him, allocating his time on demand. He cared about user experience and lived for the feedback loop—"this sprint I want to deliver this part and see how it goes." And he invited the proper stakeholders to each sprint review: a small, deliberately varied group chosen by what had been delivered and whose feedback the team actually needed. As Danil and Vasco agree, it sounds obvious—and that's exactly why it's worth celebrating. Obvious and common are not the same thing. Self-reflection Question: Does your Product Owner communicate expected value at every step—or just hand over user stories and disappear? The Bad Product Owner: Present on Paper, Missing in Action 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: . "On paper, you have a Product Owner. But you don't have a Product Owner." - Danil Chernyshev The most common—and worst—anti-pattern Danil sees is the MIA, or "missing in action," Product Owner: a person with the title who doesn't actually own the product. Sometimes it's a BA or a tech lead wearing the label; sometimes it's someone who simply can't make decisions, or doesn't understand what they're responsible for because they're busy doing another job. The fix starts with clarity: first understand what the product even is, then put in place a Product Owner who makes decisions, owns the end-user experience, and maximizes value. Danil also flags a structural trap—one Product Owner per product, not one per team. He stretches the idea with vivid examples: an Agile coach leading a transformation is effectively the Product Owner of the process, with Scrum Masters as the developers; and Steve Jobs was the Product Owner of the iPhone while also being a customer for other Product Owners building pieces of it. Ownership is about maximizing value for the customer—not about who writes the user stories. In this segment, we refer to the great Product Owner pattern Danil shares above, and how the Scrum Master's job is to help the Product Owner grow into real ownership. Self-reflection Question: Is your Product Owner empowered to make decisions and own outcomes—or just a title on an org chart? [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. [The Scrum Master Toolbox Podcast Recommends] About Danil Chernyshev Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams' potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results. You can link with . /episode/index/show/scrummastertoolbox/id/42110890

Success Is Synergy—When the Team and the Product Both Win | Danil Chernyshev 07/30/2026

Success Is Synergy—When the Team and the Product Both Win | Danil Chernyshev Danil Chernyshev: Success Is Synergy—When the Team and the Product Both Win 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: . "Success is when team members say thank you, and praise others for delivering a successful product." - Danil Chernyshev For Danil, success as a Scrum Master is never one thing—it's a combination. It's the moment team members thank each other and credit the whole group for a product that actually landed with customers. As he reminds us, Scrum Masters, Product Owners, and developers are all there for the same reason: to deliver a product and solve real problems for the end user. A healthy team that has fun together but ships nothing has only spent time and money. A team that delivers but burns everyone out, until no one wants to see each other again, isn't a success either. Real success is the synergy of both: a productive team, happy customers and stakeholders, and people who still have the energy to keep going. Danil also turns the lens inward—success means understanding where you are in your own journey. And it grows from action: when teams get stuck overthinking, he guides them back to what's inside their control, helps them find the smallest valuable step, and gets them experimenting. Start where you are, do what you can, then learn from it. Self-reflection Question: Are you optimizing for a happy team, a delivered product, or the synergy of both—and how would you know the difference? Featured Retrospective Format for the Week: Lean Coffee (paired with 1-2-4-All and 5 Whys) Danil doesn't lock himself into a single retrospective format—he chooses based on the sprint, guided by "common sense in Scrum." His default is to keep a running list of topics gathered throughout the sprint, then open the retrospective with a session to democratically decide what to discuss. From there, a light topic gets a quick Lean Coffee conversation, while a deeper one moves into from or a 5 Whys. The non-negotiable for Danil: every retrospective must end with actionable action items. A retro that produces only conversation and no change, he says, was a waste of time—maybe fun, but still a missed opportunity to reflect, learn, and adapt. [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. [The Scrum Master Toolbox Podcast Recommends] About Danil Chernyshev Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams' potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results. You can link with . /episode/index/show/scrummastertoolbox/id/42112185

Coaching the Outsider In—Helping a Distrustful Team Through Transformation | Danil Chernyshev 07/29/2026

Coaching the Outsider In—Helping a Distrustful Team Through Transformation | Danil Chernyshev Danil Chernyshev: Coaching the Outsider In—Helping a Distrustful Team Through Transformation 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: . "Developers and QAs know each other very well, but they don't trust anybody else." - Danil Chernyshev This week's coaching conversation starts with a hard situation. A subcontractor's developers—people who had always worked isolated from the business, with no plans and no communication—were brought back inside the "mother firm" as part of a digital transformation. Overnight they faced new teams, Scrum, SDLC, CI/CD, and full transparency. The developers and QAs trusted each other completely and trusted no one else: not the Scrum Master, not the Product Owner, not the BAs. Forced to estimate with story points, every story came back as a 3 or a 5, with no conversation. When Danil asked why, the answer was always "we'll discuss internally and tell you tomorrow"—he suspected a second, hidden daily Scrum without him. As he and Vasco unpack it, the real issue is transparency itself: a team used to hiding now feels exposed and doesn't know the consequences of being open. Vasco offers an experiment—build a "trio" of the Product Owner, the Scrum Master, and one friendly insider from the team to prepare refinements together. The Product Owner is always the outsider; pairing them with a trusted insider lets ideas and experiments spread faster. Before you can improve the Scrum, you first have to bring the outsiders in. Self-reflection Question: Where on your team is trust the real bottleneck—and who is the "insider" who could help an outsider earn it? [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. [The Scrum Master Toolbox Podcast Recommends] About Danil Chernyshev Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams' potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results. You can link with . /episode/index/show/scrummastertoolbox/id/42112215

Why Teams Always Adapt—And How Bad Rules Push Them Into Zombie Scrum | Danil Chernyshev 07/28/2026

Why Teams Always Adapt—And How Bad Rules Push Them Into Zombie Scrum | Danil Chernyshev Danil Chernyshev: Why Teams Always Adapt—And How Bad Rules Push Them Into Zombie Scrum 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: . "Teams always adapt. You only get to decide what they adapt to." - Danil Chernyshev Most dysfunction doesn't start with the team—it starts with the structure around them. Danil shares the story of a classic metrics-driven organization where Scrum Masters reported to a dedicated manager who measured their success by team velocity. That manager tracked retrospectives in a separate log, and would show up at the daily Scrum to confirm everyone answered the three questions. The result was predictable: the retrospective became a clock to survive, the daily became a checkbox with no real conversation, and velocity turned into theater—stories closed as "done," then reopened as "part two" in the next sprint. There was never a real done increment. Danil refuses to blame the team. They were doing exactly what teams always do—adapting to survive the rules and boundaries handed to them. As he and Vasco explore, the only real choice a leader has is not whether a team adapts, but what they adapt to. Dictate bureaucracy, and they'll adapt to surviving it. That's how productive, enjoyable work quietly turns into zombie Scrum. Servant leadership exists precisely so someone helps the team adapt toward value—not toward compliance. In this segment, we talk about , and you can hear . Self-reflection Question: Look at a behavior on your team you find frustrating—what rule or structure might that team be adapting to in order to survive? Featured Book of the Week: Actionable Agile Metrics for Predictability by Daniel Vacanti Danil calls this book eye-opening. It changed how he thinks about metrics—not as a reporting tool for executives, but as something teams can use for themselves to understand what to do next and how to improve. As he puts it, "after that book, you will probably know that a lot of cumulative flow diagrams that you saw in your past, they doesn't work well, and need to be rebuilt." The book makes flow metrics serve the team first, while still giving leadership the transparency they need. You can also hear , and get the book here: . [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. [The Scrum Master Toolbox Podcast Recommends] About Danil Chernyshev Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams' potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results. You can link with . /episode/index/show/scrummastertoolbox/id/42112300

Forged in the Fire—Why the Scrum Master Role Tests Even Experienced Leaders | Danil Chernyshev 07/27/2026

Forged in the Fire—Why the Scrum Master Role Tests Even Experienced Leaders | Danil Chernyshev Danil Chernyshev: Forged in the Fire—Why the Scrum Master Role Tests Even Experienced 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: . "From my story, you can probably say that I was forged in the fire." - Danil Chernyshev Danil had already climbed the ladder. He started with Scrum in 2010 as a developer, grew into a development manager, and reached executive level, running a department of 70 developers in his home country. Then he immigrated to Canada and had to start his career fresh. Certified by Scrum.org as both Scrum Master and Product Owner, the first role he landed was Scrum Master—and that's where the trouble began. He knew SDLC inside out, he knew how developers think, he knew Scrum from the trenches. What he didn't know was how to be a servant leader: how to balance serving and leading, how to measure his own success, how to even notice the small wins. After years at the top, he was suddenly the person who knew the least. In this episode, Danil shares why he stayed in the role instead of walking away—he loves building processes that help teams evolve, and he couldn't resist a real challenge. His advice to anyone at that same crossroads: be patient, reflect, build a feedback loop, and never stop learning. A certification proves you understand the base theory. Everything that matters comes after. In this episode, we refer to the , and how the storming phase tests every team—and every newcomer. Self-reflection Question: When was the last time you were the person on the team who "knew the least"—and what did that teach you about your own growth? [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. [The Scrum Master Toolbox Podcast Recommends] About Danil Chernyshev Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams' potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results. You can link with . /episode/index/show/scrummastertoolbox/id/42112400

The Too-Technical PO and the One Who Was Willing to Experiment | Alf Dobbert-Baums 07/24/2026

The Too-Technical PO and the One Who Was Willing to Experiment | Alf Dobbert-Baums Alf Dobbert-Baums: The Too-Technical PO and the One Who Was Willing to Experiment In this episode, we refer to and the value of keeping the PO–developer conversation at the goal level. The Great Product Owner: The PO Who Was Willing to Drop the Spec and Trust the Developers 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: . "Let's ditch the technical part, and let's see what happens." - Alf Dobbert-Baums The Great PO, in Alf's experience, is willing to experiment with letting go. She stopped writing detailed technical specifications and started writing plain user stories. Then — and this is the harder move — she stopped throwing them over the fence and walked into the developers' space to have the conversation. Alf had coached her toward it, and he watched the trust compound. Because she trusted the developers on the how, she had less work to do (the developers were closer to the system anyway) and the developers had room to make real decisions. The conversation stayed where it belonged: on the goal. Alf names the pattern this great PO embodied — open to experiments, willing to say "let's see what happens," and quietly resisting the seductive pull of getting technical because it feels safer. The Scrum Master's job is partly to make that letting-go feel safe enough to try. Self-reflection Question: Where is your PO still writing the "how" — and what would it take for them to trust the developers enough to write only the "why" and the "what"? The Bad Product Owner: The PO Who Thinks They Know More Than the Developers 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: . "He said: 'developers can retrieve the information from the archive database.' The developer said: 'the information is not in the archive database.'" - Alf Dobbert-Baums The anti-pattern is the PO who is too technical — the one who writes specs full of implementation detail and treats the developers as executors. Alf calls him John. John wrote a user story that told the developers exactly where to fetch the data from: the archive database. Then he tried to hand the story to Alf to present, the way a memo gets handed across a desk. Alf refused. He insisted John present it to the developers himself. John did. The first developer to speak said the information wasn't in the archive database. Alf hopes that moment humbled John a little. The point isn't whether John was right about the database — the point is the dynamic. When the PO writes the technical answer into the story, the developers stop being collaborators and become receivers. The translation work that creates real value — between user goal and technical option — never happens. The PO ends up with more work, less ownership from the team, and worse outcomes. In this segment, we refer to and the idea that great POs facilitate the conversation between user goal and team, rather than dictating it. Self-reflection Question: When was the last time your PO wrote a technical detail into a story and the developers had to walk it back — and what would change if the PO trusted them to design the "how"? [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. [The Scrum Master Toolbox Podcast Recommends] About Alf Dobbert-Baums Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation. You can link with . /episode/index/show/scrummastertoolbox/id/41917230

Success Is When the Team Gets Closer to the User | Alf Dobbert-Baums 07/23/2026

Success Is When the Team Gets Closer to the User | Alf Dobbert-Baums Alf Dobbert-Baums: Success Is When the Team Gets Closer to the User 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: . "Getting closer to the user — it's always very good to get the feedback from the user." - Alf Dobbert-Baums For Alf, success as a Scrum Master is measurable in proximity: how close did you get the team to the actual user? He tells a small story that makes the point bigger than it sounds. In a sprint review, a user mentioned an annoying detail — clicking an item in a long list opened a popup, and when you closed the popup, the focus jumped back to the top of the list. Four hours later, the team had fixed it. A small JavaScript change saved a whole customer-center team from scrolling back to find their place dozens of times a day. The shift Alf coaches is treating the review as a working meeting, not a demo. Users don't clap and leave — they discover. They surface the thing the PO doesn't see, because the PO has perspective and the user has the actual workflow (often with three other apps open at the same time). Alf credits a usability test he once ran for opening his eyes: "Why are you clicking there? Nope, she wouldn't click on there." When the developer sees a real person use the software, the product changes. The guessing stops. In this segment, we refer to by Michael Dougherty and Pete Oliver-Kruger and their Usability Theater technique — getting users to use the product while the team watches, the way you'd watch a play. Self-reflection Question: When did your team last watch a real user use the product — and if it's been a while, what's stopping you from inviting one to your next review? Featured Retrospective Format for the Week: The Classic Four — Prime Directive + Good / Learned / Change / Puzzles Alf's favorite retro is one of the very first. Open with the , then walk the team through four questions: what was good, what did we learn, what should we change, and what still puzzles us. Alf likes it because it celebrates successes, shares knowledge, and — through the "puzzles" question — gives space for the unresolved things people carry in their heads. But he wants to stress one thing most teams skip: revisit the agreed improvements in the next retro. Did you do them? Are they still relevant? Did the world change? Even improvements that didn't work give you information — about who to involve next time, what was missing, what was too much. Without revisiting, every retro starts from scratch. [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. [The Scrum Master Toolbox Podcast Recommends] About Alf Dobbert-Baums Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation. You can link with . /episode/index/show/scrummastertoolbox/id/41917285

When Management Writes a Book — AI, Strict Process, and the Missing Court System | Alf Dobbert-Baums 07/22/2026

When Management Writes a Book — AI, Strict Process, and the Missing Court System | Alf Dobbert-Baums Alf Dobbert-Baums: When Management Writes a Book — AI, Strict Process, and the Missing Court System 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: . "They don't really know — do I need to follow these rules, or are they at my goodwill?" - Alf Dobbert-Baums The developers and AI are on good terms. Then management decided to extend AI into product management — and the way to do that, of course, was stricter process. Same JIRA boards. Same columns. Same quality gates. Across every product. Management wrote a book and called it "how we develop." Then, in the next breath, said: "but it's not meant to be that strict — you have flexibility." Two messages, opposite directions. The result, Alf describes, is confusion and psychological-safety problems. The teams don't know whether they're playing by the rules or breaking them. They experiment with how far they can bend the book. They fall back on "common sense" and quietly skip what makes no sense. They've collected feedback — structured, organized — but feel they aren't heard. In the conversation, Vasco's framing of the legal system (every set of rules needs a court system to interpret them) led Alf to a real experiment: take the negative rules and reframe them as positive goals. Not "fewer meetings" — "meaningful meetings." Then match feedback to the goal, not the rule. It's an idea Alf came up with mid-conversation, and it's the kind of small frame-shift that can crack open a stuck dialogue with management. Self-reflection Question: Where in your organization is management asking people to follow rules they haven't defined the goal for — and what would change if you reframed those rules as goals? [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. [The Scrum Master Toolbox Podcast Recommends] About Alf Dobbert-Baums Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation. You can link with . /episode/index/show/scrummastertoolbox/id/42056535

The Team That Decided Sprint Goals Were Optional | Alf Dobbert-Baums 07/21/2026

The Team That Decided Sprint Goals Were Optional | Alf Dobbert-Baums Alf Dobbert-Baums: The Team That Decided Sprint Goals Were Optional 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: . "Everything was a golden route. It was kind of like a little feature factory." - Alf Dobbert-Baums Alf coached three teams. None of them cared about THE sprint goal. Most sprints had five or six "goals" — which is to say, none. The Product Owner was a proxy PO, no authority to say no, so anything that landed in the inbox got pulled into the sprint. The team had several applications to support on top of feature work. Missing a sprint goal had no consequences, so the question stopped being asked. When Alf pushed for a single, focused goal — concrete or abstract, didn't matter — the team would shrug and add three more stories to the cluster. Asked which item mattered most, they answered: "all of them." Alf names the dynamic precisely: short-term personal urgency replaced the team goal, and "all of them" became the death of focus. The cost wasn't just the missed goals — it was the missed collaboration. With a sprint goal, the team works together on one thing. Without one, they cooperate on parallel tracks and call it a sprint. There's a difference. Sprint goals create focus, predictability, and the rare feeling of finishing something together. In this segment, we talk about the difference between and why sprint goals are the lever that turns one into the other. Self-reflection Question: If you asked your team this sprint "what's the most important thing we'll finish?" — and they answered "all of them" — what would you do next? Featured Book of the Week: Humble Consulting by Edgar Schein and Don't Just Do Something, Stand There by Marvin R. Weisbord Alf gives two recommendations. The first is — "It teaches you that you don't know anything, and even if you ask, you still will not fully understand what the other person is in… But the good thing is that when you ask questions, it might help the other person to get on a different track." The second is . Alf tells a story to explain why it matters: he prepared a polished 90-minute workshop. Within 5 minutes of starting, the team's real topic surfaced — and it had nothing to do with his agenda. His head screamed "no, my workshop!" but the book gave him permission to ditch the plan, name what he was seeing, and let the team choose. They chose the new topic. He moderated. It became one of the most important sessions he ever ran. The lesson: don't just do something — stand there, and let what's really happening become visible. [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. [The Scrum Master Toolbox Podcast Recommends] About Alf Dobbert-Baums Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation. You can link with . /episode/index/show/scrummastertoolbox/id/42056955

The Two-Country Scrum Team and the Rapport That Never Showed Up | Alf Dobbert-Baums 07/20/2026

The Two-Country Scrum Team and the Rapport That Never Showed Up | Alf Dobbert-Baums Alf Dobbert-Baums: The Two-Country Scrum Team and the Rapport That Never Showed Up 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: . "It did not quite go as planned. I was really humbled." - Alf Dobbert-Baums Alf was new in the company. His boss walked over with a setup that already sounded like a warning: two development teams in two countries, two locations in Germany, a "difficult" Product Owner — and a quick "do you want to take it?" Alf said sure. Everything happened on video chat. Every meeting, every conversation, every attempt to read the room — through a window that closed the moment the call ended. The rapport never built. The PO stayed difficult. Alf eventually got pulled from the team. Looking back, he saw what the video chat had hidden: the crossed arms, the eyes drifting to email, the small in-between moments that turn coworkers into colleagues. The fix wasn't a tool — it was a flight. Visit the other location. Run a workshop with a real goal ("how do we want to work together?", "what's hard about our setup?"). Build a positive anchor before anything goes wrong, not after. And when you do go, don't lead with the failures — lead with what could be possible together. In this episode, we refer to the practice of as a way to create rapport without putting people on the defensive. Self-reflection Question: When was the last time you saw the people you work with face-to-face — and what conversations are you still postponing because they only happen well in person? [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. [The Scrum Master Toolbox Podcast Recommends] About Alf Dobbert-Baums Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation. You can link with . /episode/index/show/scrummastertoolbox/id/42056975

The Hydra Product Owner and the PO Who Made Trust Possible | Mirco Gerling 07/17/2026

The Hydra Product Owner and the PO Who Made Trust Possible | Mirco Gerling Mirco Gerling: The Hydra Product Owner and the PO Who Made Trust Possible 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: . The Great Product Owner: Precision That Builds Team Trust 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: . "He always had an answer, or if he didn't have the answer, he tried to ask the clients, the users, the stakeholders." - Mirco Gerling In pharmaceutical software, the wrong dose can kill someone. So when Mirco worked with a PO in that domain, precision wasn't a virtue — it was a survival requirement. The PO wrote meticulous user stories in classic "As a user, I want… so that…" format with very good acceptance criteria. The developers always knew what done meant. And when, mid-sprint, the team spotted a gap — "Is 80% tolerance of 100% or 80% of all?" — the PO was there, asking the right people, refining or splitting the story, never letting ambiguity ship. Even when half the team was out sick in winter, the remaining developers could deliver because the user stories were clear enough to stand on their own. Stories linked to automated tests. Each acceptance criterion traceable to the test that proved it. The result: a team that trusted their PO. As Mirco puts it, that trust came from one thing — the PO had already done the work needed to help the team understand what to do and how they'd know it was done. Self-reflection Question: What's the level of precision in your team's user stories signaling to your developers about how much you trust them — and how much you've prepared for them? The Bad Product Owner: The Hydra PO with Seven Heads 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: . "If the developers had questions, the people said: 'it's not my ticket, it's not my story.'" - Mirco Gerling Five Scrum teams. One Product Owner. Seven requirements engineers writing user stories alongside. Eight people doing the work of product ownership — and nobody owning any of it. Developers learned quickly that asking a question meant being bounced from one requirements engineer to another. "It's not my ticket." The eight-person PO group split into two sub-teams who, when they spoke about each other, used "you" and "they" instead of "we." Decisions made in week one collided with decisions made in week three. Mirco's intervention: treat the PO group like a Scrum team. Eight people is a team-sized group. Run retrospectives with them. Get them communicating as a unit instead of as parallel individuals. The one anchor that kept things from completely falling apart was the single PO at the top, who could still say "this feature we need at the end of the year, the other can wait." Without unified prioritization, the hydra has no direction — just seven heads pulling in seven ways. Self-reflection Question: Where in your product organization are decision-makers proliferating without a shared mandate — and what's the cost in clarity for the teams downstream? [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. [The Scrum Master Toolbox Podcast Recommends] About Mirco Gerling Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project. You can link with . /episode/index/show/scrummastertoolbox/id/41713730

The Silence Test — How to Know Your Team Doesn't Need You Anymore | Mirco Gerling 07/16/2026

The Silence Test — How to Know Your Team Doesn't Need You Anymore | Mirco Gerling Mirco Gerling: The Silence Test — How to Know Your Team Doesn't Need You Anymore 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: . "Don't talk too much. And only talk if it's necessary." - Mirco Gerling For Mirco, success as a Scrum Master starts with a simple rule he had to fight for: don't try to be someone else. Early in his career, when people kept saying "Mirco, you decide, you're the Scrum Master," he had to do the hard work of pushing back — "no, we decide together." That instinct shapes his whole definition of success. Be authentic. Wait before you speak. Ask before you instruct. And when a discussion stalls, sit with the silence — because in most cases, someone in the team has a better idea than you do. The cleanest test of whether a team is truly self-managing? Disappear. When Mirco took two months of parental leave, his team kept running every Scrum event without him. That's the signal. If you stop sending the sprint review invite, stop preparing the retrospective, stop nudging — and the team picks it up because they own it — your work is showing. Self-reflection Question: What's one thing you currently do for your team that you suspect they would do themselves if you simply stopped doing it? Featured Retrospective Format for the Week: 1-2-4-All from Liberating Structures Mirco's universal tool is , and within that toolbox, is his go-to. The pitch: "involve everybody, especially in large groups. And there's nearly no preparation needed." His proof point — facilitating a retrospective for 60 people at the bar camp in just 20 minutes. The format scales from a team of five to a room of sixty without changing its shape: one minute alone, two minutes in pairs, four minutes in small groups, then a share-back with the whole group. During a 30°C COVID summer in Hamburg, Mirco even ran retros walking outdoors with his team — station to station, down to the lake for ice cream, then back. "It was a very good and constructive retrospective." The lesson: the right structure makes you portable. [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. [The Scrum Master Toolbox Podcast Recommends] About Mirco Gerling Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project. You can link with . /episode/index/show/scrummastertoolbox/id/41714720

Two Teams, One Sprint Cadence — The Hidden Cost of Synchronization | Mirco Gerling 07/15/2026

Two Teams, One Sprint Cadence — The Hidden Cost of Synchronization | Mirco Gerling Mirco Gerling: Two Teams, One Sprint Cadence — The Hidden Cost of Synchronization 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: . "The teams need to understand the advantage of the synchronization — but will they?" - Mirco Gerling Two of Mirco's teams just got merged into one — and the brand-new, fused team is now part of a 10+ team organization trying to move from loose-coupled chaos to a standard process. Different sprint lengths. Different estimation methods. Different ticketing tools. The plan: align everyone to 4-week sprints, hold a global planning week every three months, and synchronize start and end dates across all teams. Mirco voted for 2-week sprints. The majority went with 4. And then the side effects started. Sprint reviews stack up on the same days, making it impossible for Scrum Masters to facilitate them all. Teams synchronize on paper, but interact organically across the four weeks anyway, so the cadence advantage doesn't materialize. And the merged team itself? Pushed back through Tuckman's stages by the merge — the reminded Mirco that "adjourning" is real, and a high-performing team starts over when its membership changes. Mirco's experiment: let faster-moving teams run two 2-week sprints inside the 4-week window, keeping organizational sync while restoring their own learning rhythm. Self-reflection Question: Where in your organization is process standardization being mistaken for actual alignment — and what would it cost you to separate the two? [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. [The Scrum Master Toolbox Podcast Recommends] About Mirco Gerling Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project. You can link with . /episode/index/show/scrummastertoolbox/id/41716755

The Supermarket Team That Self-Destructed Trying to Help Everyone | Mirco Gerling 07/14/2026

The Supermarket Team That Self-Destructed Trying to Help Everyone | Mirco Gerling Mirco Gerling: The Supermarket Team That Self-Destructed Trying to Help Everyone 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: . "They tried to help, and finally, it... it self-destructed the team." - Mirco Gerling The team was the supermarket of the organization. Cloud systems, versioning, developer machines, hardware — if another team needed infrastructure, this team built it. And when other teams asked, the answer was always the same: "We will try, we will try." Mirco watched what happened next play out in slow motion. The team escalated their overload to management. Management responded the way management often responds — sent in temporary help. The reinforcements solved problems quickly and left. But every system they built became permanent maintenance work for the original team. The pile grew. The team shrank. People left for other teams, or left the organization entirely. The escalation that was supposed to save them became the signal that broke them. As Mirco puts it: running to the higher level "sends a signal that self-organization or self-management does not work." Sometimes the help is the harm. In this segment, we refer to the dynamic of and how it can break down under pressure. Self-reflection Question: When your team is overwhelmed, what does the act of escalating tell management about your ability to self-manage — and is that the signal you want to send? Featured Book of the Week: The Kanban Maturity Model In this episode, Mirco also recommends two books that shaped his thinking on process and estimation. The first is , which inspired Mirco to drop story-point estimation in some teams and simply count completed tickets per sprint. The second is the — a book Mirco uses to run workshops where teams discover their current level of process maturity. "The highest level says that you have a standardized process, and the result is always the same for the same type of work," he explains. Most teams start at level zero, but that's the point: knowing where you stand is the precondition for knowing where to go next. [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. [The Scrum Master Toolbox Podcast Recommends] About Mirco Gerling Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project. You can link with . /episode/index/show/scrummastertoolbox/id/41716820

When the Scrum Guide Isn't the Rulebook — A Scrum Master's First Conflict with Management | Mirco Gerling 07/13/2026

When the Scrum Guide Isn't the Rulebook — A Scrum Master's First Conflict with Management | Mirco Gerling Mirco Gerling: When the Scrum Guide Isn't the Rulebook — A Scrum Master's First Conflict with Management 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: . "I had to learn that the organization didn't know the Scrum Guide very exactly." - Mirco Gerling In his first Scrum Master role — running hybrid as both developer and Scrum Master — Mirco walked in believing the Scrum Guide was the rulebook everyone played by. The team thought so too: they were self-managing now, so they would decide. Management hadn't read the same memo. When Mirco called time on a meeting, a manager said "It's my decision when the meeting is over." When Mirco asked the team if they were happy in a retrospective, the manager saw the flip chart afterward — and from that day on, Mirco started destroying anything from retrospectives that could attract attention. The conflict wasn't about Scrum. It was about who gets to decide what. Without an explicit conversation about the limits of self-management, the team and management each assumed authority the other thought was theirs. Mirco eventually found — a tool that makes those invisible boundaries visible and gives teams and managers a structured way to negotiate them. The lesson: raise the topic with management before the conflict, not after. In this episode, we refer to the . Self-reflection Question: Where in your team's work are the limits of self-management still unspoken — and what would change if you put them on the table 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. [The Scrum Master Toolbox Podcast Recommends] About Mirco Gerling Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project. You can link with . /episode/index/show/scrummastertoolbox/id/41716835

The Over-Communicator vs. The Over-Ambitious—Two Patterns Every Scrum Master Should Recognize | Aliu Adewale 07/10/2026

The Over-Communicator vs. The Over-Ambitious—Two Patterns Every Scrum Master Should Recognize | Aliu Adewale Aliu Adewale: The Over-Communicator vs. The Over-Ambitious—Two Patterns Every Scrum Master Should Recognize 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: . The Great Product Owner: The Over-Communicator Who Negotiated Every Scope Change 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: . "This is a guy who over-communicates everything." - Aliu Adewale The best Aliu ever worked with did something simple that almost no PO does. Before each refinement, he'd pull up the Jira board, record himself walking through every user story, explaining acceptance criteria, talking through the end goal one ticket at a time—and post the video to the team a day or two ahead. This was before Loom existed. The result: refinement felt less like discovery and more like "walking it back"—the team arrived already prepared, with real questions, ready to engage. He still attended every refinement and never missed a comment in Jira. But the second skill Aliu names matters even more: negotiation. This PO never let scope creep into a sprint mid-stride without consulting the team first. "If we add these two requests from leadership, what's the impact? Do we need to take something out?" And if the team said no, he didn't force it. He went back to leadership and named the consequence: "If we add this, here's what happens. Are you okay with that?" Over-communication and negotiation—two skills that protect the team and the product at the same time. Self-reflection Question: When was the last time your PO asked the team's permission before adding work mid-sprint? The Bad Product Owner: The Over-Ambitious PO Who Never Said No 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: . "Every yes to something unimportant is a no to what matters." - Aliu Adewale The Product Owner Aliu names as the anti-pattern is the —the one who never says no. Never to stakeholders, never to the business, never to a new feature request. He never considered the size of the team or the capacity of the team. He was blind to it. Underneath the behavior, Aliu sees a pattern: POs who want to keep their job by saying yes, stakeholders who keep asking because they think they have to, and a team on probation that doesn't feel safe pushing back. The damage compounds—more features delivered, less value per feature, and eventually the team itself starts to break. Aliu's framing is sharp: "More features don't equal more value. Sometimes more is just less." The job of the Scrum Master here is to coach the PO on when to say no, when to say yes, and how to recognize that on the phone in front of you right now, 90% of the features in that app you're staring at—you never use them. Built. Shipped. Ignored. In this segment, we refer to and the courage required to challenge stakeholder demands. Self-reflection Question: Is your PO measuring success by features shipped, or by features used? [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. [The Scrum Master Toolbox Podcast Recommends] About Aliu Adewale Aliu is an Agile Delivery Lead with over 10 years of experience empowering teams to unlock their potential and deliver meaningful value. As an author, Aliu simplifies Agile principles through real-life experiences, providing practical insights for professionals to apply Agile methodologies effectively in work and everyday life. You can link with Aliu Adewale on . You can also find Aliu and his book on . /episode/index/show/scrummastertoolbox/id/41801855

Success Is Living the Five Scrum Values—And Asking the Team If You Are | Aliu Adewale 07/09/2026

Success Is Living the Five Scrum Values—And Asking the Team If You Are | Aliu Adewale Aliu Adewale: Success Is Living the Five Scrum Values—And Asking the Team If You Are 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: . "Trust is the foundation of empowerment. When you trust your team, they will deliver beyond your expectation." - Aliu Adewale For Aliu, success as a Scrum Master is concrete: the team is living the —commitment, focus, openness, respect, and courage—and the organization is getting real value from their work. Commitment shows up in how the team holds itself to a Sprint goal. Focus shows up in how they protect that goal from noise. Openness reduces conflict because nothing festers in the dark. Respect, Aliu reframes powerfully: respect for someone's background comes before respect for their skill set—because in a team where people come from different countries, religions, and skill sets, that's the foundation everything else sits on. And courage shows up when a team can tell a Product Owner or a stakeholder that no, this can't be done in this Sprint, and we need to talk about it. But the values alone aren't success—the test is whether the team is delivering value frequently to the organization. The way Aliu keeps himself honest is uncomfortable but simple: he sends a survey to his team and asks them to tell him how he's doing on communication, on risk mitigation, on empowering them to reach stakeholders directly. He starts the assessment cycle the moment he joins—asking the organization what success looks like in this role in the next three months—and he refuses to "get carried away" and stop asking. Self-reflection Question: Have you ever sent your team a survey asking them to rate you—and acted on what they said? Featured Retrospective Format for the Week: Start, Stop, Continue Aliu's go-to retrospective is the classic . Three questions—What should we start doing? What should we stop doing? What should we continue doing?—and the team has the structure they need to pinpoint their own shortcomings and decide what to do about them. The reason it works so well, Aliu argues, is the psychological safety the simplicity creates. There's no jargon, no clever framework, no facilitator gimmick to hide behind. Experienced and self-organizing teams especially thrive with it because they can name what's not working without you having to call it out for them. As a Scrum Master, when your team starts pointing at their own gaps without your prompt, that's the moment you should applaud yourself—you coached them into the space where they can do it. [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. [The Scrum Master Toolbox Podcast Recommends] About Aliu Adewale Aliu is an Agile Delivery Lead with over 10 years of experience empowering teams to unlock their potential and deliver meaningful value. As an author, Aliu simplifies Agile principles through real-life experiences, providing practical insights for professionals to apply Agile methodologies effectively in work and everyday life. You can link with Aliu Adewale on . You can also find Aliu and his book on . /episode/index/show/scrummastertoolbox/id/41801875

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

TOPICS