sprint goal Archives - Scrum Master Toolbox Podcast

Alf Dobbert-Baums: The Team That Decided Sprint Goals Were Optional

“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 cooperation and collaboration 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 Humble Consulting by Edgar Schein — “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 Don’t Just Do Something, Stand There by Marvin R. Weisbord. 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.

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.

Efe Gümüs: The People-Pleasing Product Owner and the PO Who Understood User Value — Two Sides of Product Ownership

The Great Product Owner: The PO Who Understood User Value

“If your product owner can phrase what the user wants to do — not what the button should look like — it is going to be a night and day difference.” – Efe Gümüs

Efe describes the great product owner as someone who creates focus and a clear product vision, so the team knows what they’re building and why. The foundation is simple but powerful: describe what the user will be able to do, not what the interface should look like. Instead of specifying a red subscribe button with exact text in three languages, say “as a user, I want to subscribe to my favorite channel.” That shift unlocks the team’s ability to contribute design insights, architecture decisions, and user journey thinking — the kind of expertise no product owner could anticipate alone. Efe highlights the SPIDR slicing method as one of his favorite tools for breaking product backlog items into consumable pieces — by interface (iOS, Android, web), by data, by rules. When the PO frames work around user value and slices it effectively, the team delivers visible value in iterations, and sprint goals become meaningful. Without this, the team becomes a ticket delivery machine.

Self-reflection Question: When you look at your product backlog right now, are items described in terms of what users can do — or in terms of what the interface should look like?

The Bad Product Owner: The People-Pleasing PO Who Says Yes to Everything

“If you are doing everything your customer says, then you are not managing your product. That’s the foundation.” – Efe Gümüs

Efe names people-pleasing as the worst product owner anti-pattern — the “customer is always right” mentality applied to product management. When a PO says yes to every request, the consequences cascade quickly: multiple priorities competing simultaneously, everything marked urgent, no meaningful sprint goal, constant context switching, and new items injected mid-sprint.

The team loses focus entirely. Efe has seen this in startups where the CEO walks in with urgent customer requests, and in larger organizations where multiple customers each demand customizations. In both cases, the PO becomes a pass-through instead of a decision-maker. The customer might be happy today, but will they be satisfied in six months when nothing is coherent?

As Vasco notes, when you’re serving multiple customers and saying yes to one, you’re saying no to all the others — you just haven’t told them yet. The result is chaos: steering blindfolded without navigational tools, trying to go everywhere at the same time. A product owner’s most important skill is coherent, aligned decision-making — and that means learning to say no.

In this episode, we talk about Efe’s blog post on how to use Scrum in your hobby activities.

Self-reflection Question: How often does your product owner say no to stakeholder requests — and when they do say yes, is it because the request aligns with the product vision or because they want to avoid conflict?

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

About Efe Gümüs

Efe is an out-of-the-box Agile Coach and Scrum Master who brings fresh perspectives to Agile by connecting it with everyday life. He uses metaphors to reveal mindset patterns and applies continuous feedback loops beyond work, including music production and gym training, constantly refining performance, creativity, and personal growth and resilience.

You can link with Efe Gümüs on LinkedIn.

BONUS: Challenging the Agile Status Quo with #NoBacklogs, Allan Kelly

In this BONUS episode, we explore the provocative ideas of Allan Kelly, the author who introduced #NoBacklogs to the Agile community. Allan shares his insights on why traditional backlogs may be hindering true agility, offers practical alternatives, and explains how teams can maintain accountability while focusing on outcomes rather than outputs.

The Problem with Traditional Backlogs

“Backlogs keep ideas for far too long.”

Allan Kelly challenges the conventional wisdom of maintaining extensive backlogs in Agile environments. He distinguishes between sprint backlogs and product backlogs, highlighting how the latter often becomes a repository for stale ideas that outlive their relevance. Allan argues that this practice undermines the adaptability that should be at the core of Agile methodologies, transforming what should be a flexible approach into a more rigid, traditional project management framework.

Outcome-Focused Alternatives

“What are you doing to try and change the world?”

Instead of lengthy backlogs filled with specific tasks and features, Allan advocates for approaches centered on outcomes and meaningful change. He discusses the concept of OKRs (Objectives and Key Results) as a form of “test first management” – a powerful framework that shifts focus from outputs to measurable impacts. This perspective encourages teams to consider the broader purpose of their work rather than simply executing a predetermined list of tasks.

Balancing Structure and Flexibility

“There should be a ‘Best before’ date for all backlog items.”

Finding the right balance between necessary structure and agile flexibility is crucial for effective delivery. Allan suggests implementing a “best before” date for all backlog items to prevent the accumulation of outdated ideas. He emphasizes starting with the Sprint Goal as a guiding principle, using it to create focus and purpose that allows teams to adapt their approach while maintaining a clear direction.

Breaking Free from Traditional Mindsets

“The work to do is not a fixed entity.” Continue reading BONUS: Challenging the Agile Status Quo with #NoBacklogs, Allan Kelly

Kevin Hoey: Two Scrum Master Critical Tasks: Measuring Value Delivery in Agile Teams, And Aligning With Stakeholders

When it comes to success for scrum masters, Kevin focuses on people-centric approaches, continuous improvement, and value delivery. He emphasizes aligning with stakeholders’ goals and measuring outcomes. Kevin discusses the importance of having a product roadmap and vision, conducting health checks, and striving for daily improvement. Removing unnecessary steps and making processes more efficient are key to achieving better outcomes for the team and the business.

Featured Retrospective Format for the Week: Order Stories by Cycle Time

Kevin emphasizes the necessity of retrospectives, especially for teams that claim to be too busy. He discusses the anti-pattern of avoiding retros, highlighting the benefits of examining sprint goals and reinforcing what works well. Kevin suggests periodically reviewing stories by cycle time to identify and address delays, ensuring continuous improvement in handling challenging tasks.

Kevin also shares two other retrospective formats. Starting with the simple: just do a retro, and talk; and he also recommends another simple format: “Did we meet our Sprint goal? Why/Why not?”

How can I, as a Scrum Master, supercharge my facilitation?

Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!

About Kevin Hoey

Kevin is the lead scrum master at Domestic and General, with 10 years’ experience in project management before moving into scrum mastery. He now heads up a team of scrum masters, whilst continuing to support his own squads. Kevin believes scrum masters need to focus on self-improvement to turbocharge their ability to better support teams and the wider business on the journey to effectiveness.

You can link with Kevin Hoey on LinkedIn.

Bram De Block: Discover how to break free from the trap of thinking you know it all and bring agile success to your team

In this podcast episode, Bram discusses the topic of thinking that one knows it all, and how this attitude can negatively impact a team’s ability to effectively implement agile methodologies. Bram notes that this mindset can lead to a lack of respect from team members and a tendency to focus solely on following the sprint guide without considering the needs of the team. To combat this, Bram suggests bringing up the sprint goal without mentioning it by name, and focusing on identifying areas where team members can work together effectively. Additionally, Bram advises using curiosity to engage team members and encourage collaboration. Listen to the episode to gain a deeper understanding of how to overcome the challenges of thinking you know it all and bring agile goodness to your team.

Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story – How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Bram De Block

Bram is not an official trainer, consultant nor freelancer. He is just himself, supporting colleagues in applying and growing their own potential and getting stuff done. Bram started as a software developer for 10 years, then grew into a half-time agile coach, and finally, full-time “Global Agile Lead” at Skyline Communications. Something “special” he learned (even if he wishes it wasn’t special): the meaning and impact of “respect”.

You can link with Bram De Block on LinkedIn, or meet Bram face-to-face at this meetup he hosts in Belgium.