Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
Capacity for Scrum teams
When scheduling work for Scrum teams, capacity is calculated differently for time-based estimates and story points:
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 your team’s capacity is 40 hours and your iterations last two weeks, your team’s sprint capacity will be 80 hours.
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.
Was this helpful?