Validate Scope
Figure 38:Validate Scope: Inputs, Tools and Techniques, and Outputs. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), (5th Edition)" by Project Management Institute, 2013, p. 133. Newton Square, PA: Project Management Institute, Inc. Reprinted without permission
Figure 38: Validate Scope above depicts all the possible inputs tools and techniques resulting in Accepted deliverables, Change requests, Work performance information and Project documents updates.
5.5 Validate Scope
Process Definition
Validate Scope process receives the deliverables from Control Quality. A meeting was held to review scope specifications with the customer. If the customer agrees that the scope is correct, the customer signs an approval document. This process ensures that both parties understand the scope. If doing batch production this formality would be repeated with each batch with the customer.
Process Assessment
In most cases a formality but it is imperative to have a paper trail in case the customer denies or tries to reject delivery of the deliverables claiming the product scope was not what he or she agreed to. If the customer rejects the scope requirements, a change request is possibly performed to straighten out the scope requirements, and the deliverables are probably reworked or scrapped. Customer service-driven companies employ this process to ensure that the stakeholder's expectations are met.
Validate Scope
5.5.1
Input
Requirements Documentation 501:
In PGMT 501, Requirements Documentation for Rock-N-Roll Landscape Project is an input to validate the Scope of this project.
5.5.2
Tools and Techniques
In PGMT 612, a technical summary of tools and techniques for Validate Scope.
5.5.3
Outputs
In PGMT 614, a signed Acceptance document an output validates deliverables meet the scope requirements.