Project Scope Monitoring and Controlling

The last two processes for Scope Management, fall under the Monitor and Control process group.

Verify Scope requires the validated deliverables to be checked and verified against the requirements documentation. Why is it “validated” deliverables? It is “validated” because it has gone through the Quality Control process.

The inspection done on the validated deliverables is performed by selected eligible stakeholders. This inspection session is usually called the User Acceptance Test or UAT. It could also be called product reviews, audit or walkthrough.

Quality Control and Verify Scope could be done in parallel. However, it must be known that quality control is about correctness of the deliverable and verify scope is about acceptance of the deliverable.

At the end of this process, we will either have accepted deliverables or rejected deliverables; which means there will be change requests.

Control Scope “is the process of monitoring the status of the project and product scope and managing changes to the scope baseline” [PMBOK Guide 4th Edition].

Equipped with the project management plan, work performance information and requirements documentation, variance analysis will be performed to measure the work performance at specific dates throughout the project life cycle.

Based on the findings, there will be updates to project documents and change requests where applicable. Through the variance analysis, we will know the current health status of the project and subsequently deciding on corrective or preventive actions.