Most release dates are set by taking remaining story points, dividing by average velocity, and announcing the result as if it were a fact. It almost never is. Release date forecasting done properly treats delivery as a probability, not a single number — and that honesty is exactly what makes stakeholders trust you. It’s a cornerstone of solid release planning.

Why point estimates mislead

A single date hides all the uncertainty. “September 15” sounds precise, but it has no confidence attached — it could be a coin flip or near-certain, and the stakeholder can’t tell. Worse, point estimates ignore the natural variation in how much a team actually completes sprint to sprint.

Forecast from real throughput

The reliable approach uses your team’s historical throughput — how many items it actually completes per sprint — and projects it forward across a range of outcomes. Instead of one date you get a distribution: “50% likely by Sept 10, 85% likely by Sept 24.” That range is both more honest and more useful, because stakeholders can choose the confidence level the situation demands. We cover the statistical version in retrospective release planning.

Keep it live

A forecast isn’t a one-time calculation — it should update every sprint as new throughput data arrives, so the date tightens as you approach it. Advanced Release Planning, Roadmaps & Management for Jira does this automatically, turning your real track record into a capacity-aware, probabilistic release date that refreshes as the team delivers. Watch it against a release burndown chart to catch drift early.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio