Be sure to select measures that cover the life cycle for the types of projects that
you want to quantitatively manage. For example, if you have maintenance projects,
don??™t just measure the development life cycle. You might measure the number
of problem reports, time to review problem reports, time to implement problem
reports, time to test, number of retests, and so forth.
You need to consider both breadth and depth. Breadth means the measures
across the entire life cycle, for example, cost, schedule, defects, and effort; and depth
means the details in areas that are critical to your organization, that is, number of
customer returns by release and number of subcontractor failures by vendor.
Collect the Measures Identified from the Projects
Often the hardest part of measurement is to get good data. Again don??™t be disheartened
if you find problems with the data. Even if your standard process requires that
your projects collect certain metrics, you may find that the data are missing and/or
incorrect. You may need to ???mine the data???; this means dig them up.
Pages:
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564