May 19, 2026
7 min read
Forecasting and predictability
Agile Forecasting Examples With Real Numbers
Simple agile forecasting examples with real numbers, so teams can see what a usable forecast sounds like without turning it into spreadsheet theater.
Why teams need examples more than formulas
Forecasting advice often gets stuck at the level of abstract principles. Teams hear words like confidence, range, and capacity, but they never see what a useful forecast actually sounds like in a real planning conversation.
Examples help because they translate those ideas into language a team can use immediately. The goal is not perfect math. The goal is a forecast that stays honest after the meeting ends.
Forecast example
Real forecasting numbers only help when the assumptions behind them stay visible at the same time.
Input example
Numbers matter, but they only become planning value when the team also understands what kind of work and capacity generated them.
Recent delivery pattern
For example, a team finishing 18 to 24 points over the last few sprints should not suddenly forecast like 30 is normal.
Range over average
A better example uses the spread in the numbers to explain what looks likely, not just the midpoint that sounds neatest.
Assumptions named
The example gets stronger when the team also says what would move the outcome, such as scope volatility or reduced capacity.
Decision-ready example
The best examples teach people how to reason about a forecast, not just how to repeat the numbers inside it.
Example one: sprint-level forecast
Imagine a team that normally finishes eight to ten workable items in a sprint. This time, one engineer is out for several days and two backlog items still carry open dependency questions.
A weak forecast would say, "We should still finish the full list." A healthier forecast would say, "We are confident in the first six items. The last two depend on unresolved questions and sit outside the strong commitment range for this sprint."
Example two: release view
Now take a release slice with twenty-eight remaining items. If the team usually finishes nine to twelve similarly sized items per sprint, a clean-looking answer like "two sprints" may sound decisive but still be optimistic.
A better forecast would say, "Two sprints is possible if throughput stays at the strong end of the recent range, but three sprints is the more credible planning window based on current delivery patterns."
What these examples are really teaching
The point is not to memorize the wording. It is to connect every forecast to current capacity, visible uncertainty, and the assumptions that could change the result. That is what keeps the forecast useful after people leave the room.
- Say what you are confident about instead of presenting the whole scope as equally safe.
- Say what is still conditional instead of hiding uncertainty inside a neat-looking answer.
- Say what would move the forecast so the team knows what to watch next.
- Use examples like these as conversation templates, not as canned scripts.
TL;DR
- Forecast examples help teams see what honest planning language actually sounds like.
- A good sprint forecast separates the confident core from the conditional edge.
- A good release forecast uses recent delivery ranges instead of one optimistic number.
- The real lesson is to connect every forecast to capacity, uncertainty, and assumptions.
- Forecast examples become useful when the numbers stay attached to assumptions about capacity, scope, and uncertainty instead of pretending to explain themselves.