5 Critical Questions: What to Ask When Your Scrum Team Consistently Overcommits

Aisha, as the newly appointed Scrum Master for a DevOps team, observed their first few Sprints. The team, consisting of Ben, Chloe, and Mark, had developed a habit of pulling one or two extra items into every Sprint Planning session beyond their initial commitment. Phrases like "We can squeeze this in," or "Maybe it will fit, worth a try," were common. Aisha noticed this consistently put the Sprint Goal at risk and often led to unfinished work.

During Sprint Reviews, she'd hear explanations like, "It's almost done, just final tests remaining," or "This feature was added, but a small bug appeared elsewhere." The team was tired, yet they never hesitated to take on more. Aisha began to suspect this wasn't just a simple capacity miscalculation, but a deeper 'hero culture' or 'capacity illusion' at play. The team seemed to be under constant pressure to prove themselves and deliver everything. However, this came at the cost of a sustainable pace and high quality.

As a Scrum Master, simply telling your team to 'take less work' or 'estimate your capacity correctly' is often ineffective. Such directives don't address the root cause of the problem and fail to change underlying behavioral patterns. Teams overcommit for various reasons:

External Pressure: Relentless demands from the Product Owner, management, or stakeholders.

Hero Culture: The team's tendency to prove themselves, deliver everything, or struggle to say 'no'.

Capacity Illusion: The team misjudging their actual velocity and the cost of maintaining focus.

Uncertainty: Lacking sufficient information about the complexity or dependencies of work items.

When these underlying reasons are not addressed, the cycle of overcommitment continues, negatively impacting team morale, product quality, and sustainability. The Scrum Master's role is to make these invisible dynamics visible and help the team discover their own solutions.

In these situations, what a Scrum Master needs is not just to be a process facilitator, but also a skilled coach and a keen observer. Asking powerful coaching questions is essential to focus on the root causes rather than just the surface symptoms. This enables the team to recognize their own reality, challenge their assumptions, and change their behaviors.

Operating with servant leadership principles, the Scrum Master helps remove impediments for the team, protects them from external pressures, and guides them in developing a more realistic understanding of their own capacity. This requires supporting the team's self-management and autonomy, rather than giving direct instructions. It's crucial not to shy away from difficult conversations, but to conduct them with a curious and supportive approach, not a judgmental one.

Here are 5 powerful coaching questions a Scrum Master should ask to break your team's habit of overcommitting and foster a more sustainable working environment:

Aisha, after noticing the team had again pulled in a bit too much work after Sprint Planning, decided to bring it up during the Daily Scrum. She approached it with a curious, rather than judgmental, tone:

"Team, we've started this Sprint with great energy, but I also see that some items carried over from the previous Sprint, and we've entered this Sprint with quite a heavy load. This makes me wonder: If we continue at this pace, what technical debt are we accumulating for the next Sprint or in the long run? How does this impact the quality of our product or your sustainable pace of work?"

Ben replied, "Actually, yes, the remaining tests from last Sprint caused some headaches at the start of this one." Chloe added, "And focusing on finishing one thing completely instead of starting something new would feel better." Aisha listened to these insights and continued, "Okay, then, how does focusing on so many different topics simultaneously impact the quality and speed of your work? What is the cost of constantly context-switching?" These questions helped the team develop their own insights and recognize the problem. Aisha then carried these conversations into the Sprint Retrospective, ensuring the team addressed this as an area for improvement.