Counting stories instead of points in Agile practices may seem tempting but is ultimately misguided. The discussion critiques the reliance on story points and velocity, highlighting their shortcomings in measuring true team performance. It encourages the adoption of more meaningful metrics like lead time and cycle time, which provide a clearer picture of efficiency. This conversation sparks a deeper reconsideration of what it means to evaluate progress in agile environments.
The misuse of story points and velocity in Scrum often leads to management misinterpretation, fostering an unhealthy team environment amidst unrealistic expectations.
The podcast advocates for using lean metrics like lead time, cycle time, and throughput as clearer alternatives to estimate team productivity.
Deep dives
Critique of Story Points and Velocity
The common practice of using story points and velocity in Scrum for estimating work items is scrutinized due to concerns about their misuse. Many teams have expressed that management often misinterprets these values, using them to compare team performances and set unrealistic expectations. This has led to an unhealthy environment where teams feel pressure to manipulate story points to avoid negative consequences. Consequently, the idea of relying on more straightforward metrics instead of estimates is proposed, aiming for a more transparent and accurate measurement of team performance.
Alternative Metrics for Better Clarity
The discussion introduces three lean metrics—lead time, cycle time, and throughput—as potential alternatives for measuring team productivity. Lead time tracks the time from a customer request to the delivery of value, while cycle time measures the elapsed time from when work begins on an item to its completion. Throughput counts the number of completed items in a specific timeframe, giving a clearer picture of productivity. By focusing on these metrics, teams can minimize time spent negotiating story points, thus fostering a more efficient and effective workflow.
1.
Rethinking Agile: Beyond Story Points and Velocity
October 31st is scary enough without having someone argue that it would be so much better if we just counted the number of stories completed each Sprint. I had to go back and look at the date on this article and make certain it was not April 1....