Beyond Velocity: Why Your Sprint Points Are a Lie
Every Monday, thousands of engineering teams sit in a room and argue about whether a ticket is a "3" or a "5". Then, two weeks later, a manager looks at a chart and asks: "Why did our Velocity drop from 45 to 40?"
This is Agile Theatre.
Velocity was invented by the creators of Extreme Programming (XP) as a Capacity Planning Tool. It answers one meaningful question: "Roughly how much work can we fit in the van this sprint?"
It became a toxic metric when managers started using it to answer a different question: "How hard is the team working?"
In this guide, we ditch the "Story Points" and look at Flow Metrics—the physics of software delivery.
1. The Problem with Velocity
Velocity violates Goodhart’s Law: "When a measure becomes a target, it ceases to be a good measure."
If you tell a team their goal is to "Increase Velocity by 10%," they will not code faster. They will simply:
- Inflate Points: A "3" becomes a "5".
- Cut Corners: Skip the unit tests to finish the "8-point" story.
The number goes up. The value goes down.
2. The Superior Metric: Cycle Time
Velocity is a guess ("I think this is big"). Cycle Time is a fact ("This took 4 days").
Definition: The clock starts when work enters "In Progress" and stops when it reaches "Production".
- Why it matters: Users don't care how many "points" you burned. They care how long they waited for the feature.
- The Goal: Reduce average Cycle Time. If you drop from 5 days to 3 days, you are delivering value 40% faster.
3. The Bottleneck Finder: Flow Efficiency
This is the most painful metric to measure, but it changes everything.
$$ Flow Efficiency % = \frac{\text{Active Work Time}}{\text{Total Cycle Time}} \times 100 $$
The Reality Check:
- Total Cycle Time: 10 Days.
- Day 1: Coding (Active).
- Day 2: Waiting for PR Review (Idle).
- Day 3: Waiting for PR Review (Idle).
- Day 4: Waiting for QA (Idle).
- Day 5: Fixing Bugs (Active).
- Total Active: 2 Days.
- Efficiency: 20%.
Mentor Tip: If you want to ship faster, don't code faster. You can double your typing speed and only save 1 day. But if you fix your Code Review process (wait time), you save 3 days.
4. How to Visualize Flow (The CFD)
The Cumulative Flow Diagram (CFD) is the EKG of your team.
- Top Line: Work Started.
- Bottom Line: Work Finished.
- The Gap: Work in Progress (WiP).
The Rule: If the lines are diverging (widening gap), you are starting more than you are finishing. Your Cycle Time is increasing. Stop starting. Start finishing.
Summary
- Velocity is for Planning: Use it to decide what to put in the Sprint. Never use it to judge performance.
- Cycle Time is for Speed: Measure the clock-time to production.
- Flow Efficiency is for Optimization: Find the wait times and kill them.
Stop asking "How many points is this?" Start asking "Why did this ticket sit in 'Code Review' for 48 hours?"
