Validation and verification are two important terms in project management; they seem very similar, and it’s easy to get them confused.
These are important concepts and any PMP aspirants needs to understand them well. I will explain these terms fully, so you will have a better understanding of them when you finish this blog post.
This topic is not very important from the PMP exam point of view. However, as a project manager, you must know the difference between these terms.
This is about building the right thing if you have developed the correct product, and whether it meets customers’ requirements or not.
Validation is a subjective process. It shows you how well the product fulfilled the customer’s requirements. Modeling, simulation, and user evaluation are a few examples of this process.
For example, let’s say that you are developing a cell phone for your customers. You have conducted market research and collected the features the item should have. Then you started the production.
However, when the cell phone is finally launched, it does not get the expected market response. Eventually, it fails.
Here, you would say that the product could not be validated because it failed to meet the customers’ needs. Validation is about product testing and it is a subjective process.
This is about building the product correctly, whether it meets all stated quality requirements and is as described.
Verification is an objective process. All quality requirements must be well documented for proper measurement and analysis.
For example, let’s say that you are developing a cell phone. You have conducted market research and collected all the information on required features. You develop a plan to build the product. You complete all the requirements and develop the procedure accordingly.
Now, the production process has started. You will perform an inspection during the process to make sure that everything is going according to plan.
If the product meets requirements, this means it has been verified. Verification ensures that the product is of high quality. It is useful in making sure the product error-free.
Difference Between Verification and Validation
Validation ensures that specifications meet customer requirements, while verification ensures that products meet the specifications.
- Verification evaluates the process and the product in development, while validation evaluates the product itself.
- Verification helps the product be built the right way. The objective of validation is to build the right product.
- Inspection and document review are verification tools. Validation activities include testing the product.
- The project management team performs the verification process, while validation is performed by the client or customer.
It is possible for the product to pass verification but fail validation.
You can see this in the example provided; the company developed a cell phone that passed through the verification process. However, when they launched it, the customer response was not good. The product failed and this means the product can’t be validated.
Validation and verification are independent procedures. The project manager uses them to make sure they have built the right product in the correct way. Verification is about conformance to specifications, it is an internal process. Validation is about customer expectation and it is often an external, subjective process. Verification comes before validation.
What tools do you use for the verification process? Have your products passed validation? Please share your experiences in the comments section.