sprint review Archives - Scrum Master Toolbox Podcast

Alf Dobbert-Baums: Success Is When the Team Gets Closer to the User

“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 Shift: From Product to People 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 Prime Directive, 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.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

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 Alf Dobbert-Baums on LinkedIn.

Nigel Baker: Why Scrum Masters Should Be Measured on Outcomes, Impacts, and Team Happiness

“No customer’s going to come to you and say, do you know why I bought your product? Your remarkable compliance with your internal development process. What they’re interested in is outcomes and impacts.” – Nigel Baker

Nigel challenges the traditional ways of measuring Scrum Master success. He points to tools like the Nokia test—which, he jokes, was neither a test nor invented by Nokia—as examples of process fidelity assessments that miss the point entirely. Compliance with a process tells you nothing about whether customers are satisfied or whether the team is delivering value. Instead, Nigel argues for measuring Scrum Masters on outcomes and impacts: customer satisfaction, revenue generation, and efficiencies—the same things a Product Owner gets judged on.

But he adds a crucial dimension that POs often overlook: team happiness. Not as an end goal, but as a leading indicator. Happy teams don’t leave. Happy teams do better work. Team contentness is a KPI that signals whether the deeper success factors are in place. When your team is deeply unhappy, no amount of velocity or story completion will save you from attrition and decline.

Self-reflection Question: How are you currently measuring your success as a Scrum Master—on process compliance, or on the outcomes, impacts, and wellbeing your team actually delivers?

Featured Retrospective Format for the Week: Keep It Fresh—A Different Format Every Sprint

Nigel’s answer to the “favorite retrospective format” question is deliberately controversial: he doesn’t have one. His approach is to use a different format every single sprint. Retrospective formats, he argues, “age like milk”—by Sprint 12, asking “what should we do differently?” with the same structure produces diminishing returns. Novelty creates energy. He sometimes gets teams to invent their own formats, which produces some of the most forensic and intense retrospectives he’s seen—teams building “superweapons” and then realizing they have to turn those weapons on themselves. But Nigel’s most practical tip is using retrospective techniques inside the Sprint Review. The Review is a product retrospective, and stakeholders shouldn’t sit “like Roman emperors in the Colosseum, watching the developers as gladiators.” Instead, use facilitation methods to extract “sweet, juicy, honey-flavoured feedback” from stakeholders about what they’d change in the product.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Nigel Baker

Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.

You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.

Alex Sloley: How to Coach Product Owners Who Treat Developers Like Mindless Robots

In this episode, we refer to the previous episodes with David Marquet, author of Turn the Ship Around!

The Great Product Owner: Trust and the Sprint Review That Changes Everything

“She was like, oh my gosh, I’ve never seen this before, I didn’t think it was possible. I just saw you deliver stuff in 2 weeks that I can actually use.” – Alex Sloley

In 2011, Alex worked with a client organization creating software for external companies. They needed a Product Owner for a new Agile team, and a representative from the client—who had never experienced Scrum—volunteered for the role. She was initially skeptical, having never witnessed or heard of this approach. Alex gently coached her through the process, asking her to trust the team and be patient. Then came the first Sprint Review, and everything changed. For the first time in her career, she saw working product delivered in just two weeks that she could actually touch, see, and use. Her head exploded with possibility. Even though it didn’t have everything and wasn’t perfect, it was remarkably good. That moment flipped a switch—she became fully engaged and transformed into a champion for Agile adoption, not just for the team but for the entire company. Alex reflects that she embodied all five Scrum values: focus (trusting the team’s capacity), commitment (attending and engaging in all events), openness (giving the new approach a chance), respect (giving the team space to succeed), and courage (championing an unfamiliar process). The breakthrough wasn’t about product ownership techniques—it was about creating an experience that reinforced Scrum values, allowing her to see the potential of a bright new future.

Self-reflection Question: What practices, techniques, or processes can you implement that will naturally and automatically build the five Scrum values in your Product Owner?

The Bad Product Owner: When Control Becomes Domination

“They basically just owned the team. The developers on the team might as well have been mindless robots, because they were being assigned all the work, told how much work they could do in a sprint, what the work was.” – Alex Sloley

