スケジューリングの挙動
The automatic scheduling mechanism is one of the core capabilities of Portfolio for JIRA. It computes an optimized, realistic resource allocation and with that, forecasts release dates, resource utilization and bottlenecks taking into consideration the following aspects:
- Backlog items' priority
- Sequence - Start and end releases' dates
- Estimates and required skill level capacities
- Teams and people's availability
- People's skills - what type of work can each member do.
- Varying availability and absences. For example, vacations, people available only from certain.
- バックログ アイテム間の依存関係
- Work's stages - activities that can happen either in parallel or sequential activities.
- Team's schedules - iterations and sprint lengths, or continuous, day-to-day schedule.
- Configurable constraints for example, how many people can work in parallel on a story.
Automatic release assignment
自動的なリリース割り当ては、固定された終了日が定義されているリリースが 1 つ以上ある場合にのみ動作します。
この場合、リリース割り当てが "計算" に設定されているバックログ アイテムは、それぞれの優先度のランクに応じてリリースに自動的に追加されます。
The scheduling algorithm currently optimizes the scheduling of highest priority items first. Even if there might be a scenario where the team could fit in a bit more capacity into a release if it started with a lower priority item, Portfolio for JIRA will not suggest this in the schedule. Items that have the highest priority should also be started first. Also, you might want to prioritize items with the highest risk first to tackle uncertainty early in the process.
割り当ての計算と静的な割り当て
The following fields can either be assigned statically, or suggested automatically by the scheduling algorithm:
- リリース - 手動: "このアイテムはリリース X に同梱します"、自動: "どのリリースに最適でしょうか?"
- チーム - 手動: "このストーリーはチーム A が実装します"、自動: "スキルとキャパシティに基づいて最適なチームはどちらでしょうか?"
- メンバー - 手動: "ピーターとサラ、または彼らの両方がこれに取り組みます"、自動: "スキルと空き状況に応じ、X、Y、または Z がこのストーリーに取り組むことが望ましいです"
ドロップダウン メニューでフィールドを "計算" に設定すると、次回の再計算時に値が自動的に割り当てられ、フィールドに青色の背景が表示されます。
計画期間
Portfolio for JIRA has a planning horizon of 5 years by default. If you believe that your schedule isn't being displayed properly and your estimates are for less than 5 years, please check your team's capabilities and estimates. If you require a longer planning horizon, up to 30 years, please contact Atlassian Support.