Sprint Planning, Capacity & Resource Planning for Jira brings capacity-aware planning right into your backlog. It reads each board’s past sprint data and velocity, then helps you fill a sprint to the team’s real capacity — so you commit to what you can actually finish instead of over-committing on headcount alone.
1. Configure your boards
From Jira’s left sidebar, open Apps → Sprint Planning Configuration. On the configuration screen, pick the Scrum boards you want to plan with and save. The app then reads past sprint data and calculates velocity from each board’s Estimation configuration (story points, issue count, etc.).
- Select boards — choose the Scrum boards to enable capacity planning on. The app reads past velocity from each board’s estimation statistic.
- Save — apply your selection, then open any selected board to start planning.
2. Plan a sprint against real capacity
Open one of your configured boards and launch the planning view (use Back to the board from the configuration screen, or the app’s entry on the board). As you add work to the sprint, the app compares the committed total against the team’s capacity and recent velocity, warning you before you over-commit.
- Velocity is derived from completed work on past sprints for the selected board.
- Capacity reflects who is actually available for the sprint, so the plan accounts for part-time members and time off.
- Resource planning lets you balance work across people rather than dumping it on the team as a whole.
Tip: make sure each board’s Estimation setting (story points vs. issue count) matches how your team actually estimates — that statistic drives the velocity calculation.
Need help?
Questions or feature requests? Reach the Divim team through our Help Center, or view the listing on the Atlassian Marketplace.