The Results of Monitor and Control Scope Are Verified Deliverables

PMBOK v8 Definition

The Monitor and Control Scope process is the ongoing process of monitoring and managing changes to the project scope—and measuring the quality and value of the deliverables to fulfill quality standards. This process controls how requests for changes to the detailed project scope statement will be processed while ensuring the deliverables meet specified quality requirements and that the scope and quality are aligned to the scope baseline. This process belongs to the Scope Management knowledge area and the Monitoring and Controlling process group.

A key goal of the Monitor and Control Scope process is to determine the correctness of deliverables. The results of performing this process are verified deliverables that become an input to the Validate Scope process for formalized acceptance.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions that test your understanding of the sequence of scope processes and the difference between verification and validation. Questions often present scenarios where deliverables are completed and ask you to identify the correct next step—distinguishing between verifying correctness (Monitor and Control Scope) versus obtaining formal acceptance (Validate Scope). Expect this in situational questions about quality control, scope change management, and deliverable handoff.

Key Points to Remember (for the Exam)

Process Purpose: Monitor and Control Scope is the ongoing process of monitoring and managing changes to the project scope while measuring the quality and value of deliverables to fulfill quality standards.
Primary Goal: Determine the correctness of deliverables—ensuring they meet specified quality requirements and are aligned to the scope baseline.
Main Output: Verified deliverables—completed project deliverables that have been checked and confirmed for correctness through the Monitor and Control Scope process.
Next Process Input: Verified deliverables become an input to the Validate Scope process for formalized acceptance.
Change Handling: If there are any change requests or improvements related to deliverables, they should be changed, inspected, and reverified.
Scope Baseline Alignment: This process ensures scope and quality are aligned to the scope baseline.
Common Confusion: Do not confuse verified deliverables (checked for correctness) with accepted deliverables (formally approved by stakeholders). Verification happens in Monitor and Control Scope; acceptance happens in Validate Scope.

Typical PMI Exam Example

A project team completes a software module. The quality control team inspects the module and confirms it meets all functional requirements. The project manager records the results and notes that the module is correct. According to PMBOK v8, what is the status of this deliverable, and what process should occur next?

Answer: The deliverable is a verified deliverable from the Monitor and Control Scope process. It should now become an input to the Validate Scope process for formalized acceptance by the customer.

PMI Exam Traps

Trap: Confusing verified deliverables with accepted deliverables.
- Reality: Verified deliverables come from Monitor and Control Scope (correctness check). Accepted deliverables come from Validate Scope (formal stakeholder acceptance).
Trap: Thinking Monitor and Control Scope only deals with change control.
- Reality: It also measures quality and value of deliverables and determines correctness against the scope baseline.
Trap: Believing that Validate Scope happens before Monitor and Control Scope.
- Reality: Verified deliverables from Monitor and Control Scope are inputs to Validate Scope. Verification precedes formal acceptance.
Trap: Assuming that once a deliverable is verified, no further changes are needed.
- Reality: If change requests or improvements are identified, deliverables must be changed, inspected, and reverified before moving to Validate Scope.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Validate Scope	Output to (Input)	Verified deliverables from Monitor and Control Scope feed into Validate Scope for formal acceptance. Do not skip verification before seeking acceptance.
Scope Baseline	Aligned with	Monitor and Control Scope ensures deliverables are aligned to the scope baseline. Changes to scope baseline require the Monitor and Control Scope process.
Quality Management	Complementary	Monitor and Control Scope measures quality and value of deliverables. It works alongside quality control processes to ensure correctness.
Change Requests	Possible Output	If deliverables need improvements, change requests are processed, inspected, and reverified within Monitor and Control Scope.

Quick Review Questions

What is the primary goal of the Monitor and Control Scope process regarding deliverables?
What is the exact name of the output produced by the Monitor and Control Scope process?
Which process receives the output from Monitor and Control Scope as an input for formalized acceptance?
If a change request is made to a verified deliverable, what must happen before it can be submitted for validation?
What three elements does Monitor and Control Scope ensure are aligned?

PMBOK v8 Reference

Section 2.2.2.5 – Monitor and Control Scope