Agile estimates are forecasts
Estimates help a team make decisions. They are not guarantees of exact future performance. Good estimation makes uncertainty visible and improves planning conversations.
Relative estimation
Teams may compare items using story points or other relative scales. The point is to compare size or complexity, not to create a fake unit of time.
Capacity matters
Past throughput can help forecast what a team may complete, but capacity changes with holidays, incidents, support work, onboarding and other realities.
| Question | Practical answer |
|---|---|
| High value / low effort | Usually strong candidate |
| High value / high effort | Explore slicing or sequencing |
| Low value / low effort | May still be useful if it removes friction |
| Low value / high effort | Challenge the need |
Spikes and discovery work
When uncertainty is technical or product-related, a small investigation can be more responsible than committing to a large estimate based on guesswork.