Scrum Master Toolbox Podcast

Oluyomi Emmanuel: Product Owners Who Turn Feedback Into Agile Team Learning The Great Product Owner: Listening, Investing, and Learning With the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A great product owner is not the person with all the answers. It is the person who creates access to the right evidence." - Oluyomi Emmanuel   Oluyomi shares the example of a Product Owner whose strongest habit was asking the team for feedback, listening without defending himself, and then acting on what he heard. In one sprint review, the team looked at internal metrics and raised a difficult concern: they were completing work, but it did not always seem closely connected to what customers needed. The Product Owner could have defended the roadmap or blamed incomplete metrics. Instead, he treated the feedback as evidence worth investigating. He secured a training budget

Oluyomi Emmanuel: Constructive Independence as a Scrum Master Success Metric Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success is when the team increases its capacity to notice, discuss, and solve the problems that stand between them and meaningful outcomes." - Oluyomi Emmanuel   Oluyomi's definition of Scrum Master success has changed over time. Today, he measures success by the team's growing ability to notice, discuss, and solve the problems that stand between them and meaningful outcomes. One practical signal is when someone in the team says or does something he would previously have needed to prompt: a developer challenges an unclear requirement, a tester raises a risk before anyone asks, or a team member names a problem directly. Oluyomi calls the strongest indicator "constructive independence." That does not mean the team no longer needs support. It mean

Oluyomi Emmanuel: Creating Agile Value Stream Visibility Without More Administration Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Transparency is not created by displaying more information. Transparency is created when people share enough meaning to interpret that information in the same way." - Oluyomi Emmanuel   Oluyomi's current challenge is helping an organization create end-to-end visibility and ownership across several value streams without turning the solution into another layer of administration. At first, the problem looked like a Jira hierarchy issue: initiatives, epics, stories, and tasks needed shared definitions. But the conversations exposed something deeper. Different groups used the same work item names to mean different things, and those differences made prioritization, dependency management, coordination, and reporting harder. Together with a col

Oluyomi Emmanuel: From My Task to Our Work in Agile Teams Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "We shifted their thinking from my task to our work." - Oluyomi Emmanuel   Oluyomi describes a destructive pattern many Scrum Masters will recognize: local responsibility inside a supposedly shared team. The team looked collaborative during Scrum events, but once the meetings ended, developers, testers, and reviewers behaved like separate specialists. Developers finished coding and moved on. Testers waited for the right context or environment. Pull requests sat in review. Everyone looked busy, and everyone could explain their own behavior, but work was not reaching Done. The board already showed the queues, yet visibility alone did not change behavior because the team still spoke in individual language: "my development is finished," "testing belongs to QA," and "m

Oluyomi Emmanuel: When Agile Team Trust Breaks Before the Scrum Master Acts Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Once that trust is broken, everything else, nothing else matters." - Oluyomi Emmanuel   Oluyomi Emmanuel started his Scrum Master journey after a strategic move toward Agile ways of working changed his project coordinator role into something deeper: helping people communicate when the answers were unclear. In this episode, he shares a hard lesson from a newly formed software team of eight people, where tension between a tech lead and a new developer first appeared in GitHub pull request comments. There were sarcastic replies, cameras switched off during the daily standup, and a growing distance when the team worked in the same office. Oluyomi initially treated it as a normal forming-stage conflict and waited for the team environment to absorb th

BONUS: Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani AI is changing the work of software teams, but Salima Bhimani argues that the bigger question is not only what AI can automate. In this BONUS episode, Salima shares what she learned inside Alphabet's moonshot ecosystem, why breakthrough ideas may be hiding in plain sight, and how more people can become moonshot makers when technology meets lived intelligence. Invention Starts in Real-World Constraints "Invention is something that is always happening in relationship to something that's in the world."   Salima traces her view of invention back to a family history of migration, adaptation, and rebuilding under constraints. Her roots go from India to East Africa, where her family had to learn new languages, new land, and new ways to survive. That experience shaped a practical view of innovation: invention is not only the work of a lone genius in a lab. It often starts in friction, necessity, and the daily encounter between people

Pankaj Kumar: Product Owners Who Prepare the Ground for Agile Teams The Great Product Owner: Proactive Preparation Before the Team Asks Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Before the team asks, you know that this is the prerequisite for this user story." - Pankaj Kumar   Pankaj's example of a great Product Owner is someone who did the homework before meeting the team. This PO understood what the team needed to deliver, prepared the acceptance criteria, talked to UX early, and made sure design inputs were available before developers were blocked. Vasco describes this as "preparing the ground" for the team. The PO was not just pushing features into a sprint. He was listening to what the team could achieve, translating stakeholder needs into clearer work, and reducing waiting time so the team could focus on execution. For Scrum Masters, this is a useful pa

