Short answer: Moving capacity planning from spreadsheets into Jira puts team availability, past velocity and the sprint commitment in one place, so the plan is built from current data and leaves a record of how the commitment was reached. For agencies moving workloads to Atlassian Cloud, it is a small step that removes one of the most fragile manual files in the program.
Picture a program office on a Monday morning: the sprint starts in two days, the capacity workbook lives on a shared drive in three slightly different versions, and two people have changed their leave since anyone last updated it. With budgets flat and headcount down at many agencies, “fewer people, same mission” is the working reality. When staff are cut, an inaccurate capacity number costs more than it used to, because there is less slack to absorb the miss.
Why do spreadsheets fail as a capacity tool?
Spreadsheets are not the problem; disconnection is. The workbook sits outside the backlog, so every change in Jira (a story split, a new assignee, a descoped item) has to be re-keyed by hand. Typical failure points:
- Leave, training and detail assignments are updated by email, after the fact.
- Velocity is copied from a report at some earlier date and never refreshed.
- Versions multiply, and nobody can say which one the team committed against.
- The reasoning behind the commitment lives in someone’s head, not in a record leadership can review.
For a government team reporting up a chain, that last point matters most. When a deadline slips, the first question is what was known at planning time and why the team agreed to the scope.
How do you calculate sprint capacity for a government team?
Use a repeatable five-step sequence, the same every sprint:
- Count working days. Take the sprint length and subtract federal, state or agency holidays that fall inside it.
- Apply allocation. Multiply each person’s days by the share of their time assigned to this team. A developer detailed 50% elsewhere contributes half.
- Subtract days off. Remove planned leave, training and mandatory agency events per person.
- Convert with past velocity. Divide recent completed points by the person-days those sprints actually had. That gives points per person-day.
- Commit at or below the forecast. Multiply this sprint’s person-days by that rate and plan to the result, not to last sprint’s headline velocity.
What does a worked example look like?
A state licensing team has six people and a two-week sprint that includes Veterans Day, leaving 9 working days.
- Ana, 100% allocated, no leave: 9 days
- Ben, 100%, 2 days leave: 7 days
- Chi, 50% (detailed to another office): 4.5 days
- Dev, 100%, 3 days of required training: 6 days
- Eli, 80%: 7.2 days
- Fay, 100%, 1 day leave: 8 days
Total capacity is 9 + 7 + 4.5 + 6 + 7.2 + 8 = 41.7 person-days, against a full-strength 54 (6 people × 9 days).
The last three sprints completed 38, 42 and 40 points (120 total) over 48, 52 and 50 person-days (150 total). That is 0.8 points per person-day. Forecast: 41.7 × 0.8 ≈ 33 points.
A team that simply repeats its average of 40 points would overcommit by about 7 points, roughly 21%. That gap is the kind of miss that turns into an unexplained slip on a status report.
What changes when this lives inside the Jira backlog?
Once the calculation is inside Jira, the inputs are the same data the team already maintains. Sprint planning with Capacity Planning for Jira shows team capacity next to the backlog, using past velocity, days off and allocation, so you can see the commitment against capacity before the sprint starts. Because it is the same screen every sprint, the method stops depending on whoever built the workbook. For the full method, see our guide to capacity planning in Jira.
It also fits where many agencies are heading. Atlassian positions Atlassian Cloud, including Atlassian Government Cloud (AGC), as the destination for modernization, and the app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II / ISO 27001 platform. That describes the platform, not a certification held by DiViM. The app records planning inputs and the resulting commitment; it is a planning tool, not a compliance product. Still, a documented trail of who was allocated, what days off were subtracted and why the team committed to N points is the kind of evidence-of-decision that reviewers increasingly expect to see.
How can you roll this out in 90 days?
- Days 1–30: Run the five steps in your existing workbook for two sprints and compare the forecast to actual results.
- Days 31–60: Move allocation and days off into Jira planning and retire the shared-drive copy.
- Days 61–90: Add the forecast and actual to your sprint review so leadership sees capacity next to outcomes.
FAQ
Do we need new infrastructure to plan capacity in Jira?
No. The app installs from the Atlassian Marketplace into Jira Cloud and works inside the backlog you already use.
Does this replace story points?
No. It uses the points you already estimate, along with your team’s past velocity, and adds availability so the commitment reflects who is actually present.
Is the app certified for government compliance?
The app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II / ISO 27001 platform. DiViM does not hold its own certifications, so confirm your agency’s requirements with your security office.
Try it: Install free from the Atlassian Marketplace · Help docs




Leave a Reply
Your email is safe with us.