SCOPE MANAGEMENT PLAN
<PROJECT NAME>
<PROJECT MANAGER(S)>
<DATE>
PROJECT SCOPE STATEMENT
The project scope statement details the project’s deliverables and the work necessary to create
these deliverables. The Project Scope Statement should contain the following components:
Project Scope Description – describes what the project will accomplish
Project Deliverables – a list and description of the main project deliverables
Project Acceptance Criteria – describes what requirements must be met in order for the
project deliverables to be accepted as complete
Project Exclusions – description of work that is not included in the project and outside of
the scope
Project Constraints – lists limits on resources for time, money, manpower, or equipment
(capital)
Project Assumptions – describes the list of assumptions the project team and stakeholders
are working under to complete the project
2
ROLES AND RESPONSIBILITIES
In order to successfully manage a projects’ scope it’s important that all roles and
responsibilities for scope management are clearly defined. This section defines the role of the
Project Manager, Project Team, Stakeholders and other key persons who are involved in
managing the scope of the project. It should state who is responsible for scope management and
who is responsible for accepting the deliverables of the project as defined by the projects’ scope.
Any other roles in scope management should also be stated in this section.
Name Role Responsibilities
Table 1.1, Scope Management Roles and Responsibilities
MAJOR MILESTONES
A list of major project milestones including the start and finish dates.
3
WORK BREAKDOWN STRUCTURE
The Work Breakdown Structure (WBS) and Work Breakdown Structure Dictionary are key
elements to effective scope management. This section should discuss how the project scope is to
be subdivided into smaller deliverables in the WBS and WBS Dictionary and how these smaller
components are managed during the life of the project.
WBS DICTIONARY
The WBS Dictionary contains all the details of the Work Breakdown Structure which are
necessary to successfully complete the project. Most importantly it contains a definition of each
Work Package which can be thought of as a mini scope statement. Resources on the project will
look at the WBS dictionary to determine the scope of the Work Package they've been assigned, so
it's important to be clear when writing the definition. Most WBS dictionaries contain more
information than we show in our sample. These things usually include Level of Effort, Cost
Control Numbers, Resource Assignments, Responsibility Assignments - just to name a few.
Level WBS Code WBS Item Definition
4
SCOPE VALIDATION
Scope verification discusses how the deliverables will be verified against the original scope and
how the deliverables from the project will be formally accepted. The deliverables for the project
should be formally accepted and signed off on by the customer throughout the lifecycle of the
project and not held back as a single deliverable at the end of the project.
Below is an example of explaining how a deliverable will be verified against the original
requirements. You can use some of the same ideas but your approach will probably by different
and specific to your project and should be expressed in your own words.
5
As this project progresses the Project Manager will verify interim project deliverables against the
original scope as defined in the scope statement, WBS and WBS Dictionary. Once the Project
Manager verifies that the scope meets the requirements defined in the project plan, the Project
Manager and Sponsor will meet for formal acceptance of the deliverable. During this meeting
the Project Manager will present the deliverable to the Project Sponsor for formal acceptance.
The Project Sponsor will accept the deliverable by signing a project deliverable acceptance
document. This will ensure that project work remains within the scope of the project on a
consistent basis throughout the life of the project.