Pankaj Kumar: The Scrum Master Success Metric of Team Independence Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "The best thing to measure the success of a Scrum Master is that the team is not dependent on the Scrum Master." - Pankaj Kumar   For Pankaj, Scrum Master success has a clear test: can the team work, decide, inspect, and improve without depending on the Scrum Master for every step? He looks for self-organization, confidence in Scrum events, and a team that can continue improving without constant intervention. But he does not rely only on impressions. Pankaj uses team metrics such as velocity, backlog health, lead time, cycle time, and Cumulative Flow Diagrams when Kanban is in use. He also pays attention to team satisfaction and regular feedback. The frequency of that reflection depends on team maturity. Mature teams may need a two-week check-in rhythm, w

Pankaj Kumar: Using Agile Prioritization to Handle Competing Roles Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Who am I going to deliver to, and how urgent is this task for them?" - Pankaj Kumar   Pankaj's current challenge will sound familiar to many Scrum Masters and Product Owners: too many important demands, all arriving at once. He runs his consultancy, Test2Deploy, works with a startup, serves as a board member in Agile Finland, and is also building a healthcare app. The problem is not motivation. The problem is deciding what deserves attention when everything looks valuable. Pankaj uses a simple prioritization matrix built around value and importance, then adds practical filters: deadline, effort, risk, impact, stakeholder, and the stage of the work. Is it still planning? Is it in execution? Can it be delegated? Can it be removed? Vasco connects this perso

Pankaj Kumar: The Agile Team Split Between Seniors and Juniors Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "We have to focus not on individual tasks, but the team goals. Shared goals." - Pankaj Kumar   Pankaj describes a team that had all the ingredients for friction: senior people with deep experience, junior people who needed support, and a Sprint Goal that required everyone to move together. The weak signal showed up in the retrospective. The junior team members were quiet, and the seniors were implicitly treating mentoring as work that did not help them. Pankaj started with one-on-one conversations to understand what was behind the silence. Then he reframed mentoring around the team outcome. The senior people were not being asked to "lose time" helping juniors. They were being asked to build the capability the whole team needed to deliver. He also pointed out

Pankaj Kumar: Building Agile Trust One Small Scrum Sprint at a Time Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "We are here to learn. Learning is the key." - Pankaj Kumar   When Pankaj Kumar first moved from QA lead into the Scrum Master role, the organization was also moving from waterfall into Scrum. The team had been used to long project cycles, and suddenly they were being asked to deliver working software every two weeks. The difficult part was not the process language or the events. It was the fear behind the change. Pankaj saw that the team needed trust before it could take the first real step. He started with one-on-one conversations, made the pilot explicit, and kept bringing people back to a shared outcome instead of individual tasks. The breakthrough came when the team stopped trying to prove that "Scrum works" all at once. Instead, they picked small p

BONUS: Why AI Is Agile's Best Use Case With Melissa Reeve AI is often framed as a technology rollout, but Melissa Reeve makes a different case: organizations that already know how to learn, adapt, and improve are better prepared for AI. In this BONUS episode, we connect Lean, Agile, DevOps, and AI-native work, and explore why Scrum Masters may be closer to the center of AI adoption than they think. From Toyota Production System to AI-Native Work "I didn't really have words for what would later be my career. I didn't know about systems thinking. I didn't know about this thing called Agile."   Melissa traces the through-line from studying the Toyota Production System in Tokyo, to early Agile marketing, to developing intellectual property at Scaled Agile, and finally to AI. Her point is that Lean, Agile, and AI-native work are not separate conversations. They all depend on sensing what is happening, shortening feedback loops, learning from reality, and improving the system instead of only optimizin

BONUS: Real-Time Research for Change Leaders Using AI AI is changing how Scrum Masters, Agile coaches, and change leaders make sense of organizations. In this BONUS episode, Ari-Pekka Skarp shares how he uses AI as a research assistant, a workspace partner, and a way to bring qualitative research into day-to-day change leadership. From Curiosity to Research Assistant "It felt like having a research assistant."   Ari-Pekka's first serious AI use did not start in his full-time change leadership role. It started with side projects, research, psychotherapy-related work, and watching his son build websites with Lovable. That curiosity became practical when Ari-Pekka began using AI to support his PhD research. Instead of spending a full day scanning articles, he could find relevant sources, generate useful summaries, and decide where to go deeper in about half an hour. The key was not that AI replaced his judgment. Because he already knew the research area, he could evaluate the quality of what the AI re

BONUS: From AI Curiosity to Practical Project Tools With William Davis AI becomes useful when it moves from generic answers into the daily work of solving real problems. In this BONUS episode, William Davis shares how he started building his own AI-assisted project management tools, what went wrong when the code grew too fast, and how Scrum Masters can use AI more carefully at individual, team, and project levels. When AI Stops Being a Curiosity "I really need to get a handle on how to productively use AI in my job."   William's shift started with a familiar problem: release plans are full of uncertainty, but stakeholders still need to understand what might happen and when. Instead of handcrafting uncertain delivery ranges in Excel, William used AI to build a desktop application that created probabilistic Gantt charts. In his work, these were not traditional command-and-control schedules. They were release plans that showed stakeholders a realistic range of possible delivery dates, making uncertaint

