Control Quality versus Validate Scope

The control quality and validate scope processes help you build the right product and deliver it to the client. These are important processes and you should understand them well. 

However, before we discuss these processes, let’s have a quick look at the meanings of “validate” and “verify.” I have seen many experienced professionals who don’t understand the difference between the two terms.

Verification

Verification is about building the product correctly. 

Here, you inspect the deliverable for completeness and correctness. You ensure that the product is built the right way. It is an internal process to make sure that the stated requirements and specifications are met and that all regulations have been followed. 

The quality control engineer performs this function.

Validation

Validation is about building the right product.

This process ensures that the products meet the customer’s requirements. This process does not involve the project team. Generally, the project manager performs this function with the client or other stakeholders.

 The validation process comes after the verification process

An Example of Verification and Validation

Suppose you plan to launch a new product. You develop it, and you check whether it was developed as per the design or not. Are the specifications as per the requirements? If the answer is yes, you have verified the product. 

You launch the product in the market and receive good customer response. Sales are better than expected, and you earned a good profit. 

The product is validated because it fulfills the customers’ requirements and they are satisfied. 

Now, we come to the topic of this blog post. Many professionals consider the control quality and validate scope processes to be similar because both processes involve the inspection and review of deliverables. This is an incorrect assumption.

Control Quality

According to the PMBOK Guide, 6th edition, “Control Quality is the process of monitoring and recording results of executing the quality management activities in order to assess performance and ensure the project outputs are complete, correct, and meet customer expectations.” 

You perform the control quality process internally during the execution phase to ensure that deliverables are defect-free and fulfill the stated requirements. You will recommend corrective action if you find any deviation. 

Put simply, you inspect the deliverable for its correctness and ensure that it meets the quality requirements.

Example of the Control Quality Process

You get a project to build a 200 km road. You start the work and appoint a quality control engineer. He will check the deliverables at each stage: e.g., f raw materials, level of the road, the slope on the turn, alignment of the footpaths, etc. If he finds any variations in the process or product he will take necessary corrective actions. 

The above example shows quality control activities.

Validate Scope

According to the PMBOK Guide, 6th edition, “Validate Scope is the process of formalizing acceptance of the completed project deliverables.” 

The project manager performs the validate scope process with the client after the product is ready. The objective is to ensure formal product acceptance by the client. 

You verify the product in the control quality process and then validate it with the client for their acceptance in the validate scope process.

Example of the Validate Scope Process

Let’s continue with the example given for the control quality process. 

You have completed 50 km out of 200 km of the road. You invite the client to inspect and accept it so you can receive payment. 

They come and check whether the width of the road is correct, if the footpath is properly aligned, and if the length is right. After inspecting these parameters, they check the strength of the road. 

Once they are satisfied, they sign the acceptance letter and you get paid for the completed work. 

This is an example of the validate scope process. 

The validate scope process is not always performed at the end of the project. You can perform it during the project execution along with the control quality process, as you saw in the example above. 

In the example, the client has accepted 50 km of the road, while you remain busy with completing the rest.

Similarities Between Control Quality and Validate Scope

The following are a few similarities between the control quality and validate scope processes:

• Both processes belong to the monitor and control process group.
• Both processes involve the inspection and review of deliverables.

Differences Between Control Quality and Validate Scope

The following are a few differences between the control quality and validate scope processes:

• Control quality is an internal process, while validate scope is an external process.
• Control quality checks if the product was developed in the right way, and validate scope is concerned with building the right product.
• The control quality process ensures that the product is ready for delivery while the validate scope process gets the formal acceptance from the client.
• Control quality is performed during the project execution, and validate scope is usually performed at the end of the phase or project.

Summary

The control quality and validate scope processes are a part of the monitoring and controlling process group and both involve the inspection of deliverables, but their purpose is different. These processes help you build the correct product in the first place and get formal acceptance from the client. Both processes complement each other and help you deliver a high-quality product. 

What activities do you carry out in the control quality and validate scope processes? Please share your experiences in the comments section.