作業の進捗状況の監視

このページの内容

お困りですか?

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

コミュニティに質問

チームの進捗を監視することは、それらを計画することと同じぐらい重要です。進捗を監視することで、潜在的なボトルネックを素早く確認し、それらが実際に発生しないように対応できます。

There are several ways to monitor the progress of the work of your teams across your plans.

進捗バーの使用

You can add the progress columns in your roadmap, to visualize the issues in your plan with the following status categories:

  • TO DO for issues that are still in the To do status category
  • IN PROGRESS for issues in the In progress status category
  • DONE for issues in the Done status category
You can choose to display progress using estimates or issue count, or both by adding these columns to your plan.

This sample plan is using hours to estimate issues, and the two progress columns are displaying progress in terms of estimated story points and number of issues.

Jira Software で完了とマークされ、解決状況が設定されていない課題は、プランには含まれません。

How estimate-based progress works

If you hover on the progress bar of a parent issue, the breakdown of work will take into account the estimates of all descendant issues and the estimate of the issue itself. If the parent issue is unestimated, it will still have a progress bar, but only the aggregated estimates of the descendant issues will be considered.

In the example above, the progress details show the following:

  • The progress bar is broken down into two colors that represent completed and remaining work:
    • COMPLETED is the sum of the logged hours for all child issues in To do and In progress status categories, and the total time for any child issues in Done status category.
    • REMAINING is the sum of the remaining hours for all child issues in To do and In progress status categories.
  • The breakdown of estimated issues and unestimated issues will also be displayed. Note that progress may be inaccurate due to any unestimated issues.
  • If you complete a parent issue, but its child issues are not yet completed, and have remaining hours logged against them, the remaining hours will not be added to the completed hours of the parent issue. The remaining hours will be calculated as remaining hours of the child issues.
  • If you've enabled rolled-up values in a plan, the remaining estimates of Done child issues will roll up to their parent issues. This calculation is inconsistent with how completed and remaining estimates are calculated in the progress bar. This means that you may see inconsistent values between rolled-up estimates of a parent issue and the estimate values in the progress bar of the same parent issue.
  • If you use days to estimate work in your plan, the progress details will be displayed in day units accordingly.
  • Any issues that are not saved to Jira will not be taken into account in calculating progress.

For issues without child issues, the percentage of completed work against remaining work will also be displayed.

How issue count progress works

If you hover on the progress bar of a parent issue, the breakdown of work will take into account the number of issues in the different status categories, the total number of issues in the plan, and the percentage of the number of issues in each status category against the total number of issues.

In the example above, the progress details show the following:

  • イニシアチブ PM-4 には 2 つの子エピック (PLAT-2 およおび WEB-23) があります。この場合、進捗バーは合計 2 つの課題を網羅します。 
  • There is 1 issue that's still to do: WEB-23. Since there's a total of 2 issues, WEB-23 is 50% of the total issue count.
  • There's also 1 issue that's already done: PLAT-2. This issue is also 50% of the total issue count.
  • The estimates for each issue are not taken into account by the progress bar, since progress here only covers issue count.

Any issues that are not saved to Jira will not be taken into account in calculating progress.

Monitoring capacity

To monitor capacity in your plan, you first need to show capacity in the timeline of your plan. This is only possible if you group issues by teams and sprints.

チームでキャパシティを表示すると、チーム固有の課題が複数のスプリントにどのように分散しているかを視覚化できます。これは、スプリントにスケジュールされている作業が多すぎないかどうかを判断し、リソースが不足しているスプリントの作業を分散させる方法を計画するのに役立ちます。


Sample of an overbooked sprint

In the example above, the Wallaby sprint is showing a red capacity bar, which means too much work has been allocated to that sprint. You can quickly fix this up by removing some issues from that sprint, or adding more people to the team.


健全なスプリントの例

Clicking the capacity bar of a sprint will display the following:

  • sprint name
  • sprint start and end dates
  • status of the sprint (for example, active or future sprint)
  • sprint goal (if added in Jira)
  • sprint velocity
  • percentage of how full the sprint is in estimated story points
  • percentage of issues that have been completed (if sprint is active)

Understanding capacity details in Scrum and Kanban

For both Scrum and Kanban teams, the capacity bars reflect how work is evenly distributed across the corresponding duration (sprints for Scrum, iterations for Kanban). This is the basic premise on how work is distributed in the current plans.

