The Metric That Drove the Wrong Behavior
An organization has adopted Scrum and is using velocity as a key performance indicator for teams. Management compares team velocities and rewards the team with the highest velocity each quarter. As a result, teams have started inflating story points and splitting stories into smaller pieces to increase their velocity numbers. The quality of work has decreased, and cross-team collaboration has suffered. The Scrum Master of one team notices that their team is gaming the system and is concerned about the impact on the organization. The team's actual delivery of value has not improved.
1. What is the problem with using velocity as a performance metric, and how should the Scrum Master address it?
Read the worked answer
Velocity is a relative measure of a team's capacity to complete work within a sprint, based on their own estimation. It is not comparable across teams because each team estimates differently. Using it as a performance metric encourages gaming, such as inflating estimates or splitting stories, which undermines the purpose of estimation and can lead to lower quality. The Scrum Master should educate management on the appropriate use of velocity: as a planning tool for the team, not as a comparison or reward metric. The Scrum Master should advocate for outcome-based metrics that reflect value delivery, such as customer satisfaction, cycle time, or business impact. The Scrum Master can facilitate a conversation with management to explain the unintended consequences and propose alternative metrics. The Scrum Master should also work with the team to reflect on their behavior and realign with agile values, emphasizing transparency and honesty. The Scrum Master might use the sprint retrospective to discuss the impact of gaming and how to focus on delivering value rather than chasing numbers.
2. How can the Scrum Master help the team and organization shift focus to continuous improvement rather than competition?
Read the worked answer
The Scrum Master should promote a culture of continuous improvement by encouraging teams to focus on their own trends and learning. Instead of comparing velocities, teams should track their own velocity over time to forecast and improve. The Scrum Master can introduce metrics like lead time, cycle time, and escaped defects to provide a more holistic view of performance. The Scrum Master should facilitate communities of practice where teams share challenges and solutions, fostering collaboration rather than competition. The Scrum Master can also work with management to redefine success in terms of customer outcomes and team health. The Scrum Master might use retrospectives to help the team identify areas for improvement and experiment with changes. The key is to shift the mindset from extrinsic rewards to intrinsic motivation, emphasizing mastery, autonomy, and purpose. The Scrum Master should model transparency and courage by addressing the gaming behavior openly and focusing on the underlying issues.