In the PMBOK Guide fifth edition, the verify scope process is replaced with the validate scope process, therefore this post is no longer valid.
Please refer to my new blog post on quality control and validate scope.
Today we are going to discuss the quality control and verify scope processes.
These two are very important processes which ensure that the product is defect free and meets the user’s requirement.
Since both processes involve inspection, many professionals often get confused and think that they are the same.
However, this is not true. Both processes are different: they are performed at different stages of the project and their objectives are also different.
I hope after reading this blog post, you will be able to understand the difference between these two processes.
In the quality control process, you inspect the deliverable for its quality. You check its correctness and see if it is as per specifications.
You perform quality control activities throughout the monitoring and controlling phase with your team members to ensure that the product is defect free and all parameters are within the acceptable limits.
Now let’s see a real world example of the quality control process.
You have been appointed as project manager for a government contract to build a 1,000 km road. You start working on it. Along with other plans, you create a quality management plan and recruit a quality control engineer to monitor the quality activities.
This quality control engineer will be available on site to check the quality of the work at each stage. He will see if the received coal-tar is as per the required quality, the stones are properly being crushed, the ground level is correct, and if the sidewalk is properly aligned, etc.
In the above example, the quality control engineer was performing quality control activities.
In the verify scope process you inspect the deliverable with the client to verify if it meets all requirements and is acceptable.
The verify scope process is also performed during the monitoring and controlling phase of the project.
Both processes are performed during the monitoring and control phase of the project, however this is the only similarity. The objective of the verify scope process is to get formal acceptance from the client that the deliverable is acceptable.
Now we will see the verify scope activities in a real world example.
Let’s take the same example discussed above.
You have built the 100 km road and it is ready to be handed over. You invite the authorities to come and inspect the completed part of the road and formally accept it.
The government representatives come and verify whether all the requirements have been met or not. They will check if the road width is correct, if road leveling is okay, and the length of the completed part of the road.
Once these representatives are satisfied, they will formally accept the completed part of the road and you get your money.
The above example shows verify scope activities.
Please note that it is not necessary for the verify scope process to always be performed at the end of the project. It can happen far before the project ends. You can also perform the verify scope activity with the perform quality control process as you have seen in the given example.
In the given example, both processes are being performed in parallel. The government’s representatives are verifying the scope for the completed part of the road with you, and at the same time your team is building the rest of the road.
Differences Between Quality Control and Verify Scope
The following are a few differences between the quality control and verify scope processes:
- Quality control deals with the quality of the product while verify scope deals with the scope of the product.
- Quality control activities are performed internally, while the verify scope process is performed with the client.
- Quality control activities are performed during the project execution, and verify scope functions are usually performed at the end of the project or phase.
- The objective of the quality control process is to produce a defect free product, while the objective of the verify scope process is to get the deliverable accepted by the client.
The quality control process helps you create a defect free high quality product, and the verify scope process helps you get the product accepted by the client. Quality control activities are performed throughout the execution phase, and verify scope activities are needed when the deliverable is ready to be handed over.
There is another process called quality assurance which is often mistaken for quality control. Therefore, I have written another blog post to explain these processes as well.
Here is where this blog post on quality control and verify scope ends. If you have something to share, you can do so through the comments section.