Short answer: Sprint overcommitment happens when a team accepts more work than its real, available capacity can deliver, usually because planners reuse last sprint’s velocity without subtracting holidays, leave, training, and part-time allocations. You avoid it by committing from available capacity, not from optimism.
It is the second week of the sprint. A report promised to a legislative oversight office is due Friday, two developers are out, and the team is still holding eleven unfinished stories. Nobody planned for failure. They planned for the sprint they wished they had. In government, where fiscal-year dates and reporting chains do not move, that gap gets expensive fast.
What does overcommitment actually cost a public-sector team?
The visible cost is carryover: stories that roll into the next sprint. The hidden costs are larger. Velocity data becomes unreliable, so the next forecast is also wrong. Leadership hears “on track” until the week it isn’t. Staff work late to close the gap, and with agencies running leaner teams (fewer people, same mission), there is no slack left to absorb the miss.
Fixed budgets and fiscal-year deadlines make it worse. A team that quietly slips two points every sprint has slipped a full release by the time the quarter ends, and the PMO sees it only at the end.
Why does optimistic planning keep happening?
Three habits cause most of it. Planners treat velocity as a promise instead of an average. They count headcount, not available days. And they let pressure from stakeholders set the number instead of the calendar. Each is understandable; none is visible in a spreadsheet that was last updated three sprints ago.
How do you avoid overcommitting in a sprint?
- Start from calendar days, not people. Multiply team members by working days in the sprint, then remove federal holidays that fall inside it.
- Subtract known absences and splits. Take out approved leave, scheduled training, and the share of each person’s time allocated to other programs or details.
- Convert to points with a per-day rate. Divide recent average velocity by the average available person-days in those sprints. Multiply by this sprint’s available person-days.
- Commit at the forecast, and name a stretch list. Commit to the forecast number. Keep two or three ready stories outside the commitment so finishing early has a plan.
- Write the decision down. Record who was allocated, what was subtracted, and why the team committed to N points.
That last step matters beyond planning. Agencies are being asked more often to show what happened, who acted, and what evidence supported a decision. A sprint record that states the capacity assumptions gives a PMO a clear trail. It is documentation of planning decisions, not a compliance program.
What does this look like with real numbers?
An illustrative example for a six-person team in a 10-working-day sprint that includes Veterans Day:
- Gross capacity: 6 people × 10 days = 60 person-days.
- Holiday: 6 × 1 day = 6, leaving 54.
- Leave: one developer out 3 days. Training: one tester out 2 days. Leaves 49.
- Split allocation: one analyst is 50% on another program, so 4.5 of their 9 remaining days are removed. Leaves 44.5 available person-days.
The last three sprints averaged 38 points on about 52 available person-days, or roughly 0.73 points per person-day. For this sprint: 44.5 × 0.73 ≈ 32 points.
An optimistic plan repeats 38. That is six points, about 19%, above what the calendar supports. The 32-point commitment is not pessimism; it is the same team performing at the same rate with fewer available days.
How does one tool inside Jira make this repeatable?
The method works on paper, but it decays on paper. Spreadsheets drift from the backlog, and someone has to re-key leave dates every sprint. Doing the arithmetic where the work lives is what makes it routine, and it fits the broader move many agencies are making toward Atlassian Cloud, including Atlassian Government Cloud (AGC).
Sprint planning with Capacity Planning for Jira puts sprint and team capacity on one screen inside the Jira backlog. It uses past velocity, days-off, and allocation so you can see the forecast before you commit. The app is Cloud Fortified and runs on Atlassian’s SOC 2 Type II / ISO 27001 platform. It records planning inputs; it is a planning tool, not a compliance product.
FAQ
How much should a team commit relative to its average velocity?
There is no universal percentage. Commit to average velocity adjusted for this sprint’s available person-days, as in the example above. If availability is down by 15%, the commitment should be too.
Should we count holidays and training when forecasting?
Yes. They remove working days from the sprint, and they are known in advance, which makes them the easiest source of overcommitment to prevent.
What if leadership insists on a higher number?
Show the capacity arithmetic. A transparent list of available days and allocations turns a negotiation about willpower into a conversation about scope.
Try this readiness check: before your next planning session, list available person-days for the sprint and compare the result to the number you were about to commit. If they disagree by more than 10%, revisit the commitment.
Try it: Install free on the Atlassian Marketplace · Help docs




Leave a Reply
Your email is safe with us.