Measurements
This custom category lists measurements that apply to adoption of iterative development practice.
Relationships
Main Description

The following metrics can be use to measure how well you are adopting Iterative Development practice objectively.

Core Metrics

  • Burndown Chart- to track progress of iteration and showing remaining estimation effort to complete all open work that assigned to a given iteration.
  • Iteration Velocity - to masure the capability of the team. How much the team can achieve in an iteration.
  • Test Coverage - to measure what proportion of new code is executed per iteration. This metrics can tell you that there are executed and tested code being produced in each iteration.
  • Defect Density at Customer Ship - to measure the quality of code being produced at a given iteration.
  • Code Health - to ensure that the regression has been done in a given iteration and to make sure the health of build at the end of iteration.

Supplementary Metrics

  • Iteration Length - to ensure resonable iteration length
  • Blocking Work Items - to ensure that the road blocks are managed during an iteratio.
  • Deferred Work Items - to measure the capability of the team. How much the team can achieve in an iteration. 
  • Schedule Performance Index - to measure the schedule efficiency of the team.
  • Cost Performance Index  - to measure the cost efficiency of the team.
  • New Unique Test per Iteration - to ensure that the new code has been tested
  • Test Case Execution Status - to show what planned testing is complete, with what level of success, and what testing is still outstanding.
  • Test Density - to ensure the level of test has been done.