The following metrics can be used to objectively measure how well your team is adopting an iterative development
practice.
Core Metrics
-
Burndown Chart: to track progress of an iteration and show the remaining
estimated effort to complete all open work assigned to a given iteration.
-
Iteration Velocity: to measure the capability of the team, or how much the team
can achieve in an iteration so they can adjust the plan accordingly.
-
Code Coverage: to measure what proportion of new code is executed per iteration.
This metric can tell you how much code is being produced,executed and tested in each iteration.
-
Defect Density at Customer Ship: to monitor the quality of the product during
the development lifecycle, and to indicate the quality at customer-shipment time.
-
Code Health: to ensure that the regression has been done in a given
iteration, and to assess the build health at the end of an iteration.
Supplementary Metrics
-
Iteration Length: to ensure a reasonable iteration length.
-
Blocking Work Items: to ensure that the road blocks are managed during an iteration.
-
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 that the appropriate level of testing has been done.
|