Scope Management Plan Template With Instructions

<Project Name>
Scope Management
Plan
Prepared by:
Date:
Table of Contents
INTRODUCTION.................................................................................................................................3
SCOPE MANAGEMENT APPROACH....................................................................................................3
ROLES AND RESPONSIBILITIES.........................................................................................................4
SCOPE DEFINITION...........................................................................................................................4
PROJECT SCOPE STATEMENT............................................................................................................4
WORK BREAKDOWN STRUCTURE....................................................................................................5
SCOPE VERIFICATION.......................................................................................................................5
SCOPE CONTROL..............................................................................................................................6
SPONSOR ACCEPTANCE....................................................................................................................6
2
INTRODUCTION
Scope Management is the collection of processes which ensure that the project includes all the
work required to complete it while excluding all work which is not necessary to complete it. The
Scope Management Plan details how the project scope will be defined, developed, and verified.
It clearly defines who is responsible for managing the projects’ scope and acts as a guide for
managing and controlling the scope.
Project Scope Management follows a five step process; Collect Requirements, Define Scope,
Create WBS, Verify Scope, and Control Scope.
1) Collect Requirements – this first step is the process by which we define and document the
requirements needed to meet all project objectives. The foundation of this process is the
project charter and stakeholder register. From these, the team can identify requirements,
collectively discuss details associated with meeting each requirement, conduct interviews
and follow-on discussion to clarify the requirements, and document the requirements in
sufficient detail to measure them once the project begins the execution phase. This
documentation also serves as an input to the next step in the process which is to define
scope.
2) Define Scope – this step is critical to project success as it requires the development of a
detailed project/product description to include deliverables, assumptions, and constraints
and establishes the framework within which project work must be performed.
3) Create WBS – this process breaks project deliverables down into progressively smaller
and more manageable components which, at the lowest level, are called work packages.
This hierarchical structure allows for more simplicity in scheduling, costing, monitoring,
and controlling the project.
4) Verify Scope – this is the process by which the project team receives a formalized
acceptance of all deliverables with the sponsor and/or customer.
5) Control Scope – this is the process of monitoring/controlling the project/product scope as
well as managing any changes in the scope baseline. Changes may be necessary to the
project scope but it is imperative they are controlled and integrated in order to prevent
scope creep.
SCOPE MANAGEMENT APPROACH

It is important that the approach to managing the projects’ scope be clearly defined and
documented in detail. This section provides a summary of the Scope Management Plan in which
it addresses the following:
 Who has authority and responsibility for scope management
 How the scope is defined (i.e. Scope Statement, WBS, WBS Dictionary, Statement of
Work, etc.)
 How the scope is measured and verified (i.e. Quality Checklists, Scope Baseline, Work
Performance Measurements, etc.)
 The scope change process (who initiates, who authorizes, etc.)
 Who is responsible for accepting the final project deliverable and approves acceptance of
project scope
3
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
SCOPE DEFINITION
The scope definition section details the process of developing a detailed description of the
project and its deliverables. This can only be completed after the requirements have been
identified and defined during the requirements definition process. During the requirements
definition process three documents were created; Requirements Documentation, Requirements
Management Plan and a Requirements Traceability Matrix. You can refer to these documents
when defining the projects’ scope.
This section should explain the process you followed to develop the detailed description of the
project and its deliverables. If you used other documents such as the Project Charter,
Preliminary Project Scope Statement or Requirements Documentation you should identify them
and all other documents used. You should tie the scope definition process back to the
requirements definition as the projects’ scope answers the requirements for the project.
You should also document the tools and techniques used to define the project scope such as
expert judgment, product analysis, alternatives identification or facilitated workshops.
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:
 Product Scope Description – describes what the project will accomplish
 Product Acceptance Criteria – describes what requirements must be met in order for the
project to be accepted as complete
 Project Deliverables – detailed list of deliverables the project will result in
 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)
4
 Project Assumptions – describes the list of assumptions the project team and stakeholders
are working under to complete the project
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.
Figure 1.1, Work Breakdown Structure (WBS)
In order to more clearly define the work necessary for project completion the WBS Dictionary is
used. The WBS Dictionary includes an entry for each WBS element. The WBS Dictionary
includes a detailed description of work for each element and the deliverables, budget and
resource needs for that element.
Level WBS Element Description of Work Deliverables Budget Resources

Code Name
Table 1.2, WBS Dictionary
SCOPE VERIFICATION
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
5
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.
SCOPE CONTROL
Scope control is the process of monitoring the status of the scope of the project. This section
also details the change process for making changes to the scope baseline.
SPONSOR ACCEPTANCE
Approved by the Project Sponsor:
___________________________________________ Date:____________________
<Project Sponsor>
<Project Sponsor Title>
Revision History
Version Date Reason Executive Sponsor Sign Off

Scope Management Plan Template With Instructions

Uploaded by

Copyright:

Available Formats

Scope Management Plan Template With Instructions

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scope Management Plan Template With Instructions

Uploaded by

Copyright:

Available Formats

<Project Name>

SCOPE MANAGEMENT APPROACH

Name Role Responsibilities

PROJECT SCOPE STATEMENT

WORK BREAKDOWN STRUCTURE

Figure 1.1, Work Breakdown Structure (WBS)

Level WBS Element Description of Work Deliverables Budget Resources

Table 1.2, WBS Dictionary

Approved by the Project Sponsor:

You might also like