SCOPE MANAGEMENT PLAN

[Agency Name]
[Project Name]
[Publish Date]

Scope Management Plan

[Project Name]
TABLE OF CONTENTS
USING THIS TEMPLATE.....................................................................................................................1
REVISIONS........................................................................................................................................2
INTRODUCTION.................................................................................................................................3
SCOPE MANAGEMENT APPROACH....................................................................................................4
ROLES AND RESPONSIBILITIES.........................................................................................................4
SCOPE DEFINITION...........................................................................................................................5
PROJECT SCOPE STATEMENT............................................................................................................6
WORK BREAKDOWN STRUCTURE....................................................................................................7
SCOPE VERIFICATION.......................................................................................................................7
SCOPE CONTROL..............................................................................................................................8
SCOPE CHANGE................................................................................................................................8
ACCEPTANCE....................................................................................................................................9

Scope Management Plan

[Project Name]

USING THIS TEMPLATE

This template contains suggested language and assumes that the author of this document will
make appropriate additions, deletions, and changes for their specific project needs.
To create a document from this template:
Replace [bracketed text] on the cover page, in the header, and throughout the document
with your project and agency information by filling in the [bracketed text] area in the
document text. Filling in the information once, will propagate that field throughout the
document.
Complete the entire template making all necessary adjustments
Each section contains abbreviated instructions (Green Font) and an example using
(Black Font).
Delete this Using This Template page.
Update the Table of Contents by clicking on the References tab, selecting Update
Table, then Update Entire Table and click Ok.
Save.
To provide any suggested improvements or corrections, please email [email protected]

Scope Management Plan

[Project Name]

REVISIONS
R EVISION
v1

D ESCRIPTION

OF

C HANGE

Initial document upload to TBSM

intranet site

A UTHOR
BSD Team

E FFECTIVE D ATE
09/28/12

Scope Management Plan

[Project Name]

INTRODUCTION
Scope Management is the collection of processes used to ensure that the project includes all the
tasks required to complete the project while excluding all work which is out of scope. The Scope
Management Plan details how the project scope will be defined, developed, and verified. The
plan 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 key
business drivers and high level solution vision requirements, collectively discuss details
associated with meeting each requirement, conduct interviews and follow-on discussions
to clarify the requirements, and document the requirements in sufficient detail to confirm
consistent expectations 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 Work Breakdown Structure 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 baselined 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.
The Scope Management Plan provides the scope framework for [Project Name]. This plan
documents the scope management approach, roles and responsibilities as they pertain to project
scope, scope definition, verification and control measures, scope change control, and the
projects work breakdown structure. Any project communication which pertains to the projects
scope should adhere to the Scope Management Plan.
The objective of [Project Name] is the implementation of a new software product which will be
used to track the companys finances and improve various financial processes. This includes
design of the software, all programming and coding, and testing/validation of the software. No
external resources or outsourcing are anticipated for this project.
3

Scope Management Plan

[Project Name]

SCOPE MANAGEMENT APPROACH

It is important to clearly define and document in detail the approach to managing the projects
scope. This section provides a summary of the Scope Management Plan and addresses the
following:
Authorities and responsibilities for scope management
Scope definition process (i.e. Scope Statement, WBS, WBS Dictionary, Statement of
Work, etc.)
Scope measurement and verification (i.e. Quality Checklists, Scope Baseline, Work
Performance Measurements, etc.)
Scope change process (who initiates, who authorizes, etc.)
Acceptance and approval of project deliverables related to project scope
For [Project Name], scope management will be the responsibility of the Project Director. The
scope for this project is defined by the Scope Statement, Work Breakdown Structure (WBS) and
WBS Dictionary. The Project Director, Sponsor and Stakeholders will establish and approve
documentation for measuring project scope which includes deliverable quality checklists and
work performance measurements. Proposed scope changes may be initiated by the Project
Director, Stakeholders or any member of the project team. All change requests will be submitted
to provide estimate and impact to schedule and costs if any to the Project Director who will then
evaluate the requested scope change. Upon acceptance of the scope change request the Project
Director will submit the scope change request to the Change Control Board and Project Sponsor
for acceptance. Upon approval of scope changes by the Change Control Board and Project
Sponsor the Project Director will update all project documents and communicate the scope
change to all stakeholders. Based on feedback and input from the Project Director and
Stakeholders, the Project Sponsor is responsible for the acceptance of the final project
deliverables and project scope.

