Scrum Master Toolbox Podcast

Rajveer Prasad: Success for Scrum Masters Is the Team's Life After You Leave 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.   "If you have not helped your team move from point A to point B positively, you are just doing part of the job." - Rajveer Prasad   Rajveer defines success for Scrum Masters through the change they leave behind in the lives of the people they serve. Delivery outcomes matter, and he names lead time as a useful end-to-end metric, but he warns that numbers alone miss the deeper work. For Rajveer, success shows up in relationship signals: whether people want to have lunch with you, whether they trust you enough to help in a rare crunch without being forced, and whether they still call you after you leave the organization. Those signals matter because Scrum Masters often come from outside the technical team and must earn a place in the system. The job

Rajveer Prasad: Using Scrum Master Working Agreements to Make AI Safer 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.   "AI can put garbage in a very good wrapping and give it to you, and you're none the wiser." - Rajveer Prasad   Rajveer brings a current challenge from his own work with AI: the false sense of achievement that comes from getting a polished output before the work is truly safe, scalable, or responsible. As a non-developer building AI-supported systems, he found that an agent can quickly produce something that appears to work, while missing security, architecture, testing, or cost implications. The coaching conversation turns toward something Scrum Masters know well: working agreements. Rajveer started defining roles, values, principles, and rules for the agent, treating it like a team member that needs clear expectations. He asks the AI to explain decis

Rajveer Prasad: The Agile Team That Turned Overtime Into a Quality Problem 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.   "Working harder and working longer is not helping anyone. It's just making what we do more difficult and complex." - Rajveer Prasad   Rajveer worked with a retail organization moving into SAP HANA, with teams spread across geographies and cultures. The team wanted to help, so they worked evenings, weekends, and extra hours to keep commitments alive. At first, the organization did not demand that behavior, but once it became visible, it became the new normal. The downstream effect was predictable: bad planning, overcommitment, reduced testing, skipped regression, failed integrations, rework, and a rising defect rate. Rajveer gathered data to show the cause and effect, then worked first with leadership because expectations had already been formed ou

Rajveer Prasad: When Delivery Pressure Pulls Scrum Masters Into the Details 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.   "Failures are expected no matter when and where you are." - Rajveer Prasad   Rajveer Prasad did not plan to become a Scrum Master. He studied hospitality management and expected to build a career as a chef, but the travel and hospitality industry froze after 9/11. A survival job led him into a call-center environment, then American Express, and eventually into delivery work and Scrum training. In this episode, Rajveer shares a failure from a new product introduction where he was brought in as a consultant, expected to run the team, and slowly pulled into delivery management. The milestone plan looked reasonable, but customer collaboration was weak, dependencies were unclear, and Rajveer found himself operating at a 50-foot view when he needed to

BONUS: Breaking the Permission Loop in Agile Teams In this BONUS episode, we explore why teams often wait for permission even when they already have skill, tools, and good ideas. Tara Scott, executive, product, and culture coach and author of Breaking the Permission Loop, explains how agency starts with noticing our own reactions, building alignment, and practicing small moments of self-trust. When a Compliment Becomes a Detour "You don't really feel like you can say no. So I said yes."   Tara starts with a startup story many Scrum Masters and product leaders will recognize. She was building momentum with user research when a CEO redirected her into a data science initiative that sounded urgent, but did not answer the core product question: do people actually use this product? The request was framed as a compliment, and that made it harder to challenge. Tara's point is practical: sometimes the permission loop begins in the small space between our concern and the automatic yes that comes out before

BONUS: AI as the Third Perspective for Agile Delivery AI is already changing how agile delivery managers, Scrum Masters, and software teams handle the day-to-day work of delivery. In this BONUS episode, Rohini Prava shares how her team moved from experimenting with Cursor to using AI for practical work: bug analysis, ticket preparation, test planning, reporting, and reducing painful meetings. From Java Developer to Agile Delivery Manager "I see a good fit. And one of the scrum masters was going on holiday and I got the opportunity, I tried it, I liked it and I think I did well because I was given the role."   Rohini started her career as a Java developer in India, then moved into people management and delivery-focused work before relocating to the UK. A temporary opportunity to cover for a Scrum Master opened the door to a new direction. That experience eventually led her into the Agile Delivery Manager role, where she now leads a distributed team delivering insurance solutions. When AI Became P

BONUS: AI Makes Starting Work Easy, But Flow Still Finishes It AI is changing software teams, but Liz Rettig brings the conversation back to flow, strategy, and the discipline of finishing. In this BONUS episode, Vasco and Liz explore how Scrum Masters can use AI to make policies visible, help teams manage WIP, support Product Owners, and keep the organization focused on valuable slices instead of faster output alone. From Anthropology To Kanban And AI "As a Scrum Master, you're an anthropologist because you're watching people and you're recording how they are working."   Liz starts with her path from anthropology to Scrum Mastering, agile coaching, and professional Kanban training. That background matters because her work has always been about observing how people interact with systems. AI did not replace that skill. It made the system easier to see. In one client engagement, a team adopting an agentic framework also needed agile ways of working around that new capability. Liz saw that AI could hel

