The program office ran a schedule risk analysis before the quarter started. It said the release had an 85% chance of landing by 14 May. The team looked at it, agreed, and committed. Nine weeks later someone asked whether 14 May still held. The honest answer was that nobody knew, because the analysis was a file from January and the plan it described had been changed a dozen times since.
That is a composite, not a customer. The pattern is common, and it is not a failure of the analysis. It is a failure of timing.
What a schedule risk analysis is
A schedule risk analysis takes the estimates and the known risks for a plan and produces a range of possible finish dates, each with a probability. Instead of “we will finish on 14 May,” it says “there is an 85% chance we finish by 14 May and a 50% chance we finish by 6 May.” Most are built with Monte Carlo simulation: run the plan thousands of times with the uncertainty in it, and read the spread.
That is the right idea, and it matches how a team thinks at a PI confidence vote. The vote is expert engineering judgment, made by the people who will do the work. A schedule risk analysis gives that judgment a distribution to stand on. The team owns the assumptions: which throughput window, whose capacity, what is in scope.
Why the result goes stale
The analysis describes the plan on the day it was run. After the commitment, three things quietly change that plan. They are the three things that erode a committed release date: scope creep, dependencies surfaced too late, and capacity changes. Each one moves the finish distribution, and none of them edits the document that says 85%.
- Scope. Work is added to the release. The analysis still counts the old backlog.
- Dependencies. A link appears to another team’s work. The analysis never saw that arrow.
- Capacity. Someone is pulled onto another project or goes on leave. The analysis assumed they stayed.
The risk to the date did not stay at 15%. It moved, and the first sign is usually a missed milestone. A confidence vote is a snapshot. The question is what keeps it live.
Re-run it where the work lives
The fix is not a better first analysis. It is to treat the analysis as a continuous reading rather than a deliverable.
- At the vote, record the committed date and the confidence it was made at.
- Feed the analysis from the system the team already works in, so it reads the real scope, links and throughput.
- Re-read the forecast at the committed confidence against the committed date, in days.
- When the gap opens, renegotiate before the slip, not after it.
An illustration, not customer data. A release is committed for 14 May at 85% confidence, and at the vote the 85% forecast sits on 11 May: three days of margin. Six weeks later, nine issues have been added, one cross-team link has appeared, and an engineer has moved to another project. The 85% forecast now reads 17 May. Nothing has been missed yet. The release is already three days past its commitment, and there is still time to cut scope or move the date by choice.
Where Advanced Release Planning fits
Advanced Release Planning for Jira runs the Monte Carlo simulation natively in Jira and keeps it current. It reads the Fix Version, the Jira issue links and the throughput window the team selects, along with capacity settings, and reports the committed date against its confidence band: P50, P85 and P95. It tracks scope, dependencies and capacity against the committed date, in days, and a release reads green at or above P85, amber between P50 and P85, and red below P50. The team sets the assumptions. The app does the arithmetic and keeps it live. It does not decide what to do about a gap. It shows the team the gap while the options are still open.
For the same idea applied to older techniques, see the PERT chart gave the date a probability once and why earned value says you are behind but not when you land. The mechanics are in the schedule risk analysis reference doc.
Key takeaways
- A schedule risk analysis gives the team’s judgment a probability distribution. It is a snapshot of one day’s plan.
- Scope creep, late dependencies and capacity changes move the distribution after the vote.
- Re-read the forecast at the committed confidence, in days, not once a quarter.
- Renegotiate while the gap is small and the options are still open.
FAQ
What is a schedule risk analysis?
It is a method that uses estimates and known risks to produce a range of possible finish dates with a probability for each, usually through Monte Carlo simulation.
How often should a schedule risk analysis be re-run?
Whenever scope, dependencies or capacity change. In practice that means continuously, which is only practical if the forecast reads live data from the planning system.
Does a schedule risk analysis replace the team’s confidence vote?
No. The vote is expert engineering judgment. The analysis puts a distribution under it and keeps it current as the plan changes.
Commit on the team’s judgment. Keep the risk to the date live. See your committed date against its confidence band in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




Leave a Reply
Your email is safe with us.