Measurements can be a powerful ally in a project or they can be a complete waste of time & effort. One of the keys to their success, the measurements closely align to acceptance criteria. Getting stakeholders to recognize and agree upon documented acceptance criteria can be like nailing jelly to a tree. However, it because easier if they are strongly motivated to do so. In most cases, that motivation needs to be internal and not placed upon them by an external influence like a PMO guideline.
Measurements within the project generally start early and are part of the requirements process. After that, technical designs are often measured by the approved requirements and the overall effort measured by criteria established in the project plan. Additionally, the group doing the designs may have internal measurements they use to ensure quality is baked into the effort based upon their own guidelines.
Yet another possible measurement effort can come from the quality assurance teams. Most technical products will have some level of performance measurement. However, you can have a strong host of other quality metrics that influence the design of the product. This is one of the strongest arguments for writing test plans and test scripts BEFORE coding begins. This allows the design and development teams build towards satisfying a know standard.
In many cases, the ability for a project to succeed is based upon the ability to set measurement criteria, execute against those measurements and then pivot elements of the project when the measurements consistently miss expectations.
© 2016 Dwayne Wright