Page 150 -

5 - PROJECT SCOPE MANAGEMENT

• Project exclusion. Generally identifies what is excluded from the project. Explicitly stating what is out of
scope for the project helps to manage stakeholders’ expectations.
• constraints. A limiting factor that affects the execution of a project or process. Constraints identified with
the project scope statement list and describe the specific internal or external restrictions or limitations
associated with the project scope that affect the execution of the project, for example, a predefined
budget or any imposed dates or schedule milestones that are issued by the customer or performing
organization. When a project is performed under an agreement, contractual provisions will generally be
constraints. Information on constraints may be listed in the project scope statement or in a separate log.
• Assumptions. A factor in the planning process that is considered to be true, real, or certain, without
proof or demonstration. Also describes the potential impact of those factors if they prove to be false.
Project teams frequently identify, document, and validate assumptions as part of their planning process.
Information on assumptions may be listed in the project scope statement or in a separate log.
Although the project charter and the project scope statement are sometimes perceived as containing a certain
degree of redundancy, they are different in the level of detail contained in each. The project charter contains high-
level information, while the project scope statement contains a detailed description of the scope elements. These
elements are progressively elaborated throughout the project. Table 5-1 describes some of the key elements for
each document.

table 5-1. Elements of the Project charter and Project Scope Statement

Project Charter Project Scope Statement

Project purpose or justification Project scope description
(progressively elaborated)
Measurable project objectives
and related success criteria Acceptance criteria

High-level requirements Project deliverables
High-level project description Project exclusions
High-level risks Project constraints
Summary milestone schedule Project assumptions
Summary budget
Stakeholder list
Project approval requirements
(what constitutes success, who
decides it, who signs off)

Assigned project manager,
responsibility, and authority
level
Name and authority of the
sponsor or other person(s)
authorizing the project charter

124 ©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.