ただし、キャパシティの詳細がどのようにバーに反映されるかについては、いくつかの相違点があります。

For Scrum teams:

  • ストーリー ポイントの見積りを使用する場合、スプリントの期間に対してベロシティが測定されます。ベロシティが 2 週間のスプリントに対して 30 ストーリー ポイントに設定されている場合、キャパシティの詳細には、見積られたストーリー ポイントに関して、スプリントの埋まり具合がパーセンテージで表示されます。
  • 時間ベースの見積りを使用する場合、キャパシティは 1 週間の期間に対して測定されます。週のキャパシティが 2 週間のスプリントに対して 200 時間に設定されている場合、キャパシティの詳細には、見積られた時間に関して、スプリントの埋まり具合がパーセンテージで表示されます。
  • Even if a story spans multiple sprints, its estimate will consume capacity from the sprint that's assigned to it. For instance, TIS-123 is scheduled for 20 days, and it spans sprints 1 and 2 because each sprint runs for 10 days. TIS-123 is assigned to sprint 1, so its estimate of 30 story points will be allocated to sprint 1.

For Kanban teams:

Capacity is measured against the duration of a week. If weekly capacity is set to 200 hours, then the capacity details will show the percentage of how full the iteration is in terms of the estimated hours.

リリースの監視

複数のプロジェクト、チームおよびリリースをまたいだ作業の管理は、特にチームの進捗を素早く確認する必要がある場合は複雑になることがあります。

From the releases view

You can jump to the releases view of your plan to grab a high-level view of how work is tracking. This will help you determine if your teams can realistically complete the work assigned to the releases in your plan.

Releases view with sample releases

In the example above, you can quickly see the how each release is tracking. As long as the start and end dates of the issues fall within the start and end dates of their corresponding releases, then the releases stay on track.

次のいずれかの手順を実行して、このリリースの妨げになっているものを掘り下げることができます。

  • プランのロードマップでリリースを表示し、保留中の課題にブロッカーが存在しないかを確認します。
  • For project releases, view the release in Jira, to see a condensed list of all the issues assigned to that release, and possibly to change the release dates as needed.
  • リリースの進捗バーにカーソルを合わせ、完了が必要な課題の数を確認します。
    (warning) 現時点では、進捗バーには現在プランで表示可能な課題の詳細のみが含まれます。つまり、古いリリースの情報は正確ではない可能性があります。

タイムライン セクションから

You can also track the progress of releases directly in the timeline section of a plan.

Sample plan with releases in the timeline

Green icons represent releases that are on track, while red ones are for releases that are off track. As long as the start and end dates of the issues fall within the start and end dates of their corresponding releases, then the releases stay on track. Click on an icon to view more details about the release, and more importantly, to determine how you can fix the state of off track releases.

The number of releases could accumulate over time, which can make it hard to navigate from one release to another on the timeline. There may be times when releases are only one day apart, or there may be multiple releases scheduled on the same day.

If this happens in your plan, try doing one of the following:

Jumping from one release to another

リリース アイコンをクリックし、左矢印または右矢印をクリックして次のリリースにジャンプします。

While jumping from one release to another, the details of each release will be displayed accordingly.

Sample multiple releases on the timeline

Viewing details of multiple releases

Occasionally, you may see a number above a release icon. In the sample release below, the number denotes that there are two releases scheduled on the same day.

Click on the release icon to see the releases scheduled for that day, and then click the right arrow of each release to view more details about it.

同じ日にスケジュールされたリリースの例

タイムラインでのリリースのハイライト

If there are any releases that you want to keep an eye on, you can highlight these releases on your timeline. This helps make any relevant releases stand out in your timeline.

[タイムラインでハイライト] チェックボックスを選択すると、タイムラインのリリースに赤または緑色の線が表示されます。

Sample releases highlighted on the timeline

課題をリリースでフィルタリング

You can also filter issues by a release, which will display the corresponding issues filtered by sprint in the roadmap view.

ロードマップ ビューでリリースでフィルタリングした課題の例

課題をプロジェクトでフィルタリング

You can also filter issues by projects, which will display only the releases of the relevant projects. To further narrow down on the release details, consider filtering the issues by a single project.

Issues filtered by the IOS project, with releases filtered as well

最終更新日 2020 年 8 月 10 日

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

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