Managing capacity

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

When managing work across multiple teams, it can be too easy to assign too much work to a team, thereby exceeding the capacity of that team. Portfolio for Jira makes it easy for you to monitor team capacity in the improved interface.

  

An overbooked sprint vs a healthy sprint in the timeline

What is team capacity?

Team capacity is simply defined as the ratio of the units of work that a team takes on for a given period of time against the maximum units of work that a team can take on for that given period of time. "Maximum units of work" essentially mean the one of the following:

  • For Scrum teams using story points, this is the velocity of a sprint.
  • For Scrum teams using time-based estimates (days or hours), this is the weekly capacity (in hours) of the team.
  • For Kanban teams, this is the weekly capacity (in hours) of the team.

See how to set the maximum units of work in Creating teams.

From the sample sprints provided, note the following details:

  1. The associated team estimates work in story points, and is therefore a Scrum team.
  2. From the sprint dates, we can infer that the Scrum team works in 2-week sprints.
  3. In each sprint, the team has a velocity of 30 story points. This means that the team can finish a maximum of 30 story points in each sprint.
  4. Sprint Dingo has been allocated 32 story points, which exceeds team velocity. Sprint Dingo is then overbooked, and is displaying a red capacity bar.
  5. Sprint Quoll has been allocated 18 story points, which does not exceed team velocity. Sprint Quoll is then a healthy sprint, and is displaying a green capacity bar.

At any time, you may need to do any of the following tasks, to manage team capacity:

最終更新日 2019 年 7 月 28 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.