Swap Velocity for PBI Count in Sprints

WHY IT MATTERS: Senior engineers waste hours debating story point values that obscure actual delivery capacity. The Scrum.org article argues that velocity often creates Agile Theater, where teams chase abstract numbers instead of improving flow. If your forecasts feel noisy or your retrospectives keep circling back to whether an eight-point story should have been a five, the metric itself may be the problem. Switching to a simpler signal can restore empirical process control without adding process weight.

WHAT CHANGED: The 2019 Story Points Detox Plan proposes a zero-cost experiment using data you already own. Take your historical sprints and build two charts from the same dataset. On the first chart, keep your standard velocity line showing the sum of story points completed per sprint. On the second chart, replace the Y-axis with a count of Product Backlog Items done per sprint. Then compare the shapes. Many teams find that the count-based line is more stable and easier to forecast from, because story point inflation and compression cancel out over time while item counts reflect real throughput. The article notes that this comparison works well as a retrospective activity, letting the team inspect the evidence and adapt their planning approach rather than forcing a top-down mandate.

WHAT TO WATCH: Look for whether your PBI sizes are already relatively uniform. If they vary wildly, a straight count may mislead more than velocity. Also watch for stakeholder resistance; the article suggests running both metrics in parallel at first rather than ripping out velocity overnight. The broader pattern is introducing flow metrics alongside legacy agile metrics to build confidence through evidence. You can apply the same empirical approach to other sacred cows like burndown charts or utilization targets.