Decision guide
Story Points vs Throughput Forecasting vs No Estimates
How should your team estimate and forecast delivery?
Side by side
| Criterion | Story points and velocity | Throughput forecasting (Monte Carlo) | No estimates (fixed time, variable scope) |
|---|---|---|---|
| Effort to produce | Medium to high (meetings) | Low (from tracker data) | Shaping effort up front |
| Expresses uncertainty | Poorly (single numbers) | Yes, confidence levels | Through scope, not dates |
| Risk of gaming | High if used as a target | Low (counts finished items) | Low |
| Needs history | Some sprints | 10-20 weeks ideal | No |
When to choose each
Story points and velocity
Estimate relative size per item; forecast from points completed per sprint.
Choose when
- The team finds sizing discussions useful for shared understanding
- Items vary a lot in size and can't easily be sliced
Avoid when
- Points are used to compare people or teams
- Estimation meetings take hours and forecasts still miss
Throughput forecasting (Monte Carlo)
Count items finished per week and simulate the remaining work to get dates with confidence levels.
Choose when
- Work is sliced into similar-sized items
- Stakeholders need dates with honest confidence
- You want weekly re-forecasts at almost no cost
Avoid when
- There's no history yet (borrow a similar team's for a start)
- Item sizes vary wildly
No estimates (fixed time, variable scope)
Decide how much time a problem is worth, then shape scope to fit.
Choose when
- The date or budget is fixed
- The team is good at slicing and shaping
- Outcomes matter more than a fixed feature list
Avoid when
- Contracts require a fixed scope and date
- Stakeholders aren't ready to negotiate scope
Verdict
Prefer throughput forecasting with thin, similar-sized items for dates with honest confidence, and fixed time, variable scope when the date is fixed. Keep story points only if the sizing conversation itself helps the team — never as a performance metric.