ROLES AND RESPONSIBILITIES

In order to successfully manage a projects scope, it is important to clearly define all roles and
responsibilities for scope management. This section should define the role of the Project
Director, 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.
For additional information regarding this topic, refer to the Project Roles document located on
the Tennessee Business Solutions Methodology (TBSM) intranet site.
The Project Director, Sponsor and project team will all play key roles in managing the scope of
this project. As such, the Project Sponsor, Project Manager, and team members must be aware of
their responsibilities in order to ensure that work performed on the project is within the

Scope Management Plan

[Project Name]
established scope throughout the entire duration of the project. The table below defines the roles
and responsibilities for the scope management of [Project Name] .
Role
Description
Project Sponsor
Provides executive team approval and sponsorship for the project.
Has budget ownership for the project and is the major stakeholder and
recipient for the project deliverables.
Project Director
Provides overall management to the project. Accountable for establishing
a Project Charter, developing and managing the work plan, securing
appropriate resources and delegating the work and insuring successful
completion of the project. All project team members report to the project
manager. Handles all project administrative duties, interfaces to project
sponsors and owners and has overall accountability for the project.
Steering
Provide assistance in resolving issues that arise beyond the project
Committee
managers jurisdiction. Monitor project progress and provide necessary
tools and support when milestones are in jeopardy.
Stakeholder
Key provider of requirements and recipient of project deliverable and
associated benefits. Deliverable will directly enhance the stakeholders
business processes and environment. Majority of stakeholders for this
project will be agency leads, CIOs, and project management
representatives.
Team Member
Working project team member, who analyzes, designs and ultimately
improves or replaces the business processes. This includes collaborating
with teams to develop high level process designs and models,
understanding best practices for business processes and partnering with
team members to identify appropriate opportunities, challenging the old
rules of the business and stimulating creating thinking, and identifying
organizational impact areas.

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, the Requirements Management Plan and the
Requirements Traceability Matrix were created. These documents can be found on the
Tennessee Business Solutions Methodology (TBSM) intranet site. When defining the project
scope, these documents should be used as reference.
This section should explain the process followed to develop the detailed description of the
project and its deliverables. If other documents such as the Project Charter, Preliminary Project
Scope Statement or Requirements Documentation were used, they should be identified in this

Scope Management Plan

[Project Name]
section. The scope definition process should be tied back to the requirements definition as the
projects scope answers the requirements for the project.
This section should also be used document the tools and techniques used to define the project
scope such as expert judgment, product analysis, alternatives identification, or facilitated
workshops.
The scope for [Project Name] was defined through a comprehensive requirements collection
process. First, a thorough analysis was performed on the agencys current software applications
based on employee and user feedback. From this information, the project team developed the
project requirements documentation, the requirements management plan, and the requirements
traceability matrix for what the new software application must accomplish.
The project description and deliverables were developed based on the requirements collection
process and input from subject matter experts in software design, technical support,
programming and business applications. This process of expert judgment provided feedback on
the most effective ways to meet the original requirements of providing a new software platform
from which the company can improve its financial tracking and internal financial processes.

PROJECT SCOPE STATEMENT

The project scope statement details the projects deliverables and the work necessary to create
these deliverables. The Project Scope Statement should contain the following components:

Product Scope Description (In Scope) Describes what the project will accomplish
Product Completion/Acceptance Criteria Describes what requirements must be met in
order for the project to be accepted as complete
Risk Assessment- Describe the top two or three projects risk and a high-level mitigation
plan. This brief assessment will be expanded in the formal Risk Management Plan.
Project Deliverables Detailed list of deliverables the project will result in
Project Exclusions (Out of Scope) 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)
Dependency Linkages- In some cases, one project may be dependent upon another
projects deliverables; this linkage needs to be identified and its progress monitored. In
other cases, a project may be dependent upon information from several agencies; the
tasks and activities of the information gathering process need to be monitored.
Measures of Project Success- This section describes the metrics that will be used on the
project to determine how success will be measured. Such metrics might include how to
measure customer satisfaction or might state what user friendly system is.
Project Assumptions Describes the list of assumptions the project team and
stakeholders are working under to complete the project
6

