The Overcommitted Team
A development team has a velocity of 30 story points per two-week sprint. The Product Owner, under pressure from stakeholders, has committed the team to 45 story points for the upcoming sprint. The team members are concerned but feel pressured to accept. During sprint planning, the Scrum Master notices the discrepancy but is unsure whether to intervene. The team starts the sprint and by day 3, it's clear they are behind. The Scrum Master observes that team members are skipping pair programming and code reviews to try to meet the commitment. The Product Owner is unavailable for discussion until the sprint review.
1. What should the Scrum Master do at this point, and why?
Read the worked answer
The Scrum Master should intervene immediately. The team's sustainable pace and quality are at risk. The Scrum Master should facilitate a conversation with the team to acknowledge the overcommitment and its consequences (skipping practices that ensure quality). The Scrum Master should also reach out to the Product Owner to discuss the sprint backlog and the potential impact on value delivery. The Scrum Master's role is to protect the team from unrealistic expectations and to ensure Scrum is understood and enacted. The Scrum Master might coach the Product Owner on the importance of using velocity as a guide, not a commitment, and on the dangers of pressuring the team. The Scrum Master should also help the team renegotiate the sprint scope with the Product Owner, perhaps by removing or deferring some items. If the Product Owner is unavailable, the Scrum Master should escalate appropriately, but first work with the team to adjust the sprint plan within the sprint, as Scrum allows for adaptation. The key is to address the issue early and prevent a death march.
2. How should the Scrum Master coach the Product Owner and stakeholders to prevent this in the future?
Read the worked answer
The Scrum Master should coach the Product Owner on the purpose of velocity and sprint planning. Velocity is a planning tool, not a performance metric. Overcommitting leads to technical debt, burnout, and lower quality. The Scrum Master should explain that the team's velocity is based on historical data and that consistently exceeding it is unsustainable. The Product Owner should involve stakeholders in understanding the team's capacity and the trade-offs. The Scrum Master might facilitate a workshop with stakeholders to set realistic expectations and to explain how Scrum handles uncertainty. The Product Owner should also be coached on the importance of being available during the sprint to answer questions and make decisions. The Scrum Master should emphasize that the sprint backlog is a forecast, not a contract, and that the team should be allowed to adjust as they learn. The goal is to create an environment where the team can deliver high-quality work at a sustainable pace, and stakeholders understand that predictability comes from empirical data, not wishful thinking.