The release calendar was agreed in October and pinned to the wiki. Three releases, three dates: 5 February, 19 March and 30 April. Each had been committed with a confidence vote. Sales planned a webinar around the March date, and support booked its training week after it.
Three weeks later the calendar looked exactly as it had in October. Every date was still in black. One of them was already in trouble, and nothing on the page could say which.
What a release calendar is for
A release calendar is a shared schedule of planned release dates, usually across teams or products, so that support, marketing, sales and operations can plan around them. It is useful because other people commit to it. The date for each release comes from a team’s confidence vote, which is expert engineering judgment about what the team can deliver, with what, and by when.
A calendar is a snapshot
The calendar records the date. It usually does not record the confidence the date was committed at, and it cannot follow what happens afterwards. Three things quietly move a committed date after the vote: the three things that erode a committed release date are scope creep, dependencies surfaced too late, and capacity changes.
On a calendar the cost multiplies, because the date has an audience. When a date moves late, the webinar, the training week and the customer notice move with it, and each of those owners finds out at a different time.
Keep the calendar. Put a number next to each date.
The answer is not a different calendar. It is to treat each date as a commitment with a live confidence band and read it against what has changed.
- Next to every date, write the confidence it was committed at (P50, P85 or P95).
- Point each calendar row at one Fix Version, so scope has a boundary.
- Base the forecast on a throughput window long enough to include the team’s normal mix of support and interruptions.
- Record known time off per person and import public holidays per team before they arrive.
- At every sprint boundary, read the gap in days between the calendar date and the forecast at the committed confidence.
- Tell the calendar’s audience when a date turns amber, not when it turns red.
An illustration, not customer data. Release B is committed for 19 March at 85% confidence. At the vote the 50% forecast sits at 10 March and the 85% forecast at 18 March: one day of margin. Two weeks later a hard dependency on the platform team’s API is found, and six issues are added to the Fix Version. No one did anything careless. The 50% forecast is now 17 March and the 85% forecast is 31 March, twelve days past the commitment. The date sits between P50 and P85, so it reads amber, and the calendar still reads 19 March.
Now the conversation has a number on it, and it happens five weeks before the webinar, not the week of it. Ask the platform team for the API earlier? Move a Should-have to the next release? Or move the calendar date while others can still re-plan around it? Every option is the team’s call. What changes is when the call is made.
Where Advanced Release Planning fits
Advanced Release Planning for Jira is not a calendar tool. It supplies the figure each calendar row is missing. It reads the Fix Version, the Jira issue links, the throughput window you choose, and the Capacity Awareness settings for time off and public holidays. It re-runs the Monte Carlo forecast as those change and reports the committed date against the 50%, 85% and 95% bands, with the gap in days attributed to scope, dependencies or capacity. The team sets the assumptions: which throughput window, whose capacity, what is in scope. The app does the arithmetic at Monte Carlo scale and keeps it live. Green at or above P85, amber between P50 and P85, red below P50.
For the fixed-length version of the same problem, see why timeboxing fixes the date but not what fits inside it. For a plan drawn on a single axis, see why the project timeline is drawn once. For exactly what the app reads, see the release calendar reference doc.
Key takeaways
- A release calendar lists planned release dates so other teams can plan around them.
- Each date is the output of a confidence vote, which is expert engineering judgment, and the calendar rarely records the confidence behind it.
- Scope creep, late dependencies and capacity changes move dates after the vote, and the calendar does not show it.
- Write the confidence next to each date and read the gap in days at every sprint boundary.
FAQ
What is a release calendar?
A shared schedule of planned release dates across teams or products, used so that support, marketing, sales and operations can plan around them.
What is the difference between a release calendar and a roadmap?
A roadmap describes what is planned and in what order. A release calendar fixes dates. Either one is a snapshot unless each date is re-forecast as scope, dependencies and capacity change.
How do I know which dates on the calendar will hold?
Record the confidence each date was committed at, then compare the current forecast at that confidence with the date. The gap in days, and whether it is green, amber or red, tells you.
Keep the calendar. Keep every date honest too. See the committed date and its live confidence band in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




Leave a Reply
Your email is safe with us.