Sprint Velocity vs Throughput: Which Metric to Use?
Compare sprint velocity (story points per sprint) with throughput (items per unit time). Learn when to use each metric and how they complement each other.
Detailed Explanation
Velocity vs Throughput
Both metrics measure output, but they answer different questions and behave differently in practice.
Sprint Velocity
- Unit: Story points per sprint
- Requires: Story point estimation
- Best for: Sprint planning, release forecasting in Scrum
- Weakness: Depends on consistent estimation; inflating points inflates velocity
Throughput
- Unit: Work items completed per time period (week, sprint)
- Requires: No estimation -- just counting done items
- Best for: Kanban, flow metrics, teams that skip estimation
- Weakness: Treats all items equally; a 1-day task and a 2-week epic both count as 1
When to Use Which
| Scenario | Recommended Metric |
|---|---|
| Scrum team with stable estimation | Velocity |
| Kanban team | Throughput |
| Team new to agile | Throughput (simpler) |
| Release date forecasting | Velocity (more nuanced) |
| Identifying bottlenecks | Throughput + cycle time |
Using Both Together
Many mature teams track both. Velocity for sprint planning, throughput for flow analysis. If throughput is stable but velocity drops, it means the team is completing the same number of items but they are smaller -- useful for spotting estimation drift.
Key Insight
Neither metric should be used as a performance evaluation tool. Both are planning aids, not productivity scores.
Use Case
Use this comparison when deciding which metric to implement for your team, or when transitioning from Scrum to Kanban or vice versa.