4.6.1. Individual Statistics

Several pieces of data are tracked daily during an iteration to measure the iteration's progress over time.

Assigned Issues

Very simply, the list of issues assigned to the iteration is stored each day so that changes to the plan can be tracked.

Estimated Time

Assuming the assigned issues have been given time estimates, the total of those time estimates being the total estimated time for the iteration is stored each day. As the assigned issues and time estimates are updated, the changes are tracked in the statistics.

Logged Time

When the time tracking features of AgileTrack are in use, the amount of time logged working on issues in the iteration is logged. As issues are added or removed from an iteration, the logged time only pertains to the issues still assigned to the iteration.

Unit-tested Issues

Just as the list individual assigned tasks and stories is tracked daily in the iteration statistics, the list of issues which have been marked unit tested is also tracked. Each day, as issues are marked unit tested, the number of tested issues is logged.

Verified Issues

To track the completion progress of the iteration, each issue that is verified is stored in the iteration statistics. When compared to the list of assigned issues, iteration progress can be viewed accurately over time.

Completed Time

As issues are marked completed, the time estimates for those issues are summed up to calculate the total completed time for the iteration. So, as issues are completed, the estimated progress of the iteration is also tracked.

Iterations statistics are tracked by AgileTrack so that they can be used in charts and reports to show the progress of iterations over time. For example, a burn-down chart shows the number of total issues versus the number of remaining issues in an iteration from start to finish.

Next Section: 4.6.2. Charts