/
User Guide — Scrum Agile Sprint Planning with Capacity Planning for Jira

User Guide — Scrum Agile Sprint Planning with Capacity Planning for Jira

This guide shows Scrum Masters and Agile teams how to plan sprints with real capacity using Scrum Agile Sprint Planning with Capacity Planning for Jira — creating subtasks, estimating and assigning work, and comparing sprint load to planned capacity and past velocity, all on one screen.

Try it free: Scrum Agile Sprint Planning with Capacity Planning on the Atlassian Marketplace — 30-day free trial, supports up to 20,000 users.

1. Installation

  1. Sign in to Jira Cloud as a site administrator.

  2. Go to Apps → Explore more apps and search for Scrum Agile Sprint Planning with Capacity Planning for Jira.

  3. Click Get it now, choose your site, and accept the requested permissions.

  4. Start your free trial when prompted.

2. Opening the planning view

Open a Scrum board and launch the app's planning view from the board. The view brings sprint scope, subtasks, capacity, and velocity together so you never have to leave the screen to plan.

3. Set up teams and capacity

  • Create teams per board. Define a team for the board so the app can track that team's capacity and allocation independently of other boards.

  • Set capacity per sprint. Adjust the team's available capacity for each sprint to reflect who is actually available (time off, partial allocation, etc.).

  • Capacity is expressed in the unit your team plans in — story points or hours.

4. Plan a sprint

  1. Select the sprint you want to plan. You can see current and future sprints and focus on one at a time.

  2. Find stories that need detail. Use the app's filters to surface stories missing subtasks.

  3. Create and assign subtasks on the spot. Add subtasks, assign an owner, and enter a time estimate — all on the same screen, without losing focus.

  4. Watch the sprint load bar. As story points or hours are added, the load bar compares the current sprint commitment against the team's planned capacity and past velocity, so you can avoid over- or under-committing.

5. Work with assignees and aggregates

  • Filter per assignee down to subtasks in both the backlog and the sprint to see exactly what each person is carrying.

  • Read the aggregates. The view shows results per team member and rolled up for the whole team, so the distribution of work is obvious at a glance.

6. Use past velocity

The view shows the team's past velocity alongside current sprint points and planned capacity. Use it as the reality check on every commitment: if the planned load runs ahead of historical velocity, rebalance before you commit.

7. Multi-sprint visibility

Look ahead to future sprints to plan beyond the current one — useful when you're sequencing work or smoothing capacity across several sprints.

8. Tips for predictable planning

  • Start each sprint from baseline capacity, then subtract known time off.

  • Treat the load-vs-velocity bar as the commitment gate — green-light only when load is at or below sustainable velocity.

  • Keep teams defined per board so capacity stays accurate when people work across multiple boards.

9. Getting help