チームのキャパシティについて理解する

このページの内容

お困りですか?

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

コミュニティに質問

To manage the capacity of the multiple teams in your plan, we recommend that you have a good grasp of the concept of capacity in the improved interface. Team capacity is 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.

When you're showing team capacity in the timeline, capacity bars will display in the timeline, and these bars will reflect how work is distributed across the corresponding duration. For Scrum teams, this duration would be sprints. While for Kanban teams, this duration would be iterations. There are differences on how work is distributed and how capacity is represented across both types of teams:

スクラム チームでのキャパシティの取り扱い

These are some details to take note of when managing the capacity of Scrum teams.

Scrum teams estimate work in either story points or time-based estimates

When using story points, team velocity is measured against sprint duration.

For example, if velocity is set to 30 story points for a 2-week sprint, then the capacity details will show the percentage of how full the sprint is in terms of the estimated story points against the total velocity.

ストーリー ポイントの見積りを使用しているチームのスプリントの例

When using time-based estimates (days or hours), capacity is measured against the duration of a week.

If weekly capacity is set to 160 hours for a 2-week sprint, then the capacity details will show the percentage of how full the sprint is in terms of the estimated hours against the total hours (320 hours) for the 2 weeks.

時間ベースの見積り (時間) を使用しているチームのスプリントの例

The estimate of an issue that spans multiple sprints will consume capacity from its assigned sprint

This only applies to Scrum teams, and to issues of the epic hierarchy level and above.

For instance, the epic TIS-123 is scheduled for 20 days, and it spans sprints 1 and 2 because each sprint runs for 10 days. Let's also say that velocity is set to 30 story points for each sprint.

  • If TIS-123 is assigned to sprint 1, and has an estimate of 30 story points, then its estimate of 30 story points will be allocated to sprint 1.
  • If TIS-123 is assigned to sprint 1, and has an estimate of 50 story points, then its estimate of 50 story points will be allocated to sprint 1. Sprint 1 will then be overbooked, and will display a red capacity bar.

An issue that spans multiple sprints, and is not assigned to any of these sprints, will equally consume capacity from the sprints

For instance, the epic TIS-123 is scheduled for 20 days, and it spans sprints 1 and 2 because each sprint runs for 10 days.

If TIS-123 is not assigned to any of the 2 sprints, then its estimate of 30 story points will be equally distributed among the 2 sprints. Sprint 1 will be allocated 15 story points, and the rest of the 15 story points will be allocated to Sprint 2.

カンバン チームでのキャパシティの取り扱い

Capacity for Kanban teams is measured against the duration of a week. Even if you can set the weekly capacity (days or hours) of a Kanban team, there is no way to change the iteration length, and it will stay a week long.

1 週間のカンバン チームの見積り時間の例

上記の例では、キャパシティは週あたり 200 時間に設定されています。そのイテレーションにおける課題の見積り時間とステータスに基づいて、次の詳細がわかります。

  • この時点で 200 時間のうち 0 時間が終了しているということは、作業の 0% が完了しているということになります。
  • チームの週のキャパシティである 200 時間に対して 200 時間がコミットされているということは、その週のチームのキャパシティ全体の 100% に達しているということになります。

1 つのストーリーが複数の週にわたる場合、キャパシティはその週に均等に配分されます。

2 週間にわたるカンバン課題の例

上記の例で、課題は 100 時間かかると見積られ、2 週間にわたっています。この場合、キャパシティは 2 週間で均等に配分され、各週のキャパシティに対して 50 時間コミットされます。

最終更新日: 2019 年 10 月 18 日

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

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