Short answer: To plan a sprint around federal holidays, PTO, and training days, subtract every non-working day from each person’s available days, apply their allocation to your project, and multiply the remaining person-days by your team’s historical points per person-day. Do it before you commit, not after the sprint starts slipping.
A two-week sprint that spans Veterans Day (Wednesday, November 11, 2026) is not a ten-day sprint. It is a nine-day sprint, and that is before anyone books leave. Teams that commit to last sprint’s velocity anyway are the ones explaining a miss to leadership two weeks later.
Why do holidays and leave break government sprints so often?
Public-sector calendars are dense. Federal holidays, agency-specific closures, mandatory annual training, use-or-lose leave, and fiscal-year-end absences all land on a team that is often already smaller than it was a year ago. With flat budgets and workforce reductions, “fewer people, same mission” is the planning reality, and every lost day is a larger share of the total.
Velocity alone does not see any of this. Velocity is an average of past sprints, which may have been full-strength or short-handed. Applying it to a sprint with a different number of working days is guesswork presented as a forecast.
How do you calculate sprint capacity around holidays and leave?
Use this sequence every sprint:
- Count working days in the sprint. Start with the calendar, then remove federal holidays and any agency closure days.
- Subtract individual days off. Collect PTO, sick-leave patterns you already know about, mandatory training, court duty, and details to other programs. Ask for these at or before sprint planning, not during standup.
- Apply allocation. If someone spends 50% of their time on your project, multiply their remaining days by 0.5. Part-time and detailed-elsewhere staff are the most common source of hidden over-commitment.
- Convert person-days to points. Divide a recent sprint’s completed points by its available person-days (not headcount times ten). Multiply by this sprint’s available person-days.
- Commit to the result, then hold a buffer. Leave a small share of capacity for unplanned work, such as production support or an urgent data call.
Worked example: a six-person team across Veterans Day
A state agency team of six plans a sprint from Monday, November 9 to Friday, November 20, 2026. That is 10 weekdays, minus Veterans Day, so 9 working days.
- Ana: 1 day PTO, so 8 days
- Ben: 2 days of required training, so 7 days
- Chen: no time off, so 9 days
- Dee: 3 days PTO, so 6 days
- Eli: 50% allocated, so 4.5 days
- Fay: 80% allocated, so 7.2 days
Total available: 8 + 7 + 9 + 6 + 4.5 + 7.2 = 41.7 person-days, against 60 for six people over ten days. That is about 70% of nominal capacity.
Over the last three sprints the team averaged 40 points on 54 available person-days, or about 0.74 points per person-day. Multiplying: 41.7 × 0.74 ≈ 31 points. If the team had simply repeated its usual 40, it would have over-committed by roughly nine points, and the shortfall would have appeared as “missed commitments” with no visible cause.
What should the team write down?
Agencies increasingly want to be able to show what happened, who was involved, what changed, and what supported a decision. Sprint planning is a small but real part of that record. A capacity decision that notes the holiday, each person’s days off, allocations, the velocity ratio, and the resulting commitment gives a program manager an answer when someone asks, “Why did you commit to 31 points?” This is documentation practice, not a compliance outcome: it records a planning decision so it can be explained later.
A simple worksheet is enough to start: one row per person with columns for working days, days off, allocation percentage, and available person-days, plus a footer with the velocity ratio and the committed points. Run it for the next three sprints and compare commitment to actual.
How does doing this in one tool inside Jira make it repeatable?
The spreadsheet works until the third sprint, when someone changes a leave date in one file and not the other. Moving the same logic into Jira’s backlog removes the copy-and-paste step. Sprint planning with Capacity Planning for Jira shows sprint and team capacity on one screen, using past velocity, days-off, and allocation, before you commit. Planners adjust a person’s days off or allocation and see the capacity number change in the same view where they pull stories into the sprint.
The app is Cloud Fortified and runs on the Atlassian Cloud platform, which Atlassian certifies to SOC 2 Type II and ISO 27001. For agencies moving planning workflows onto Atlassian Cloud, including Atlassian Government Cloud (AGC), it keeps capacity decisions next to the work instead of in a side file.
FAQ
Do federal holidays count against capacity?
Yes. Remove them from the working-day count before applying anything else. Include agency-specific closures as well.
Should we use headcount times sprint length to calculate velocity ratios?
No. Use actual available person-days from past sprints, so the ratio reflects the leave and allocation the team really had.
How much buffer should we leave for unplanned work?
It depends on your team. Measure unplanned work over a few sprints and reserve that share, rather than picking a number up front.
Try it: Install Sprint planning with Capacity Planning for Jira · Help docs




Leave a Reply
Your email is safe with us.