A list of 16 metrics at iteration level have been defined in VelociQ.

Some of them
are mandatory and some of them are applicable at release level. The entire list is
mentioned here please refer to the agile life cycle model for definitions and norms.

Schedule deviation should be ideally zero in all iterations this is measured to

ensure if the iterations are really time-boxed. At a release level, this is measured to
check if there was any delay with respect to the originally planned release dates.

Effort deviation is measured to check how good the estimates were.

Planned and Actual Utilization factor is an indicator of the how well the people in
the team were utilized. This will also help in determining the planning effectiveness
and to check if the team really has a sustainable pace.

The Customer Induced Volatility at an iteration level, checks for compliance to

scrum practice of not allowing changes in the iteration. At a release level, this helps
in determining the flexibility utilized by the customer.

Commitment Slippage, is specific for Agile projects. This determines how good the
team was in meeting the committed deliverables.

Agile recommends closing all the defects identified in the same iteration. This
may not always be the case, as iterative cycles are time boxed and some low
priority defects may be addressed in the next iterative cycle. Measuring Defect
correction efficiency is a good way to analyze how effective the team is in fixing the
defects in the same iteration. This could be measured severity wise for better
analysis.

Phase containment is not applicable to agile projects as all phases like design,
CUT and test would happen in parallel. Instead defect containment is measured at
iteration level to see how good the reviews and testing were in that iteration.

 Defect Density is a standard metric mandated for all projects irrespective of the
life cycle model.

Measuring PDDR gives an indication on the effectiveness of development process.

This needs to be measured separately at iteration and release levels release level
metric is not to be rolled out from individual iterations. The goal should be have zero
post delivery defects at release level.

Measuring Productivity would help the team to benchmark themselves against

other projects and industry standards.

Velocity is a unique metric for Agile projects most literature mention that this
needs to be measured as the number of story points. At Wipro, we normalize it with
effort to handle change in team size hence measured as the ratio of actual story
points to actual effort.

UT Code Coverage, Test Automation rate and Build Success rate are some of the
other metrics that help projects to measure the effectiveness of engineering
practices.

The Delivered Business Value is another metric exclusive for agile projects. Each
story is assigned a business value based on the priority. While story points indicate
the bigness of the story, the priority indicates the importance of the story to
business. Higher priority stories have higher business value. This metrics is
measured as a ratio of the business value delivered in the iteration to the total
business value in the product backlog. Analysis of this metric will help the business
in determining if the product is ready for a market release. If the ratio is high it
indicates that the high priority stories have been addressed, the ones remaining in
the backlog are low priority ones and further development could be stopped.