Page 160 -
P. 160

5 - PROJECT SCOPE MANAGEMENT






                         The verified deliverables obtained from the Control Quality process are reviewed with the customer or sponsor
                      to ensure that they are completed satisfactorily and have received formal acceptance of the deliverables by the
                      customer or sponsor. In this process, the outputs obtained as a result of the Planning processes in the Project Scope
                      Management Knowledge Area, such as the requirements documentation or the scope baseline, as well as the work
                      performance data obtained from the Execution processes in other Knowledge Areas, are the basis for performing
                      the validation and for final acceptance.

                         The Validate Scope process differs from the Control Quality process in that the former is primarily concerned
                      with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables
                      and meeting the quality requirements specified for the deliverables. Control Quality is generally performed before
                      Validate Scope, although the two processes may be performed in parallel.



                      5.5.1 Validate Scope: Inputs


                      5.5.1.1 Project Management Plan


                         Described in Section 4.2.3.1. The project management plan contains the scope management plan and the
                      scope baseline. As described in Section 5.1.3.1, the scope management plan specifies how formal acceptance of
                      the completed project deliverables will be obtained. The scope baseline (Section 5.4.3.1) includes the approved
                      version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be
                      changed only through formal change control procedures and is used as a basis for comparison.


                      5.5.1.2 requirements documentation

                         Described in Section 5.2.3.1. The requirements documentation lists all the project, product, and other types of
                      requirements for the project and product, along with their acceptance criteria.


                      5.5.1.3 requirements traceability Matrix


                         Described in Section 5.2.3.2. The requirements traceability matrix links requirements to their origin and tracks
                      them throughout the project life cycle.





















             134      ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK  Guide) – Fifth Edition
                                                                                          ®


                                           Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
                                       This copy is a PMI Member benefit, not for distribution, sale, or reproduction.
   155   156   157   158   159   160   161   162   163   164   165