5 Powerful Questions a Scrum Master Must Ask When a Team Consistently Overcommits
Is your team constantly missing Sprint Goals, leaving work unfinished, and experiencing low morale? This article explores coaching questions Scrum Masters can use to uncover capacity illusion, challenge hero culture, and reveal the true cost of overcommitment.
Introduction: The Blue Team's Unfinished Sprint Story
Aisha is an experienced Scrum Master for the 'Blue Team.' She observes a recurring pattern: during every Sprint Planning, the team enthusiastically commits to too much work. They're full of 'This time we'll succeed!' energy. Yet, when the Sprint ends, the scene is always the same: the defined Sprint Goal isn't met, some work remains 'almost done,' quality is compromised, and team morale dips. The Product Owner (PO) is consistently disappointed.
Aisha knows that simply telling them 'take less work' doesn't work. There's a deeper underlying issue: perhaps a 'hero culture,' a misunderstanding of capacity, or external pressures. As a Scrum Master, Aisha's role isn't to provide the right answers, but to help the team discover their own solutions by asking the right questions. Here are 5 powerful categories of questions Aisha uses to break this cycle.
1. Making the Symptom Visible: 'What is the impact of this pattern on the team?'
Enabling the team to express their own observations and feelings helps them internalize the seriousness of the problem. Discussing the personal and team impact, rather than just stating 'work isn't getting done,' is the first step towards change.
In a Retrospective, Aisha directs these questions to the team:
- How do you feel about the unfinished work at the end of each Sprint?
- What do you believe is the biggest reason this pattern keeps repeating?
- How does unfinished work affect your daily flow and motivation?
2. Uncovering the Capacity Illusion: 'What can we truly accomplish?'
Guiding the team to confront past data is key to breaking the capacity illusion. Moving beyond story points to analyze the actual amount of 'done' work, according to their 'Definition of Done,' helps the team gain a realistic perspective. This focuses on how much work is truly completed, not just how much was taken on.
Aisha prompts the team to look back at their past Sprints with these questions:
- Looking at 'done' work from the last three Sprints, what was our average throughput?
- How do you explain the difference between your estimates and actuals? What factors contribute to this gap?
- As Developers, how many 'truly done' items can we realistically expect to complete in a Sprint? Is this expectation realistic?
Facing these tough realities and helping a team discover its true capacity requires practice. practice one conversation in the Mastery demo and hone this skill.
3. Challenging Hero Culture: 'Whose expectations are we trying to meet?'
Sometimes teams take on more work than their capacity allows due to external pressures or an internal desire to 'do it all.' This can be termed a 'hero culture.' The Scrum Master's role is to challenge this culture, helping the team recognize these dynamics.
Aisha asks these questions to help the team understand these invisible pressures:
- What does taking on so much work protect the team from, or what perception does it create?
- If we committed to less work and focused purely on the Sprint Goal, who might be disappointed, or what risks might emerge?
- How can we communicate our capacity limits more effectively with the Product Owner and other stakeholders?
4. Revealing the Cost of Unfinished Work: 'What is the true cost of work not done?'
Unfinished work doesn't just mean 'not done'; it has long-term negative effects on technical debt, customer satisfaction, and team morale. Quantifying these costs helps the team understand the depth of the problem.
Aisha uses these questions to uncover these hidden costs:
- How does unfinished work impact our technical debt and product quality? What's the long-term cost?
- How are our customers or end-users affected by consistently unfinished work? How do we build their trust?
- How does this situation impact collaboration and trust within the team?
Asking the right questions to address difficult topics that your team and stakeholders might be avoiding is crucial. explore Mastery scenario practice and develop these skills.
5. Exploring Alternatives: 'What if we did things differently?'
After diagnosing the problem, the team needs to be encouraged to generate solutions and take ownership. The Scrum Master guides the team to define concrete steps for the future Sprints. This is a crucial step for developing the team's self-management capabilities.
Aisha asks these questions to encourage the team to take action:
- In the next Sprint Planning, what can we do differently to manage our capacity more realistically?
- What 'first step' can we take to increase our likelihood of achieving the Sprint Goal?
- What kind of dialogue should we have with the Product Owner and other stakeholders when making these decisions?
Frequently Asked Questions
Common questions about teams overcommitting and concise answers:
- Q: How can a Scrum Master stop a team from taking on too much work?
- A: Instead of directly stopping them, use coaching questions to help the team recognize their own capacity and the consequences of overcommitment. Empower them to make their own decisions.
- Q: Why do teams consistently overcommit?
- A: Often due to external pressure, a desire to be 'heroes,' misunderstanding capacity, unclear Sprint Goals, or an ambiguous 'Definition of Done.'
- Q: What role should the Product Owner play in this situation?
- A: The Product Owner should clarify the Sprint Goal, prioritize effectively, and set realistic expectations, avoiding demands that exceed the team's capacity. They should foster transparent dialogue with the team.
- Q: When is the best time to have these conversations?
- A: Retrospectives, after Sprint Planning, or during one-on-one coaching sessions are suitable times for these discussions. The key is to address the issue when it arises or to bring it up regularly.
Try the Related Tool
Practice difficult work moments with an AI character. Talk, get a star-based skill signal, and track growth.
Start exploring->Make your Scrum Master impact visible + free PDF
Get short, practical tips each week. Your first email includes the “Scrum Master Impact Dashboard” PDF to help make your contribution visible.
How do you prove your impact as a Scrum Master?
Without obsessing over velocity: 5 metrics + a 6-week plan for a clear impact story.
- 5-metric impact dashboard
- 6-week execution plan
- Manager-ready talk track
We respect your privacy. We only use your email to send the PDF and weekly tips.
No spam. Unsubscribe anytime.