We have briefly discussed why verification is important to the product quality. Verification does not just address the product quality. Our project work requires verification as well. When we take on a project, we should have the scope articulated in a way that we can confirm that the project did indeed fulfill the objective. As part of our project work we will compare the product as it is to this end objective. Part of the termination activities of the project will be the confirmation (or refutation) that we have indeed met our contractual obligations.
Just as verifying the product solely at the end is insufficient, so too is verifying the project’s ability to meet the objective solely at the end of the project a good indicator of failure. The project manager and project team must develop metrics at the start of the project that will form the guiding light for our project actions. We provide a brief list of some possible metrics:
- Product quality (ppm)
- Product cost
- Specific key product features or characteristics
- Cost Performance Index
- Schedule Performance Index
- Schedule Variance
- Cost Variance
We will know when we miss-step by monitoring the ideal against our present performance. We will note any discrepancies that foretell failure and take controlling actions to put the project back on the trajectory to deliver as needed. If we cannot uncover a way to put the project back on track, we will then have to discuss with the project sponsor and key stakeholders the next course of action. We are in a position to have this discussion nearer to the problem rather than wait until the end of the project to be surprised that we spent money, time and talent to not produce the expected results.
Verification is also important for project management and it is also not just at the end of the project as contract closure actions.Tags: product development, project management, Quality, risk, verification