見積もりとトラッキングの設定

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. GreenHopper 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 GreenHopper, 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 the Work mode.)
  
• The type of Tracking Statistic you select affects which units are used by the 'Remaining' field, which appears at the bottom right top of each issue in Work mode:
  

Note that 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.

スプリント バーンダウン チャートはトラッキング統計をもとにして作成されます。トラッキング統計にストーリー ポイントを使用している場合、バーンダウン チャートはストーリーごとのストーリー ポイントを示しています。（すなわち、見積統計をバーンダウンしているストーリーは、完了した時点で始めて、グラフ上のバーンダウンとして表示されます。）一方、時間管理を選択した場合、部分的なバーンダウンが表示されます。（すなわち、それぞれの日にその時点までに経過した時間と残余時間です。）