Capacity and velocity

On this page

In this section

Still need help?

The Atlassian Community is here for you.

Ask the community

The number of story points or hours your team can complete in one iteration is referred to as its capacity. For example, an iteration with a capacity of 30 story points (which is the default setting) can contain six issues that are estimated at five story points each.

Velocity, which is used strictly for planning purposes, is your team’s average capacity per iteration over time based on past performance. For example, a team with a velocity of 30 story points will require two sprints to complete an epic estimated at 35 story points, assuming no other work was already assigned to those sprints.

Once you've set up capacity planning, you can then monitor capacity from your timeline

Enable capacity in your plan

To view capacity on your timeline, navigate to the in the View settings menu, group your issues by Team or Sprint, then select the checkbox next to Show capacity on timeline.

Once enabled, visit the Assign capacity page to learn more about managing the capacity of teams and sprints, and how capacity is calculated.

Plan scenarios using capacity

The Scenarios tool in Advanced Roadmaps lets you create several “what if” versions of your roadmap based on changes in capacity, teams, and more. From these multiple versions, you can select which one you want to keep as your plan, and save it back to Jira Software.

Last modified on Apr 21, 2021

Was this helpful?

Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.