5 Crucial Coaching Questions Scrum Masters Must Ask When Teams Consistently Overcommit
Is your team constantly taking on more work than they can handle? As a Scrum Master, guide your team towards a sustainable pace with powerful coaching questions that expose the underlying hero culture, capacity illusion, and burnout.
1. Introduction: The Hero Culture and the Burnout Cycle
Eliza, as the Scrum Master for 'Alpha Team,' frequently observed Sprint Planning meetings concluding with a familiar scenario. John, the Product Owner, would enthusiastically present new features, and the entire team, including Developers Aisha and Mark, would accept each item with a silent agreement that they could deliver everything.
However, as the Sprint progressed, that familiar tension would set in. Voices would quiet during Daily Scrums, eyes would avoid contact, and phrases like 'almost done' or 'just need a bit more time' would float around. At the Sprint Review, they'd face a pile of unfinished work. No one complained directly, as everyone felt they were 'doing their best.' This was what Eliza called the 'hero culture': consistently taking on more work than capacity allows, then making extraordinary efforts to catch up at the last minute. Over time, this led to burnout and compromised quality.
Eliza knew she had to break this cycle. Simply saying 'don't take on too much' wasn't effective; it could be perceived as accusatory or undermining the team's motivation. The team needed to develop their own insights, recognize their true capacity, and understand that saying 'no' could actually lead to creating more value. This required asking the right coaching questions.
2. Unmasking Capacity Illusion: 'What work are we truly completing?'
Teams often confuse 'being busy' with 'being effective.' Constantly working on something doesn't mean that work is actually completed or generating value. As a Scrum Master, you need to help the team see their actual capacity and the cost of context switching. This requires focusing on concrete data and objective observation.
Questions You Should Ask:
- 'What work did we actually complete this Sprint? Which items truly met our 'Done' definition?'
- 'Why did these items remain unfinished? At what stage did we get stuck, what impediments did we encounter?'
- 'What are our criteria for considering an item 'done'? How consistently do we adhere to these criteria?'
- 'What was the amount of work carried over from the last Sprint to this one? What might be the root causes of this recurring pattern?'
- 'How does the accumulation of unfinished work impact our next Sprint Planning?'
These questions are particularly valuable during the Sprint Retrospective or evaluations conducted after the Sprint Review. They enable the team to question their perception of capacity by looking at tangible data.
Want to practice navigating these challenging situations through simulation? Practice one conversation in the Mastery demo and experience how to use these questions in a real scenario.
3. Understanding the Difficulty of Saying 'No': 'What drives us to take on too much?'
Many teams take on more work than their capacity allows due to a fear of disappointing the Product Owner or stakeholders, or simply a desire to appear 'productive.' This is even more pronounced in situations with low psychological safety or where the team struggles to clearly articulate its boundaries. As a Scrum Master, you must help them explore these motivations, team dynamics, and external pressures.
Questions You Should Ask:
- 'Why does it feel difficult for us to say 'no' to requests from the Product Owner or other stakeholders? What are our concerns?'
- 'How does taking on so much work make us feel? Stress, pride, pressure... which is most prominent?'
- 'How do we perceive external pressure? Is this pressure real, or our interpretation? What can we do to manage this pressure?'
- 'What consequences do we anticipate if we take on less work? What might be the negative or positive outcomes?'
- 'If we can't finish an item on time, what is the impact on the team?'
These questions help bring the team's internal motivations and fears to the surface. Addressing these topics in Retrospectives or 1-on-1 coaching sessions allows the team to establish healthier boundaries.
4. Prioritization and Focus: 'How do we choose what is most valuable?'
A lack of a clear Sprint Goal, fuzzy priorities, or an inability to distinguish between 'important' and 'urgent' are common reasons for teams to take on too much work. As a Scrum Master, you should guide the team to establish clear priorities and understand the impact of their choices.
Questions You Should Ask:
- 'What was our Sprint Goal for this Sprint? To what extent does every item we've taken serve this goal?'
- 'If we can't do one piece of work, what would be the biggest impact? Who would feel this impact?'
- 'Which of these items will generate the highest value? Why do we believe this item is the most valuable?'
- 'Letting go of one item, which other item would it allow us to finish faster? Is this a trade-off?'
- 'During Sprint Planning, what criteria do we use when selecting items? Are these criteria clear enough?'
These questions are critical during Sprint Planning meetings or when a new work request comes in during the Daily Scrum. They help the team focus and choose what truly matters.
Looking for more scenarios to practice these challenging prioritization conversations with your team? Explore Mastery scenario practice and hone your skills.
5. Transparency and Stakeholder Management: 'How do we manage expectations?'
Unrealistic stakeholder expectations or the team's inability to effectively communicate progress and limitations can lead to an overloaded workload. As a Scrum Master, you should encourage the team to communicate proactively and manage expectations.
Questions You Should Ask:
- 'How transparently do we communicate our actual Sprint status to stakeholders? Are their expectations realistic?'
- 'When and how should we inform the Product Owner about work we won't complete this Sprint? Why is early communication important?'
- 'What steps can we take to realistically set stakeholder expectations? What kind of dialogue should we establish with them?'
- 'What kind of dialogue can we establish with stakeholders who constantly bring us new work? How can we understand their needs while explaining our capacity?'
- 'When presenting unfinished work at the Sprint Review, how do we explain the reasons and future implications?'
These questions prompt the team to review its interactions with the outside world and its communication strategies. Proactive communication reduces pressure on the team and builds stakeholder trust.
Frequently Asked Questions
- Why doesn't the Scrum Master just say 'You must say no'? The Scrum Master's role is to empower the team to make its own decisions and learn. Instead of direct instruction, coaching questions enable the team to find its own solutions, which is a more sustainable approach.
- Is taking on too much work always bad? Occasionally taking on more work than capacity allows might be acceptable for learning or emergencies. However, when it becomes constant, it degrades quality, increases technical debt, and leads to team burnout.
- When should I ask these questions? You can use these questions during Scrum events like Sprint Planning, Daily Scrum, Sprint Retrospective, or in 1-on-1 coaching sessions. The key is to ask them at the right time, with a non-judgmental attitude.
- What if the team still takes on too much work? Continue sharing your observations, show concrete data (completed work, carried-over work), and foster the team's learning cycle. Patience and consistency are crucial. You might also consider coaching sessions with the Product Owner if necessary.
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.
SCRUM MASTER IMPACT DASHBOARD
30 Metrics + 6-Week Plan + Manager Conversation Guide
This document solves a common challenge for early/mid-level Scrum Masters: “How can my contribution be measured?” Without obsessing over velocity, without blame, you'll build a practical system focused on impact.
- Start in 10 minutes
- First results in 6 weeks
- Minimum set with 5 metrics
Golden rule: A Scrum Master doesn't “sell speed.” They improve learning and flow.
How to use this PDF
- 1) Pick 5 metrics today
- 2) Capture baseline (10 min)
- 3) Follow the 6-week plan
- 4) Update the dashboard each sprint
- 5) Talk to your manager with 3 sentences + 1 table
Minimum starter set
- Psychological safety
- WIP
- Sprint goal
- Unplanned work
- Blocker time
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.