Assign capacity

Capacity and velocity

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Before you can manage the capacity of a sprint or team, capacity must be enabled on your timeline.

In order to use the capacity management function, issues need to be assigned to a sprint and a team that uses boards as their issue source. This allows you to manage active sprints, plan future capacity, and assign issues to sprints directly from your plan. Issues pulled from other sources such as filters or projects will appear as external sprints in your plan.

Capacity for Scrum teams

When scheduling work for Scrum teams, capacity is calculated differently depending on which units you use to estimate work:

  • If you’re using time-based estimates, the sprint capacity is determined by taking the weekly capacity and multiplying by the number of weeks per iteration. For example, if you set the capacity at 40 hours, the sprint’s capacity will be 80 hours, assuming a two-week sprint.

  • If you estimate in story points, no conversion is necessary since story points are defined per iteration. The capacity applies to the whole sprint. By default, this is set to 30 story points, though you can adjust this to meet your team’s needs.

Capacity for Kanban teams

Kanban teams can only use time-based estimates.

For Kanban teams, work is broken down into iterations which each last one week. You can set the weekly capacity of a Kanban team in either days or hours, but the length of the iteration cannot be changed.

Assign capacity

Once enabled, select the sprint's tab from the timeline to open the sprint flyout window which shows critical information about the health of the sprint. To learn more about how to monitor your sprint capacity from your timeline, head over to the Monitor capacity page.

Advanced Roadmaps assigns capacity on a first-come, first-served basis. Any issue that you want to include in your capacity calculations need to be estimated first, either in story points or hours/days; unestimated issues won't consume capacity. If the amount of work assigned to the iteration exceeds its capacity, the sprint progress bar turns red to indicate the iteration is overbooked, as shown below:

If you need to schedule an issue over multiple iterations, it will consume all of the available capacity in the first iteration before moving on to the next one. Alternatively, we recommend breaking issues down into smaller subtasks which can then be assigned to separate iterations.

Issues that have start and end dates that fall during a sprint--but is not assigned to the sprint-- will still consume capacity from it. In the sprint flyout window, these issues are marked with the label x issues not assigned to sprint. Similarly, issues that are assigned to a sprint but aren't estimated are listed with the label x unestimated issues.

Change iteration capacity

The capacity of your iterations can fluctuate for several reasons. Examples include public holidays, a sick team member, or team members spread across different projects.

In these situations, you can keep the sprint (and therefore your plan) accurate by editing its capacity via the sprint details flyout. To change the capacity of a sprint, select the number next to the Sprint capacity field, and enter a new value:

When you’re done, select the checkmark to confirm the change. This can be done for active and future sprints.

Last modified on Sep 6, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.