Page 131 -

5 - PROJECT SCOPE MANAGEMENT

5 5

Project scoPe MAnAGeMent

Project Scope Management includes the processes required to ensure that the project includes all the work 5
required, and only the work required, to complete the project successfully. Managing the project scope is primarily
concerned with defining and controlling what is and is not included in the project.

Figure 5-1 provides an overview of the Project Scope Management processes, which include the following:

5.1 Plan Scope Management—The process of creating a scope management plan that documents how
the project scope will be defined, validated, and controlled.
5.2 collect requirements—The process of determining, documenting, and managing stakeholder needs
and requirements to meet project objectives.

5.3 define Scope—The process of developing a detailed description of the project and product.
5.4 create WBS—The process of subdividing project deliverables and project work into smaller, more
manageable components.
5.5 Validate Scope—The process of formalizing acceptance of the completed project deliverables.

5.6 control Scope—The process of monitoring the status of the project and product scope and managing
changes to the scope baseline.
These processes interact with each other and with processes in other Knowledge Areas as described in detail
in Section 3 and Annex A1.

In the project context, the term scope can refer to:

• Product scope. The features and functions that characterize a product, service, or result; and/or
• Project scope. The work performed to deliver a product, service, or result with the specified features and
functions. The term project scope is sometimes viewed as including product scope.

The processes used to manage project scope, as well as the supporting tools and techniques, can vary
by project. The scope baseline for the project is the approved version of the project scope statement, work
breakdown structure (WBS), and its associated WBS dictionary. A baseline can be changed only through formal
change control procedures and is used as a basis for comparison while performing Validate Scope and Control
Scope processes as well as other controlling processes.

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

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