The following is a list of problems we have encountered in metrics programs found in organizations. This list can be used as a checklist for any metrics or metrics programs you have implemented in your organization.
Metrics are collected but not used.
No mechanism exists to distribute project performance metrics for review, comparison, and use.
Project-level metrics do not appear to be used to help project managers manage their projects.
There is no understanding of the value of metrics or how to use them.
No formal feedback loop is found on the quality of the metrics, questions about them, etc.
Metrics reports are difficult to review for trends.
Metrics data are inconsistent.
Personnel collect and input data that they think are right but are unsure.
A standard WBS (a basic building block for management activities) is not followed consistently, and metrics cannot be traced back to WBS activities.
No one reviews the metrics data in the various databases for data integrity.
Training and communication are not occurring throughout the organization.
Procedures need to be devised to document metrics generation, collection, review, and use.
Existing procedures need to be updated to reflect changes.
Automated tools are not used; the wrong automated tool is used; or the automated tool is used incorrectly.
The metrics reports are difficult to read and understand.
Procedures are not well-defined or consistently followed (e.g., usage of "may if desired at PM's discretion").
The time it takes to identify, track, collect, and report the metrics is not measured.
Redundant data entry is rampant.