Key Takeaways
- Capacity planning in Jira means planning each sprint against real team capacity and past velocity rather than headcount or wishful thinking.
- Capacity numbers only matter when they shape the commitment, so a sprint is planned against who is actually available once leave and part-time allocation are subtracted.
- Divim’s Sprint Planning, Capacity and Resource Planning for Jira puts past velocity, planned capacity, and allocation on one screen, with capacity adjustable per sprint including days off.
- Seeing sprint load against capacity as work is added lets a team stop over-committing before the sprint starts.
Capacity planning in Jira means planning each sprint against real team capacity and past velocity, not wishful thinking. This hub collects Divim’s guides on forecasting, velocity, and capacity-aware planning for enterprise Agile teams.
Capacity numbers only matter when they shape the commitment: once you know who’s actually available, plan the sprint against that capacity instead of headcount.
How to do capacity planning in Jira, step by step
- Start from available days, not headcount. For each person, take the working days in the sprint and subtract planned leave, public holidays, and training. See capacity planning around PTO and holidays in Jira.
- Apply real allocation. Someone split 50/50 across two teams brings half their days to each. Remove time for support rotations and recurring meetings too. For mixed or part-time teams, use the method in how to calculate team capacity when half your team is part-time.
- Convert capacity into the unit you plan in. If you estimate in story points, scale your recent average velocity by this sprint’s available days versus a normal sprint. If you plan in hours, use the net hours directly.
- Check velocity against capacity before committing. Velocity tells you what the team finished in the past; capacity tells you who is here this time. When the two disagree, capacity wins. More in capacity vs velocity in sprint planning.
- Fill the sprint to capacity, not past it. Pull backlog items in priority order until the planned load meets the capacity line, and leave a buffer for unplanned work. Then run sprint planning in Jira against that number.
Where Jira helps, and where it stops
Jira’s velocity chart shows what each sprint completed, and Jira Plans (Advanced Roadmaps, on Premium and Enterprise) lets you set a team’s capacity per iteration. What standard Jira boards don’t give you is a per-person view of availability inside the sprint, which is why many teams keep a side spreadsheet. If that sounds familiar, read the sprint planning capacity spreadsheet: keep it, fix it, or kill it?
Start here
- Advanced Agile Planning for Jira
- Streamline Agile Planning with Divim’s Sprint and Capacity Planning
- Streamline Jira Planning with Sprint Capacity
- Driving Predictability in Software Development
- Sprint Planning and Capacity Planning for Jira: What’s New
- Agile Capacity Planning for Government Teams
- Capacity Planning Template: Keep the Capacity Field Live
Get the app
Sprint Planning, Capacity and Resource Planning for Jira puts past velocity, planned capacity, and allocation on one screen: adjust capacity per sprint (days off included) and stop over-committing before the sprint starts.
Try Sprint Planning & Capacity free on the Atlassian Marketplace →