Scope Management Plan

[Project Name]
The [Project Name] scope statement provides a detailed description of the project, deliverables,
constraints, exclusions, assumptions, and acceptance criteria. Additionally, the scope statement
includes what work should not be performed in order to eliminate any implied but unnecessary
work which falls outside the of the projects scope.
[Project Name] includes the design, programming, and testing of a new software application for
tracking the companys finances. The deliverables for this project are a completed software
application for finance tracking with the flexibility to modify and expand the application as
necessary in the future. This project will be accepted once the new software has been
successfully tested in each department and has been shown to be compatible with the companys
current information technology (IT) infrastructure. This project does not include ongoing
operations and maintenance of the software. Only internal personnel and resources may be used
for this project. Additionally, the project is not to exceed 180 days in duration or $450,000 in
cost. Assumptions for this project are that support will be provided by the project sponsor and all
department managers and that adequate internal resources are available for the successful
completion of this 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.
For additional information regarding this topic, refer to the Work Breakdown Structure document
located on the Tennessee Business Solutions Methodology (TBSM) intranet site.
For more effective management, the work required to complete [Project Name] will be
subdivided into individual work packages not to exceed 40 hours of work. This will allow the
Project Director to more effectively manage the projects scope as the project team works on the
tasks necessary for project completion. The project is broken down into three phases: the design
phase, the programming phase, and the testing phase. Each of these phases is then subdivided
further down to work packages that are estimated to require no more than 40 hours of work and
no less than 4 hours of work.

SCOPE VERIFICATION
Scope verification should describe how the deliverables will be verified against the original
scope and how they will be formally accepted. For best results, the project deliverables should
be reviewed and approved by the customer throughout the lifecycle of the project and not held
back as a single deliverable at the end of the project.
As [Project Name] progresses, the Project Director will verify interim project deliverables
against the original scope as defined in the scope statement, WBS and WBS Dictionary. Once
7

Scope Management Plan

[Project Name]
the Project Director verifies that the scope meets the requirements defined in the project plan, the
Project Director and Sponsor will meet for formal acceptance of the deliverable. During this
meeting the Project Director 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.
Milestone

In Scope

Out
Scope

Date

Deliverable

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.
For additional information, refer to the Change Control Process document located on the
Tennessee Business Solutions Methodology (TBSM) intranet site.
The Project Director and the project team will work together to control of the scope of [Project
Name]. The project team will leverage the WBS Dictionary by using it as a statement of work for
each WBS element. The project team will ensure that they perform only the work described in
the WBS dictionary and generate the defined deliverables for each WBS element. The Project
Director will oversee the project team and the progression of the project to ensure that this scope
control process is followed and progress is reported through Project Scope measurements tools.

SCOPE CHANGE
If a change to [Project Name] scope is needed, the process for recommending and estimating
changes to the scope of the project must be carried out. Any project team member or Sponsor
can request changes to the project scope. All change requests must be submitted to the Project
Director in the form of a project change request document. The Project Director will then review
the suggested change to the scope of the project. The Project Director will then either reject the
change request if it does not apply to the intent of the project, or convene a Change Control
meeting between the project team and Sponsor to review the change request further and perform
an impact assessment of the change. If the change request receives initial approval by the
Project Director and Sponsor, the Project Director will then formally submit the change request
to the Change Control Board. If the Change Control Board approves the scope change the
Project Sponsor will then formally accept the change by signing the project change control
document. Upon acceptance of the scope change by the Change Control Board and Project
Sponsor the Project Director will update all project documents and communicate the scope
change to all project team members stakeholders.
8

Scope Management Plan

[Project Name]

Scope Management Plan

[Project Name]

ACCEPTANCE
(This section should be modified for best application to specific projects. Include all project team
members that should have some level of authority regarding document review and approval.)
Approved by:
___________________________________________
<Approvers Name>
[Project Name] Executive Sponsor

Date:____________________

___________________________________________
<Approvers Name>
[Project Name] Business Sponsor

Date:____________________

___________________________________________
<Approvers Name>
[Project Name] Project Director/Manager

Date:____________________

___________________________________________
<Approvers Name>
[Project Name] Stakeholder

Date:____________________

10