The sprint had been planned to the hour. Story points balanced against velocity, the board tidy, everyone nodding in planning. Two weeks later, the burndown was a flat line with a cliff at the end, and the Scrum Master was explaining — again — why a “fully committed” sprint had quietly fallen apart.
Nobody had done anything wrong. One engineer was in Portugal for a wedding. Another took the long weekend that the planning tool never heard about. Two teammates were out for a national holiday the tool assumed was a normal Tuesday. The plan didn’t fail because the team was slow. It failed because the plan assumed eight people would work ten straight days, and that was never going to be true.
This is the silent schedule killer. Not scope creep, not bad estimating — just the ordinary, fully-approved time off that every team takes, invisible to the math that promises a date.
Why “minus 20% for holidays” doesn’t hold up
Most teams handle time off with a fudge factor. Knock 15–20% off capacity, call it a buffer, move on. It feels responsible. It rarely survives contact with a real calendar.
Time off isn’t evenly distributed. A blanket percentage assumes everyone is a little bit absent all the time, when reality is that two specific people are completely absent during one specific week — often the week a release is due. A public holiday removes the whole team at once. A two-week vacation pulls one person’s entire contribution out of a single sprint. Averaging those into a flat discount smooths over exactly the spikes that wreck a forecast.
The fix isn’t a better percentage. It’s tying non-working days to the actual people and the actual dates, then letting the forecast recalculate from there. As Mountain Goat Software puts it, the cleanest way to estimate the impact of time off is to adjust planned working days against your average, rather than guessing at a velocity haircut.
Capacity that knows your calendar
This is where capacity planning with PTO and holidays in Jira stops being a spreadsheet exercise. Advanced Release Planning & Management for Jira lets you tie PTO directly to real Jira users — the same accounts already assigned to the issues — so a person’s time off reduces their availability, on the exact days they’re gone, not the team’s in the abstract.
Public holidays work the same way without the manual grind. Instead of clicking through a calendar one date at a time, you import holidays in bulk: load a region’s holiday set from a CSV, apply it to the team, and every one of those non-working days drops out of the available capacity automatically. A team split across the US, India, and Germany can carry three different holiday calendars at once, and the plan respects all of them.
Because the app reads real working days rather than calendar days, the burnup chart finally tells the truth. The line bends where the team is actually out, not as a gentle uniform slope that pretends every week is identical. A realistic burnup chart is one that knows next week only has three working days in it.
From honest capacity to an honest date
Reduced capacity is only half the value. The point is what it does to the forecast. Once the simulation works from real available days, it produces a release date the calendar can actually support.
This is the same engine behind our probabilistic release forecasting — thousands of simulated futures built on your team’s real throughput. Feed that engine a capacity that already accounts for who’s out and when, and the p50/p85/p95 dates shift to reflect the calendar instead of an idealized one. Elite teams ask “who’s actually available next sprint?” before they talk velocity; this just bakes that question into the model so you don’t have to remember to ask it.
The result is a quieter kind of planning. When someone proposes a December release, you can see immediately that the last two weeks are mostly holidays, and have the scope conversation in advance — calmly, with data — instead of in a retro three weeks too late. The vacation that used to be a surprise becomes just another input. You can explore the full picture in our guides to release planning in Jira, and see exactly how the PTO and holiday tools work in our guide to capacity planning with PTO and holidays.
Let your forecast adapt to your team’s real calendar
Your team is going to take time off. That’s not a planning problem — pretending they won’t is. Tie PTO to real users, import your holidays in bulk, and let the forecast adapt to the calendar your team actually lives by.
Browse more release planning guides and resources, or try Advanced Release Planning & Management for Jira free for 30 days and watch your next release date adjust the moment you add the team’s time off.
Leave a Reply
Your email is safe with us.