Goals

The new accuracy view shows some rollup numbers useful to know what happened during an iteration.
The goal is to provide high level hour counts to be used in retrospectives about

1. How much scope did we add to this iteration
2. How much scope did we postponed
3. How much was over-estimated
4. How much was under-estimated

All metrics are computed based on the disposition of stories and tasks. In the rest of this page, mentions of ADDED, DISCOVERED, PLANNED... refers to the different values of story and task disposition

Metrics

Added hours

Total up the estimated/actual hours of all tasks that are marked ADDED. All tasks of ADDED stories are ADDED as well.

Postponed hours

Total up the postponed hours of all stories. The postponed hours of a story is the total of the remaining hours of
all continued tasks at the time they were continued (when a story is continued, all tasks are continued).

Difference between Moving and Continuing moved tasks are not taken into account in the calculation of postponed hours. Moving is a planning operation that is supposed to be used before the start of an iteration. Once an iteration is started we should use continue instead as it is a tracking operation. move is still available as a way to fix an iteration w/o tracking.

Over-estimated hours

Total up the difference between actual and estimated when the story actual is less than the story estimate

Under-estimated hours

Total up the difference between actual adn estimated hours when the story actual is greater than the story estimate

Issues

How should we handle DISCOVERED tasks?
Should they be considered

1. misestimation and included in the normal underestimated hours calculation or
2. added scope and included in the iteration added hours