In 2018, while working with five interconnected Product Owners, Alex observed a Sprint Planning session that revealed a severe anti-pattern. One Product Owner completely controlled everything, telling the team exactly what work they would take into the Sprint, assigning specific work to specific people by name, and dictating precisely how they would implement solutions down to technical details like which functions and APIs to use. The developers were reduced to helpless executors with no autonomy, while the Scrum Master sat powerless in the corner. Alex wondered what caused this dynamic—was the PO a former project manager? Had the team broken trust in the past? What emotional baggage or trauma led to this situation? His approach started with building trust through coffee meetings and informal conversations, crucially viewing the PO not as the problem but as someone facing their own impediment. He reframed the challenge as solving the Product Owner’s problem rather than fixing the Product Owner. When he asked, “Why do you have to do all this? Can’t you trust the team?” and suggested the PO could relax if they delegated, the response was surprisingly positive. The PO was willing to step back once given permission and assurance. Alex’s key lesson: think strategically about how to build trust and who needs to build trust with whom. Sometimes the person who appears to be creating problems is actually struggling under their own burden.

Self-reflection Question: When you encounter a controlling Product Owner, do you approach the situation as “fixing” the PO or as “solving the PO’s problem”? How might this reframe change your coaching strategy?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Alex Sloley

Alex believes that a great Scrum Master can have a long and lasting impact on people and teams. He is a global agile and product management evangelist, author of The Agile Community, and frequent international speaker. A former Microsoft leader with 15 years’ experience, he now trains, coaches, and drives transformations worldwide. Certified across Scrum, ICAgile, and Kanban, Alex energizes communities, guides leaders, and—yes—enjoys good beer.

You can link with Alex Sloley on LinkedIn.

Chrissy Fleming: From Tasks to Outcomes, An Agile Cultural Transformation Story

Chrissy shares her experience transforming a sales-led organization from task orientation to outcome focus. By partnering with the head of tech and implementing OKRs, they created meaningful conversations about team goals and progress. Through initiatives like Demo Days and the creation of team “houses,” they successfully shifted the organizational culture while ensuring teams felt ownership of their future.

Self-reflection Question: How can you create meaningful opportunities for your teams to shape their own identity and future?

The Scrum Master Toolbox Podcast Recommends…

🔥 In the ruthless world of fintech, success isn’t just about innovation—it’s about coaching! 🔥

Angela thought she was just there to coach a team. But now, she’s caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn’t just about the product—it’s about the people.

🚨 Will Angela’s coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

The Scrum Master Toolbox Podcast Recommends…

About Chrissy Fleming

Chrissy came to Scrum-Mastering via Product Management and a deep love of seeing teams work together. She spent 15 years in the New York tech scene and is currently an Associate Principal in Business Agility with Turnberry Solutions. She also has her own company where she coaches and helps businesses and technologists with their development.

You can link with Chrissy Fleming on LinkedIn.

Ruta Hardikar: The Product Owner that skipped the Sprint Reviews, and what that caused for the Scrum team

The Great Product Owner: The Customer advocate Product Owner

This Product Owner was very close to the customer, and listened to their needs as well as the struggles they had with the product. Through their work, the PO tried to focus on adding to the backlog stories that would help the customer directly, and would often act as the customer when talking to the team. They were able to focus on prioritization, and prioritized the work for the team. The PO was also able to create clear priorities and have conversations with the team about the 3 V’s: Vision, Value, and Validation.

The Bad Product Owner: The Product Owner that skipped the Sprint Reviews, and what that caused for the Scrum team

The processes we have in place influence the choices, and the focus of the Product Owners. In this segment, we talk about a team and their Product Owner that did not host a Sprint Review. Instead, the PO would focus on reviews with individuals, separate discussion with single stakeholders. However, that meant that other stakeholders would not know what the team had worked on during the Sprint. Furthermore, the team was not involved, and did not have the chance to show, and be proud of what they had accomplished during the Sprint. This was an anti-pattern that Ruta tried to overcome. Listen in to learn how Ruta tackled this anti-pattern.

Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Ruta Hardikar

Ruta has over 8 years experience with Agile, and has taken the roles of Agile Coach, Scrum Master, Release Train Engineer (RTE in SAFe), working with GM Financial.

You can link with Ruta Hardikar on LinkedIn.