Every quarterly review has this moment. A release date goes up on the screen, and beside it sits a small, honest number: Jun 7 · 85%. Somewhere in the room a leader frowns. “Eighty-five? Why isn’t it a hundred — are we not confident?”

That 85% is a release date confidence level, and it’s the most misread number in modern planning. It isn’t the team hedging, and it isn’t the tool being unsure. Read correctly, it’s the single most useful thing on the slide. So let’s read it.

What a release date confidence level actually is

A release date confidence level is the output of a forecast run on your team’s real historical throughput — thousands of simulated futures (Monte Carlo, if you want the mechanism) built from how this team has actually delivered, sprint after sprint. “85% by June 7” means that in 85 of every 100 simulated outcomes, the committed scope finishes on or before that date.

Read it that way and the frown fades. The number isn’t doubt; it’s calibration. A single naked date — the kind roadmap tools let you type in by hand — hides all of its risk behind false precision. A date carrying a confidence level shows you exactly how much room you have. And it rests on expert engineering judgment, not a machine’s guess: the team owns the assumptions — which throughput window, whose capacity, what’s in scope — and the app does the arithmetic at a scale no one could reach by hand. This is the SAFe confidence vote, run on evidence the team validates instead of a show of hands.

How to read the three bands in a review

You don’t need the math in the meeting. You need three colors and three decisions:

• Green (85% or higher): Commit. The date sits at or beyond the P85 mark, so the plan carries a genuine buffer. This is the confidence vote passing — on data.
• Amber (50–85%): This is a decision, not a date. The team can hit it, but there’s no margin for the first surprise. Renegotiate scope, add capacity, or consciously accept a later date now — don’t discover it in six weeks.
• Red (below 50%): The date is a wish. Saying the confidence level out loud is what stops the room from nodding a fictional date into the plan.

Which is why 100% is the real warning sign, not the goal. A date with no band — or a suspiciously round certainty — is the old typed-in date wearing a confident face. Honest planning lives in the range, not the point. For the leadership version of this argument, see what executives actually want from agile: a date that holds.

A confidence level is only worth reading if it’s live

Here’s the part most teams miss. The 85% you saw at PI planning was true at PI planning. It’s a snapshot. And a committed date rarely slips in one dramatic moment — it erodes quietly, through three familiar culprits: scope creep, dependencies surfaced too late, and capacity changes. Each one nudges the date after everyone has already agreed to it.

Picture it concretely: a partner team quietly slips an API you depend on, or two engineers roll off to an incident. Neither event announces itself in a status meeting, yet both move your date. A live confidence level is simply that erosion made visible — expressed as a percentage and a number of days, the moment it happens.

So the confidence level worth managing to isn’t the one from a planning room six weeks ago — it’s the one that reflects reality today. That is exactly what Advanced Release Planning keeps current: it tracks all three of the things that erode a committed release date against your committed date, in days, in real time. The percentage updates the moment scope, a dependency, or capacity shifts — so you renegotiate before you slip, not after. A confidence vote is a snapshot; the app keeps it live.

Read the band, not the point

The skill is the same whether you’re an RTE closing PI planning or a VP three questions deep in a steering review: don’t ask “what’s the date?” Ask “what’s the date, and how confident are we — right now?” That one adjustment turns a slide full of optimism into a plan you can defend. If you want the mechanics of how the live band is computed, our docs walk through it in Live Confidence Bands.

Every committed date in Advanced Release Planning for Jira carries its confidence level and its band — green, amber, or red — and keeps it current as your throughput, scope, and capacity change. Point it at your next release and read the real number before you commit to it.

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