見積もりとトラッキングの設定
This page only applies to Scrum boards.
見積とトラッキングについて
Many Scrum teams separate estimation (which is used for measuring the size of a backlog and calculating velocity) from tracking (which is often the burndown of hours used during the Sprint to be sure we're not way off the pace necessary to complete the stories in the Sprint timebox), and use different units for each. A common approach is to estimate tasks in Story Points, then track tasks using hours. JIRA Agile therefore gives you the flexibility to set your estimation and tracking statistics differently, depending on what best suits your team.
Product teams often need to be able to estimate how long a product will take to deliver. This is tough because the backlog may stretch many months into the future, so the team can only provide a very rough estimate in conditions of uncertainty without wasting days breaking the work down. However, from sprint to sprint as they work through the stories the team will develop a cadence of completing <x> units of work they had 'rough estimated', i.e. their velocity. This means that they can relatively accurately estimate how long portions of the backlog will take to get done with simple rough estimates that the team can produce way before they even consider doing them. However, to make this work the team needs to estimate stories with a consistent level of uncertainty. The team also needs to track the amount of estimation units they have actually fully completed from sprint to sprint because this number is the one that tells us with relative certainty how much we can fit into each future sprint and have conviction that they will all be completed.
独自の見積統計とトラッキング統計が選択可能
In JIRA Agile, you can choose which type of units (e.g. Story Points, Issue Count) will be used for estimating and tracking issues. You do this by choosing an Estimation Statistic, then choosing to either use the same units for your Tracking Statistic or to use time-tracking. Each board can have a different type of Estimation Statistic and Tracking Statistic.
- The type of Estimation Statistic you select affects which units are used by the 'Estimate' field, which appears at the right of each issue in Plan mode: (Note that the 'Estimate' field is editable when an issue is in Plan mode, but not editable once the issue moves into Work mode.)
- The type of Tracking Statistic you select affects which units are used by the 'Remaining' field, which appears at the bottom right of each issue in Work mode:
ベロシティとバーンダウンの表示
A team's velocity is based on the Estimation Statistic — ie. for each sprint, the velocity is the sum of the Estimation Statistic for completed stories. Velocity is shown in the Velocity Chart and also on the Sprint Report, in the Estimate Statistic column header of the "Completed Issues" table (e.g. "Story Points (12)" means that 12 Story Points were completed in that sprint). Please note that the values for each issue are recorded at the time when the issue moves into the sprint. Changing the Estimate value afterwards will not be reflected in the Sprint Report, but will be shown as scope change in the burndown. Velocity is also used in the Version Report, to predict Release Dates.
The Sprint Burndown Chart is based on the Tracking Statistic. If you are using Story Points as your Tracking Statistic, then the Burndown Chart shows the Story Points per story (ie. stories burning down the Estimate Statistic are only burnt down on the graph as they are completed); whereas if you choose the Time-tracking option you are shown partial burndown (ie. the number of hours currently used and remaining each day).
見積統計の設定
見積統計をボードに設定する手順は、次のとおりです：
- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest. Note that only the administrator of a board (or a person with the 'JIRA Administrators' global permission) can configure a board.
- 見積タブをクリックします。
見積統計フィールドで、次のオプションのいずれかを選択します。
見積統計
説明：
ストーリーポイント
課題ごとのストーリーポイントの数をもとにして見積もります。これが最も一般的に使用されるオプションです。
(
Note that, by default, the Story Points field is only available to issues of type 'Story' or 'Epic' — you can change this as described in JIRA Agile - JIRA Configuration.)事業価値
課題ごとの事業価値をもとに見積もります。
初期見積り
Estimation will be based on the JIRA 'Original Estimate' field (for details see the JIRA documentation Logging Work on an Issue). By default this is specified in minutes, but it can be hours/days/weeks depending on your JIRA system configuration (for details see the JIRA Time Tracking documentation).
課題数 スプリントの課題の数をもとに見積もります。「見積」 フィールドは編集できません。 <カスタムフィールド> JIRA システムの任意の数値形式のカスタムフィールドをもとに見積もります。
スクリーンショット：「見積」タブ（クリックで拡大）
時間管理を有効にする
If you enable time tracking, you will be able to view the remaining time estimate for an issue (and its sub-tasks), when viewing an issue.
トラッキング統計をボードに設定する手順は、次のとおりです：
- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
- 見積タブをクリックします。
時間管理フィールドで、次のオプションのいずれかを選択します。
トラッキング統計
説明：
なし
見積統計をもとにしてトラッキングします。
残余見積時間と消費時間
Tracking will be based on the JIRA 'Remaining Estimate' and 'Time Spent' fields (for details see the JIRA documentation Logging Work on an Issue). By default these fields are specified in minutes, but you can use hours/days/weeks depending on your JIRA system configuration (for details see the JIRA Time Tracking documentation).
この方法は、見積統計を使う方法と基本的に異なっていることに注意してください。というのは、これらの数値は課題が完了したときにバーンダウンするのではなく、ユーザーが消費時間または残余見積時間に新しい値を設定した時にのみバーンダウンするためです。