Verified Deliverables: Definition and Role in Scope Management
PMBOK v8 Definition
Verified deliverables are completed project deliverables that have been checked and confirmed for correctness through the Monitor and Control Scope process. A goal of the Monitor and Control Scope process is to determine the correctness of deliverables. The results of performing the Monitor and Control Scope process are verified deliverables that become an input to the Validate Scope process for formalized acceptance. This concept belongs to the Scope Management Knowledge Area and involves the Monitoring and Controlling Process Group.
Why It Matters for the Exam
The PMI exam frequently tests the distinction between "verified deliverables" and "accepted deliverables" because these two terms are often confused by candidates. Questions typically appear in scenario-based items where you must identify the correct sequence of processes or determine which output feeds into which subsequent process. Understanding this distinction is critical for scoring points in Scope Management questions.
Key Points to Remember (for the exam)
- Definition: Verified deliverables are completed deliverables checked and confirmed for correctness through the Monitor and Control Scope process.
- Main Process Origin: Monitor and Control Scope produces verified deliverables as an output.
- Main Output Relationship: Verified deliverables serve as an input to Validate Scope for formalized acceptance.
- Purpose of Verification: The goal is to determine the correctness of deliverables against requirements and quality standards.
- Sequential Flow: Verified deliverables → Validate Scope → Accepted deliverables → Formal stakeholder acceptance.
- Change Handling: If change requests or improvements are needed, deliverables should be changed, inspected, and reverified.
- Common Confusion Point: Verified ≠ Accepted. Verification checks correctness; acceptance formalizes stakeholder approval.
Typical PMI Exam Example
A project team completes a software module and checks it against the requirements documentation. After confirming all features function correctly, the team records the module as a verified deliverable. This deliverable is then presented to the customer during the Validate Scope process for formal acceptance. The project manager must understand that the verification step occurred in Monitor and Control Scope, not Validate Scope.
PMI Exam Traps
-
Trap: Thinking that verified deliverables are the same as accepted deliverables. Reality: Verified deliverables are an input to Validate Scope; acceptance happens after formal stakeholder sign-off.
-
Trap: Confusing Monitor and Control Scope with Validate Scope. Reality: Monitor and Control Scope verifies correctness; Validate Scope formalizes acceptance of deliverables.
-
Trap: Assuming verification occurs only once at project end. Reality: Verification is an ongoing process within Monitor and Control Scope throughout the project lifecycle.
-
Trap: Mixing up "verified deliverables" with "completed deliverables" in general. Reality: A completed deliverable is not automatically verified; it must be checked and confirmed through the Monitor and Control Scope process.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Validate Scope | Input to (verified deliverables feed into Validate Scope) | Verified deliverables are the input; Validate Scope produces accepted deliverables as output |
| Acceptance Criteria | Defines conditions for acceptance | Verified deliverables must meet acceptance criteria before formal acceptance |
| Quality Requirements | Part of verification criteria | Monitor and Control Scope ensures deliverables meet specified quality requirements |
| Scope Baseline | Reference for measurement | Verified deliverables are compared against the scope baseline to assess performance |
| Change Requests | Trigger for reverification | If changes occur, deliverables must be changed, inspected, and reverified |
Quick Review Questions
- Which process produces verified deliverables as an output?
- What is the primary input to the Validate Scope process?
- What is the key difference between "verified deliverables" and "accepted deliverables"?
- If a change request is approved for a verified deliverable, what must happen before it can be presented for acceptance again?
- A project manager has deliverables that have been checked for correctness. Which process has been completed?
PMBOK v8 Reference
Section 2.2.2.5 – Monitor and Control Scope
Section 2.2.2.6 – Validate Scope
(Refer to the PMBOK v8 context provided: Passages 1, 3, and 5 contain the exact definitions and relationships described above)