Page 147 -

5 - PROJECT SCOPE MANAGEMENT

Since all of the requirements identified in Collect Requirements may not be included in the project, the Define
Scope process selects the final project requirements from the requirements documentation delivered during the
Collect Requirements process. It then develops a detailed description of the project and product, service, or result.

The preparation of a detailed project scope statement is critical to project success and builds upon the major
deliverables, assumptions, and constraints that are documented during project initiation. During project planning,
the project scope is defined and described with greater specificity as more information about the project is known.
Existing risks, assumptions, and constraints are analyzed for completeness and added or updated as necessary.
The Define Scope process can be highly iterative. In iterative life cycle projects, a high-level vision will be developed 5
for the overall project, but the detailed scope is determined one iteration at a time and the detailed planning for the
next iteration is carried out as work progresses on the current project scope and deliverables.

5.3.1 define Scope: Inputs

5.3.1.1 Scope Management Plan

Described in Section 5.1.3.1.The scope management plan is a component of the project management plan
that establishes the activities for developing, monitoring, and controlling the project scope.

5.3.1.2 Project charter

Described in Section 4.1.3.1. The project charter provides the high-level project description and product
characteristics. It also contains project approval requirements. If a project charter is not used in the performing
organization, then comparable information needs to be acquired or developed, and used as a basis for the detailed
project scope statement. Organizations that do not produce a formal project charter will usually perform an informal
analysis to identify the content necessary for further scope planning.

5.3.1.3 requirements documentation

Described in Section 5.2.3.1. This documentation will be used to select the requirements that will be included
in the project.

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

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.