BONUS: How Scrum Masters Can Use AI Without Losing the Human in the Loop AI makes it easier than ever to build software, prototypes, courses, and coaching tools. In this BONUS episode, Mike Lyons and Greg Pfister share what that speed changes for Scrum Masters, why product judgment becomes more important, and how coaches can start using AI without outsourcing the conversations their teams still need. When AI Stops Being a Curiosity and Starts Saving Real Time "It's not that the work is wrong or not needed, it is needed. That's an important step. Retrospectives are critical."   Greg's first practical AI moment came while trying to build an "Ask Mike" capability for self-paced courses. After a frustrating outsourcing attempt, he started using ChatGPT to help him rebuild the tool himself, eventually moving into Cursor, Claude Code, and the Superpowers plugin for Claude Code. Mike's moment was less technical: using AI inside Mural to affinity-map retrospective notes. The lesson for Scrum Masters is not

BONUS: The Hidden Dangers of AI at Work With Ari-Pekka Skarp AI is usually sold as a productivity tool, but Ari-Pekka Skarp argues that the real story is what it does to the conversations, skills, and purpose that hold teams together. In this BONUS episode, Ari-Pekka explores why organizations are rushing to use AI "as efficiently as possible" without defining what efficiency means, and what that rush is quietly costing us. Organizations Are Conversations "The organizations are actually conversations, conversational patterns between people."   Ari-Pekka's path from software engineering in 1999 to psychology, psychotherapy, and change leadership was driven by one thread: how the mind works, both individually and socially. Meeting Ralph Stacey, Esko Kilpi, and Douglas Griffin at Nokia changed how he saw organizations. Instead of a machine made of parts, an organization is a living pattern of conversations — people responding to each other's gestures, again and again. George Mead added the idea that th

Deborah Colombari: Product Owners Who Protect Focus and Enable Ownership In this episode, we refer to INVEST criteria and Behavior Driven Development. The Great Product Owner: Clear Outcomes, Strong Refinement, and Space for the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "He doesn't say how. That allows the team to own the solution." - Deborah Colombari   Deborah describes a great Product Owner who came from project management, but learned to work deeply with upstream discovery and refinement. This PO uses INVEST criteria, Behavior Driven Development-style acceptance criteria, and explicit policies so that developers understand what needs to be done and why. He writes down expected outcomes at the epic and feature level, not only at the story level. Because he does not have a developer background, he depends on the tech lead, and Deborah sees that as

Deborah Colombari: Stable Agile Teams Make Delivery Predictable Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "When I have a stable team, I have reliable data." - Deborah Colombari   For Deborah, success as a Scrum Master comes down to one word: stability. A stable team communicates better, shares knowledge, avoids hero-driven delivery, and becomes predictable enough that the Scrum Master can use historical data instead of wishful thinking. Deborah connects stability with flow metrics and statistical thinking. When an expedite request appears, a stable team can look at its own history and forecast with a useful level of confidence. An unstable team, by contrast, creates silos, overloads key people, and turns every new request into a crisis. Vasco connects Deborah's answer to systems thinking and statistical process control: the team is part of a wider system, and it

Deborah Colombari: Coordinating Global Agile Teams Around One MVP Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "The scope is clear. How we are going to deliver it is not clear." - Deborah Colombari   Deborah brings a live challenge from a new global project. Her team carries the deadline, but three other teams must contribute, and those teams do not share the same priority or urgency. The question becomes: how do you align teams when only one of them feels the pressure? Deborah has already tried management alignment meetings, but they have not worked as well as needed. Her next experiment is a one-week workshop inspired by Lean Inception, where managers and teams can write down what is needed, when it is needed, and what each team can realistically contribute. Vasco and Deborah explore three practical moves: define the MVP as a real vertical slice, ask whether a pe

Deborah Colombari: The Agile Team Destroyed by a Toxic Feedback Loop Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Whenever we almost started to achieve norming, we went back to storming." - Deborah Colombari   Deborah shares the story of a team of about twelve developers and QA specialists that kept losing people one by one. The early signal was not a technical problem. It was turnover. A toxic direct leader created pressure, blame, and snarky responses whenever the team tried to explain what was happening. Because that leader's own manager behaved the same way, Deborah saw a reinforced pattern rather than an isolated personality problem. The team could not stabilize. Every time it moved toward norming, someone left or someone new arrived, sending the team back into storming. Knowledge walked out the door with the people who left, delivery dates slipped, morale dr