Short answer: Velocity is a record of what your team finished in past sprints; capacity is the working time your team actually has in the next one. Government teams get into trouble when they use velocity as a forecast without first adjusting it for holidays, training, detail assignments, and part-time allocation.
Veterans Day lands on a Wednesday this year, right in the middle of a two-week sprint. Two developers have mandatory training, one is on leave, and the team just lost a contractor to a budget cut. Yet the sprint board still shows last sprint’s velocity of 36 points, and leadership expects the same. This is the most common planning error in public-sector agile, and it is fixable.
What is the difference between velocity and capacity?
Velocity is a lagging indicator: the story points the team completed in recent sprints. Capacity is a leading indicator: the person-days available in the coming sprint after subtracting days off, meetings, training, and time allocated to other programs. Velocity answers “what did we get done?” Capacity answers “how much time do we have?” You need both, and you need to combine them correctly.
Where do government teams get this wrong?
Four patterns show up repeatedly:
- Treating average velocity as a promise. The average was earned with a specific team size and calendar. Change either and the number no longer applies.
- Ignoring the public-sector calendar. Federal holidays, agency-wide training windows, fiscal year-end activity, and leave-heavy periods shrink capacity in ways a commercial team rarely sees.
- Counting detailed or part-time staff as full-time. A person at 50% allocation to your team contributes half the days, whatever the org chart says.
- Using velocity to compare teams. Points are relative to each team. Comparing them across teams creates pressure to inflate estimates, which makes the data useless for forecasting.
These errors matter more now. With flat or shrinking budgets and “fewer people, same mission” the norm across FedCiv, DoD, and State and Local, a team that loses members needs to know its real capacity before it commits, not after it misses.
How do you plan a sprint using velocity and capacity together?
- Convert velocity to a rate. Divide completed points by the person-days the team actually had in each recent sprint. This gives points per person-day, which survives changes in team size and calendar.
- Count next sprint’s available person-days. Start with working days times team members, then subtract holidays, leave, training, and the share of each person allocated elsewhere.
- Multiply. Available person-days times your points-per-person-day rate gives a capacity-based forecast.
- Compare to the naive number. If the gap is large, discuss it openly with the product owner before the sprint starts, and decide what moves out of scope.
- Record the reasoning. Keep the days-off, allocations, and resulting commitment together so anyone can later see who was available and why the team committed to N points.
What does this look like with real numbers?
Take a six-person team. In its last three sprints it completed 34, 38, and 36 points, each with full staffing over 10 working days (60 person-days). Average velocity is 36 points, or 0.6 points per person-day.
The next sprint runs November 9 to 20. Veterans Day removes one day for everyone, so the team has 6 people times 9 days, or 54 person-days. One developer is in a three-day training course and another is on leave for two days, which removes 5 more. Available capacity is 49 person-days.
49 times 0.6 equals about 29 points. The naive velocity forecast of 36 overstates what the team can finish by 7 points, nearly 20%. Committing to 36 would nearly guarantee carryover, and carryover is exactly what erodes leadership’s trust in a young agile program. Committing to 29, with a documented reason, makes the sprint a plan the team can meet.
Why does doing this in one tool inside Jira make it repeatable?
The method above is simple. The failure point is the spreadsheet: someone rebuilds it each sprint, calendars are copied by hand, and the reasoning lives on a laptop. As agencies move planning work onto Atlassian Cloud, including Atlassian Government Cloud (AGC) for many public-sector teams, capacity planning belongs next to the backlog it constrains.
Sprint planning with Capacity Planning for Jira puts past velocity, days-off, and allocation on one screen inside the Jira backlog, so you can see capacity against the stories you are about to commit before you start the sprint. The result is a planning record showing who was allocated, which days were subtracted, and how the commitment was reached. The app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II / ISO 27001 platform. It records planning decisions; it is not a compliance product.
Where this fits: the points-per-person-day calculation above is one step in running sprint planning in Jira against the capacity you actually have. For the person-day inputs themselves, see the step-by-step guide to sprint capacity planning in Jira. If the debate on your team is which number should drive the commitment, velocity sets the ceiling and capacity corrects it; for a longer public-sector walkthrough with a matrixed-staff example, read what agile teams get wrong about velocity and capacity.
FAQ
Should capacity replace velocity?
No. Capacity tells you available time; velocity tells you how much work that time has historically produced. Used together, they give a forecast grounded in both calendar and evidence.
How many sprints of history do I need?
Three to six recent sprints with stable team composition is a practical starting point. If the team changed substantially, use only the sprints after the change.
What if leadership insists on the higher number?
Show the person-day math. A one-page comparison of naive velocity versus capacity-adjusted forecast usually moves the conversation from “why so low?” to “what should we descope?”
Try it: Install free on the Atlassian Marketplace · Read the help docs
Not ready to install? Build a three-column worksheet this week: person, available days next sprint, allocation percent. Multiply the total by your points-per-person-day rate and compare it to your last velocity.




Leave a Reply
Your email is safe with us.