Short answer: A documented sprint capacity decision is a short record of who was available, what was subtracted (holidays, leave, training, shared allocation), what historical velocity was used, and why the team committed to a specific number. It does not make an agency compliant with anything, but it gives program managers a defensible, reviewable trail when an auditor, inspector general, or budget office asks why a commitment was made.
Picture the meeting nobody wants: a modernization program slipped two releases, the team lost two positions during the year, and leadership asks a simple question. “When you committed to that scope in March, what did you know?” If the honest answer is “we looked at the backlog and it felt doable,” the program has a credibility problem that no status slide will fix.
Why does sprint capacity need a paper trail in government?
Public-sector buyers are operating under heavy evidence pressure. Continuous ATO practices, CMMC requirements for the defense industrial base, and tight incident-reporting windows have trained agencies to expect that they can show what happened, who acted, what changed, and what evidence supported a decision. That expectation is spreading beyond security into delivery itself.
At the same time, many teams are being asked to do the same mission with fewer people. Hiring freezes, attrition, and reassignment mean the team that planned last quarter is often not the team that is delivering this quarter. When capacity is shrinking, an undocumented commitment is a risk: it looks like the team overpromised, even when the real cause was a headcount change that happened after planning.
To be clear about scope: capacity documentation is a planning practice, not a compliance control. It will not satisfy a security framework. What it does is make your delivery decisions explainable, which is exactly what oversight bodies and budget offices ask for.
What should a sprint capacity decision record contain?
Keep it small enough that a scrum master will actually fill it in every sprint. Five elements cover almost every question you will get later:
- Roster and allocation. Every person on the team and the percentage of their time committed to this team, including people shared with another program or detailed elsewhere.
- Subtractions. Holidays, approved leave, mandatory training, and known outages, listed by person and day.
- Velocity basis. Which past sprints you used to estimate throughput, and whether any were excluded as outliers.
- The commitment. The number of points (or hours) committed and the gap between calculated capacity and commitment.
- The rationale and approver. One or two sentences on why, and who agreed. “Committed below capacity to absorb pending security patching” is enough.
How do you build the habit without adding overhead?
1. Capture it at the moment of planning, not afterward
A record reconstructed weeks later is a story, not evidence. The decision should be captured in the same session where the team commits, using the numbers on screen at that moment.
2. Keep the record next to the work
If the capacity math lives in a personal spreadsheet and the backlog lives in Jira, the two drift apart and the spreadsheet disappears when its owner changes jobs. Store the decision where the sprint itself lives so anyone reviewing the sprint can find the reasoning.
3. Log changes as changes
When someone is pulled onto a data call or a position is cut mid-sprint, record the new capacity and what scope moved out. The goal is a visible before-and-after, not a silently edited plan.
4. Review the trail at the end of each quarter
Compare committed versus delivered alongside the capacity notes. Patterns appear quickly: chronic optimism, a recurring training block nobody planned for, or a shared specialist who is always double-booked.
Worked example: a three-week sprint after a staffing cut
Consider a hypothetical seven-person state licensing modernization team running three-week sprints (15 working days). The upcoming sprint includes one observed holiday, so there are 14 working days. The team recently lost one full-time position, and the remaining roster looks like this:
- Three developers at 100%: 3 × 14 = 42 person-days
- One developer at 100% with 3 days approved leave: 11 person-days
- One developer shared with another program at 50%: 7 person-days
- One tester at 80% with 2 days of mandatory training: (14 − 2) × 0.8 = 9.6 person-days
- One business analyst at 60%: 14 × 0.6 = 8.4 person-days
Available capacity is 78 person-days. Over the last six sprints the team averaged 48 points with roughly 100 available person-days per sprint, or about 0.48 points per person-day. That puts calculated capacity at about 37 points (78 × 0.48 = 37.4).
The product owner wanted 46 points to stay on the original release plan. The team committed to 36, and the record reads: “Capacity reduced by one FTE and one holiday; committed 36 of 37 calculated points; 10 points of reporting enhancements deferred to next sprint; approved by program manager.” When leadership later asks why the release moved, the answer is already written down, with numbers, dated, and tied to the sprint.
Making it repeatable inside Jira
The practice only survives if it costs almost nothing. That is the problem Sprint planning with Capacity Planning for Jira addresses: the team sees past velocity, days off, and each person’s allocation on one screen in the Jira backlog, and sizes the sprint against real capacity before committing. Because the inputs live in Jira rather than a side spreadsheet, the numbers behind each commitment stay attached to the sprint they shaped. For agencies moving work onto Atlassian Cloud or Atlassian Government Cloud (AGC) as part of modernization, it keeps planning on the same platform as the backlog. The app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II / ISO 27001 platform; it records planning inputs and decisions, and it is not itself a compliance product.
FAQ
Does documenting capacity decisions make a program audit-ready?
No single practice does. It gives reviewers a clear, dated record of how delivery commitments were made, which supports the broader documentation an agency already maintains.
How long should a capacity decision record take?
If the inputs are already on screen during planning, two to five minutes per sprint. If it takes longer, the inputs are living in too many places.
What if leadership overrides the team’s commitment?
Record that too: the calculated capacity, the requested scope, and who approved the difference. A documented override protects the team and gives leadership an honest view of the risk they accepted.
Try it: a 30-day capacity record pilot
Pick one team and run two sprints with the five-element record above. At the end, compare commitment to delivery and see whether the notes explain the gap. If they do, extend the practice to the rest of the program.
Try it: Install Sprint planning with Capacity Planning for Jira free · Help docs




Leave a Reply
Your email is safe with us.