Story points were originally invented as a psychological tool to help teams discuss task complexity without anchoring to exact calendar hours. Over time, however, management in many companies converted story points into a measure of individual productivity, leading to estimation inflation and endless debate during sprint planning.
When a team spends four hours every sprint arguing whether a user story is a 5 or an 8, that is non-value-adding ceremony waste. Worse yet, story point velocity cannot reliably forecast when a specific customer deliverable will reach production.
During our consulting engagements, we replace speculative estimation rituals with empirical flow metrics derived directly from team version control and ticketing timestamps:
1. Lead Time: The total elapsed duration from when a customer problem or feature ticket is formally accepted into the backlog to when it is running in production.
2. Cycle Time: The time elapsed from when an engineer begins active work on a task to when it passes verification and is deployed.
3. Work-In-Progress (WIP): The total count of active items in development, code review, or testing stages at any given moment.
4. Throughput: The number of discrete completed work items delivered per week.
By plotting cycle times on a scatterplot and tracking the 85th percentile duration, engineering leaders can answer stakeholder questions with mathematical confidence (e.g., '85% of our work items complete in 4.2 days or fewer') without requiring developers to spend hours estimating fictitious points.