Assign capacity

Capacity and velocity



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


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.

スクラム チームのキャパシティ

スクラム チームの作業をスケジュールする際は、作業の見積もりに使用する単位に応じてキャパシティの計算方法が異なります。

  • 時間ベースの見積もりを使用している場合、スプリント キャパシティは、週ごとのキャパシティにイテレーションごとに週数を掛けることによって決定されます。たとえば、2 週間のスプリントを想定した場合、キャパシティを 40 時間に設定した場合、スプリントのキャパシティは 80 時間になります。

  • 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.

カンバン チームのキャパシティ

カンバン チームは、時間ベースの見積もりのみ使用できます。

カンバン チームの場合、作業は、それぞれ過去 1 週間のイテレーションに分割されます。カンバン チームの週次キャパシティは日数または時間単位で設定できますが、イテレーションの長さは変更できません。

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.

最終更新日 2021 年 4 月 21 日


Powered by Confluence and Scroll Viewport.