BONUS: AI Is Not Just Typing Faster With Marcus Hammarberg In this BONUS episode, Vasco Duarte and Marcus Hammarberg explore what changes when AI agents move from writing small functions to creating whole features, running through tickets, and even improving their own instructions. The conversation keeps coming back to a simple but difficult question: if agents make software delivery faster, what should humans use that speed for? When the Agent Writes the Feature "What I realized was that the agent could now write the code from a prompt that I gave it, and it was good enough that I didn't have to touch a lot of it."   Marcus starts with the moment that changed his own practice: in December 2025, he used an AI agent to build a feature for a flow metrics app based on Jira change logs. Before that, AI coding felt like asking for small functions and then cleaning up the result. This time, the agent could take a feature-level prompt and produce something useful. That shifted the question from "can AI hel

BONUS: AI in the SDLC Puts Customer Feedback Before Faster Typing AI is already changing software development, but David Mantica argues that the real shift is not only in code generation. In this BONUS episode, Vasco and David talk about what happens when AI enters the whole software development life cycle: executive decision-making, Scrum Master work, product feedback, data quality, agentic systems, and the human skill of learning to adapt. From Executive Curiosity to Real AI Use Cases "You have two directions you can go with AI. One is productivity. The other part of AI that organizations haven't quite tapped into yet is how do you make money with it?"   David describes AI adoption as something that, like agile and AWS before it, often starts in the middle of the organization before executives fully understand what is happening. Early conversations were about policy, regulation, and tool choices. Now, the conversation has moved toward use cases: where GenAI helps personal productivity, where agent

BONUS: The Scrum Master's AI Prompt Library, with Joshua McDonald In this BONUS episode, Joshua McDonald shares how he uses AI in the daily work of a Scrum Master, from team summaries and leadership updates to retrospectives and coaching preparation. The conversation is practical and grounded in one clear warning: AI can give Scrum Masters time back, but it cannot replace their judgment. When AI Stops Being a Toy and Starts Saving Real Time "It would have to be when it started to save me about one to two hours per day."   Joshua's turning point came when AI moved from curiosity to practical assistant. He began using tools like Microsoft Copilot to analyze reports, prepare communication, and package updates for different audiences. The value was not that AI did the thinking for him. The value was that it helped him reach useful coaching conversations faster, especially when working with reports on predictability, volatility, and cycle time. Turning Flow Data Into Better Coaching Conversations "

Kaloyan Chalakov: Great Product Owners Start the Conversation Instead of Becoming the Boss In this episode, we refer to Product Owner anti-patterns and team and PO collaboration. The Great Product Owner: Open Communication, Active Listening, and Feasibility First Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Start the open conversation and listen to the critical discussions." - Kaloyan Chalakov   Kaloyan describes the best Product Owner pattern as almost the opposite of control. A strong Product Owner comes to the team with the outcome, the timeline, and the stakeholder context, then starts a feasibility conversation. They ask what is possible, what is risky, what can be decomposed, and what the team needs in order to deliver. In Kaloyan's example, the Product Owner stayed focused on stakeholder communication while the team helped shape the work into somethi

Kaloyan Chalakov: Building Scrum Master Success Around Trust and Unspoken Leaders Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success for me is making myself obsolete in the team." - Kaloyan Chalakov   Kaloyan defines Scrum Master success in a way that sounds funny at first: forty hours a week to drink coffee and do nothing. But the point is serious. Success means the team no longer needs the Scrum Master for every decision, question, or conflict. They are self-organizing, self-managed within their context, and able to call for help only when it really matters. When Kaloyan joins a new team, he avoids setting big targets in the first three months. He observes, builds trust, and watches for what the team does not show openly. One of his key signals is the presence of "unspoken leaders," the people the team looks to when something difficult happens. He learned that

Kaloyan Chalakov: Coaching Organizations to Challenge the Beliefs Behind Agile Pressure Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "What's happening with the team is just the symptom of what's happening with the whole system." - Kaloyan Chalakov   Kaloyan brings a common Scrum Master challenge: a team under pressure from a Product Owner who starts acting more like a project manager. Planning turns into a list of tasks, Daily Scrum becomes a status report, and pressure flows from customers and market competition, through management, to the Product Owner, and finally to the team. In the conversation, Vasco and Kaloyan map the system and notice something deeper than pressure: the belief that a competitor's release will directly damage the company unless the team moves faster. That belief becomes the real intervention point. Kaloyan reflects that Scrum Masters can ch

