Minimizing risk in applying metrics on multiple projects

Using the author's own metrics validation methodology, he shows how this methodology can be used across dissimilar multiple projects. He shows how to reduce the risk of using metrics on multiple projects. He also shows that the choice of metrics and their values can have a significant effect on the quality of software that is achieved and on the cost and amount of inspection that is incurred on multiple projects. A multi-project example, emphasizing the discriminative power validity criterion in support of the quality control function, is presented. A metrics validation process is defined that integrates quality factors, metrics and quality functions.<<ETX>>