5 Coaching Questions: What a Scrum Master Should Ask When the Team Consistently Overcommits

1. The Problem Story: The Phoenix Team's Endless Sprints

2. Why Just Saying "No" Fails

3. What Skill Is Truly Needed: The Art of Inquiry for Clarity

4. A Framework for Unpacking Overcommitment

• Observe and Listen: Pay close attention to the team's body language, tone of voice, hesitations, and conversations. Phrases like "We'll just make it work" or "We'll figure it out somehow" can be indicators of overcommitment.
• Make Data Visible: Present metrics to the team such as completed work (velocity) from past Sprints, unfinished items, bugs, and rework. Numbers provide an objective basis, moving beyond emotional discussions.
• Ask Open-Ended Questions: Pose questions that encourage the team and the Product Owner to think and evaluate the situation from different angles. These questions challenge assumptions and help establish realistic expectations.
• Uncover Risks and Costs: Discuss how overcommitment affects not only delivery time but also quality, team morale, and long-term sustainability.
• Foster Shared Ownership: Ensure that decisions are made by the team. Your role is to create an environment that helps them make the right decisions.

5. 5 Coaching Questions Every Scrum Master Should Ask

• 1. "To achieve this Sprint Goal, what absolutely must be done? What can we defer?" This question helps the Product Owner and the team clarify true priorities. It breaks the illusion that everything is "critical" and encourages focus. It helps them understand how flexible or rigid the Sprint Goal truly is.
• 2. "Considering our past Sprint performance, how confident do we feel about completing this amount of work?" This directs the team towards historical data and realistic capacity. It ensures decisions are based on concrete evidence rather than emotional responses or pressure. This helps to counteract a "hero culture."
• 3. "If we take on this additional work, what existing plan item would we implicitly be saying no to or deferring? What would be the cost of that?" This question forces the team and Product Owner to make a clear trade-off. It highlights that every decision has a cost and makes hidden costs (e.g., technical debt, quality degradation) visible. It's also crucial for stakeholder management.
• 4. "What would be the impact on the team and our product if we have multiple 'almost done' items at the end of the Sprint?" This emphasizes the cost of accumulating unfinished work. It reinforces the importance of the "Definition of Done" and shows that value is only realized when work is truly complete. This can also be addressed in Daily Scrum and Sprint Retrospective.
• 5. "As we start this Sprint with this workload, in what areas would the team feel most supported?" This question brings out the team's concerns and needs. It reinforces the Scrum Master's servant leadership role and demonstrates a commitment to the team's motivation, well-being, and sustainability.

• Practicing these questions in real scenarios is the best way to develop your skills. explore Mastery scenario practice and be prepared for these challenging conversations.

Frequently Asked Questions (FAQ)

• Q: How can a Scrum Master manage a Product Owner who constantly pushes for more work? A: It's crucial to educate the Product Owner about the team's actual capacity, past performance data, and the long-term costs of overcommitment. Use coaching questions to involve the Product Owner in these decisions and support them in prioritization.
• Q: What's the difference between a Scrum Master telling a team what to do and coaching them? A: Telling is giving directives and reduces team autonomy. Coaching, on the other hand, involves asking the right questions to help the team find their own solutions, empowering them, and aiding their learning. This is fundamental to servant leadership.
• Q: How do these questions help with stakeholder management? A: These questions inform stakeholders (including the Product Owner) about the team's capacity, the cost of priorities, and realistic expectations. By promoting transparency and encouraging data-driven discussions, they help stakeholders make more informed decisions and build trust in the team.
• Q: What if the team still insists on taking on too much work despite these questions? A: In this case, bring the topic up in the Retrospective. Discuss why the team made that decision, its consequences, and how they might act differently in the future. Perhaps there's external pressure or a need for "heroism." Focus on uncovering the root causes.