Kaloyan Chalakov: The Agile Team That Built Great Architecture But Forgot the Customer Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "You don't have to build it only because we can. We need to lead to a purpose." - Kaloyan Chalakov   Kaloyan worked with a technically strong team that could build impressive architecture, pipelines, and infrastructure fast. Sprint after sprint, they showed the quality of the technical system they were creating. But the hard question stayed unanswered: what customer problem were they solving? The wake-up moment came in a sprint review, when a client finally joined and told the team that the network and architecture were nice, but they did not solve the actual problem. The customer needed one small piece of functionality, and the team could not point to it. The room went silent. The Product Owner felt exposed, the team felt embarrassed,

Kaloyan Chalakov: When Textbook Scrum Hurt the Team, Learning to Adapt as a Scrum Master 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.   "It doesn't matter if it works for you. The most important thing is that it doesn't work for me." - Kaloyan Chalakov   Kaloyan Chalakov came into Agile after years in safety-critical environments, where control and preparation mattered. That background helped him, but it also created his first big Scrum Master trap: trying to be the "perfect" Scrum Master from the books. He pushed two-week sprints, events, and practices because that was how Scrum was supposed to work. Then one team member pulled him aside and told him the truth: the process did not work for him. Kaloyan's first reaction was defensive, because his pride was hurt. But that feedback became a signal. He started using that team member as a barometer for whether the change

BONUS: The Chip Race Behind AI With Rakesh Kumar AI feels like a software revolution, but Rakesh Kumar argues that the next limits may come from chips, energy, and the physical systems underneath our code. In this BONUS episode, Rakesh explains why AI progress is tied to hardware, what software teams need to relearn about efficiency, and why the economics of data centers should matter to product leaders. Why Chips Became a Society Topic "The race about AI essentially becomes the race about chips."   Rakesh traces his path from a small town in India to computer science, chip research, entrepreneurship, and eventually writing The Chip Age. The turning point came during the COVID-era chip shortages, when cars, appliances, and everyday electronics became harder to buy. That moment made chips visible to people outside engineering. AI then raised the stakes further: the promise of new medicines, new materials, and major productivity gains depends on models that require enormous amounts of computation. Fo

Marcin Klimaszewski: The Product Owner View of Great Scrum Masters in Agile Teams In this episode, we refer to Design Thinking, Product Build Day, and The Mom Test by Rob Fitzpatrick. The Great Product Owner: A Scrum Master Who Knows When to Step Into Product Work 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 skill of a great Scrum Master is being flexible with the role." - Marcin Klimaszewski   Because this is a Product Owner week, Marcin closes the week by describing what great Scrum Masters look like from the product side. The key word is flexibility. A great Scrum Master protects team rhythm and alignment, but also understands when the team needs something outside the textbook process. Marcin shares the example of a product or epic kickoff where the Scrum Master worked with the Product Owner and Product Designer to create a useful workshop. The team

Marcin Klimaszewski: Product Owner Ownership That Gives Agile Teams Real Direction 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.   "Ownership is one of the most important things, and knowing how to hold this ownership." - Marcin Klimaszewski   Marcin defines Product Owner success through ownership. The word is in the title, but in many organizations the role is not actually given the authority, clarity, or support needed to make decisions. A successful Product Owner protects the team from conflicting stakeholder pressure, becomes a reliable decision point, and gives the team a clear sense that product decisions will lead somewhere. Marcin shares a Product Build Day example where a founder entered the day with a clear statement: the prototypes and tests would inform real product direction, not become a fun internal exercise. That clarity changed the team's energy. Peop

Marcin Klimaszewski: Product Owner Discovery When Agile Stakeholders Want Delivery First Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "If I can ship everything by the weekend, what is worth shipping?" - Marcin Klimaszewski   Marcin's current challenge is one many Product Owners recognize immediately: convincing stakeholders to invest time and money in discovery. Everyone says they want to understand the customer, but when discovery becomes real work, the pressure returns to plans, backlogs, and delivery. Marcin points to the Double Diamond design process as a useful way to explain the work. The first diamond explores problems and decides which problem deserves attention. The second diamond explores solutions. Many companies rush into the second diamond and become feature factories. The backlog is already large, stakeholders already have promises, and discovery c

Marcin Klimaszewski: The Product Owner Lesson From Agile Teams That Forget 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: http://bit.ly/SMTP_ShowNotes.   "The user never wants to log in. That is never the goal of the user." - Marcin Klimaszewski   Marcin describes a pattern he has seen too often: teams speak about users as if the team already knows what users need. In one EdTech example, the obvious solution looked simple from the development side: students should log in. But in a classroom with twenty or thirty students and only forty-five minutes, login was not a neutral feature. A few forgotten passwords, a few typos, and the teacher suddenly became an administrator instead of a teacher. The Product Owner needed the team to see the real problem, not just the technically familiar solution. The eventual answer was simpler for the users: the teacher logged in and shared a code with the stu