Scheduling

このページの内容

お困りですか?

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

コミュニティに質問

The following scheduling settings are available for configuration in your plan:

Sample scheduling settings in a plan

見積

You can choose which unit to use when estimating issues in your plan.

  • Available for plans that use Scrum boards and Kanban boards as issue sources.
  • Ideal for Scrum and Kanban teams that use time-based estimates for their work.


ストーリーポイント
  • Only available when all the issue sources of the plan are Scrum boards.
  • Once a Kanban board is associated to a plan, story points are no longer available to use.
  • Ideal for Scrum teams that use story point estimates for their work.
  • If you're planning work for Scrum teams, we recommend to use story points when estimating the issues in your plan.

The estimation unit that you choose for your plan impacts the types of teams that you can create in your plan.

  • If you're using days or hours (time-based estimation), you can create both Scrum and Kanban teams in your plan.
    • For Scrum and Kanban teams, the default capacity is set to 200 weekly hours.
    • For Scrum teams, the default iteration length is set to 2 weeks.
  • If you're using story points, you can only create Scrum teams in your plan. The default team velocity is set to 30 story points, and the default iteration length is set to 2 weeks.

See Creating teams for more details.

Dependencies

Regardless of the estimation unit being used in the plan, you can choose how dependent issues can be scheduled.

Scheduling behavior 説明
Sequential Dependent issues cannot be worked on at the same time, whether the issues are manually scheduled or auto-scheduled.
Concurrent Dependent issues can be worked on at the same time, whether the issues are manually scheduled or auto-scheduled.

For example, you have the following in your plan:

  • You have dependent stories TIS-1 and TIS-2, with TIS-1 blocking TIS-2.
  • You have Sprint 1 as the immediate sprint in your plan, and Sprint 2 and Sprint 3 following it.
  • Both issues have the same target start and end dates.
  • Both issues are estimated at 30 story points.
  • Both issues are assigned to the same team, and team velocity is at 30 story points.
  • Both issues are not currently assigned to any sprint.

While the issues have no assigned sprint, the badges will turn red. This is because the dependent issues have the same target dates, which is not a realistic schedule because TIS-1 is blocking TIS-2. Thus, the badges will turn red.

最終更新日 2019 年 6 月 27 日

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

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