What should a government Scrum Master check before sprint planning? Confirm the sprint dates and holidays, subtract every day-off from each person’s available days, apply real allocation percentages, compare the result with recent velocity, and write down the commitment and the reasoning. Eight short checks, done in the same order every sprint, turn planning into a repeatable and defensible routine.
Your agency lost two positions at the start of the fiscal year, the mission did not shrink, and the program office still expects the same quarterly milestones. “Fewer people, same mission” is now the planning reality for many FedCiv, DoD, and State and Local teams. When headcount drops, a sprint commitment built on hope fails faster, because there is no slack left to absorb a miss.
Why does a checklist matter more in government?
Government teams rarely have clean, full-time staffing. People are detailed to other programs, contractors rotate, leave is scheduled around fixed federal holidays, and mandatory training lands in the middle of a sprint. Each of those facts is easy to know and easy to forget at the planning meeting. A checklist moves them from memory to a repeatable routine, and it leaves a record of what the team knew when it committed. That record matters when leadership asks, months later, why a milestone slipped or why a team committed to what it did.
What is on the sprint planning checklist?
Run these eight checks in order. Most take under five minutes once the data is in one place.
- Lock the sprint dates and count working days. Mark federal holidays and any agency closure days first, before anything else.
- List every person who will touch sprint work. Include part-time staff, detailees, and contractors with limited hours.
- Record each person’s allocation. A developer who is 50% on your team is 0.5, not 1.0, no matter how often they attend your standup.
- Subtract known days-off. Leave, training, travel, and required agency events all come out before the math starts.
- Total the available person-days. This is your honest capacity ceiling.
- Compare with recent velocity. Use the last three completed sprints and the person-days those sprints actually had.
- Pick a commitment at or below the forecast. Leave room for the unplanned work every government team gets, such as data calls and audit requests.
- Write the decision down. Note who was allocated, which days were subtracted, and why the team chose N points.
How do you calculate capacity in practice?
Here is a worked example for a six-person team planning a two-week sprint from Monday, November 9 to Friday, November 20, 2026. There are 10 weekdays, and Veterans Day (Wednesday, November 11) is a federal holiday, so the team has 9 working days.
- Analyst A: 100% allocation, no leave. 9 days.
- Developer B: 100% allocation, 2 days of mandatory training. 7 days.
- Developer C: detailed at 50% to another program, no leave. 4.5 days.
- Developer D: 100% allocation, 1 day of leave. 8 days.
- Tester E: 80% allocation, no leave. 7.2 days (9 x 0.8).
- Developer F: 100% allocation, no leave. 9 days.
The team has 9 + 7 + 4.5 + 8 + 7.2 + 9 = 44.7 available person-days, against a nominal 60 for six people over ten days. That is a 25% gap that a “six people, ten days” mental model never sees.
Now check velocity. In the last three sprints, the team completed 38, 34, and 36 points, with 50, 46, and 48 available person-days. Total points are 108 over 144 person-days, or 0.75 points per person-day. Applied to 44.7 person-days, the forecast is about 33.5 points. A commitment of 32 or 33 points is defensible, and a commitment of 40 is not. The team that planned for “six full-time people” would have committed near 40 and then explained the miss.
How does doing this in one tool make it repeatable?
The checklist works on a spreadsheet, but it breaks down at scale. Allocation lives in one file, leave in another, and velocity in a Jira report, so every sprint starts with reconciliation instead of planning. For agencies moving work onto Atlassian Cloud, including Atlassian Government Cloud (AGC), the natural step is to bring capacity into the backlog where the work already lives.
That is what Sprint planning with Capacity Planning for Jira does. It lets you plan sprints and team capacity on one screen, using past velocity, days-off, and allocation, before you commit, inside the Jira backlog. The app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II and ISO 27001 platform. It records your planning inputs, so the “who, which days, and why N points” note in step eight is already sitting beside the sprint. It is a planning tool, not a compliance product, but a consistent decision trail makes it easier to answer the questions leaders ask.
FAQ
How long should sprint planning prep take with a checklist?
Once allocation and leave data is current, the eight checks usually take 15 to 20 minutes of Scrum Master time before the meeting. Most of the effort is the first sprint, when you build the baseline.
Should we adjust capacity for meetings and unplanned work?
Yes. The velocity ratio already reflects typical meeting load and interruptions, because it is calculated from completed sprints. If a one-off event is coming, such as an audit, treat it as a day-off or reduce the commitment explicitly.
What if we have fewer than three completed sprints?
Use what you have, commit conservatively, and label the forecast provisional in your note. Refine it as history accumulates.
Try it: Install free from the Atlassian Marketplace · Help docs
Rollout idea: for your next sprint, run the eight checks by hand, then compare the result with your usual estimate. The gap is your overcommitment risk.




Leave a Reply
Your email is safe with us.