In 30 seconds
- Velocity sums story points finished per sprint.
- Throughput counts items finished per time period.
- If items are similar in size, throughput forecasts just as well with less effort.
Pick velocity when…
- The team already estimates in story points
- Items vary a lot in size
- The team works in fixed sprints
Pick throughput when…
- Items are split to similar, small sizes
- The team uses Kanban or continuous flow
- You want to skip estimation overhead
Side by side
| Velocity | Throughput | |
|---|---|---|
| Unit | Story points per sprint | Items per week |
| Needs estimates | Yes | No |
| Typical method | Scrum | Kanban |
| Forecasting | Points left / velocity range | Items left / throughput, or Monte Carlo |
Myth vs reality
Myth · Throughput ignores item size.
Reality · It relies on keeping items similar in size.
Myth · Velocity is more precise.
Reality · Both give ranges; precision is an illusion.
Myth · You can't use throughput in Scrum.
Reality · Many Scrum teams do.
FAQ
Can we track both?
Yes; comparing them can reveal estimation drift.
Which works for Monte Carlo forecasting?
Throughput is the usual input.
Should we compare teams on either?
No; both are for a team's own planning.