Page 2 of 2

SCOPE MANAGEMENT PLAN

Project Title: Date:
Methodology and approach
The Scope Management Plan provides the scope framework for this project. 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.
It is important that the approach to managing the projects scope be clearly defined and documented
in detail. This section of the Scope Management Plan 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.

Roles and Responsibilities
In order to successfully manage a projects scope its important that all roles and responsibilities for
scope management are clearly defined in the Scope Management Plan.

Collect requirements
is the process of determining, documenting, and managing stakeholder needs and
requirements to meet project objectives
Scope and Requirements Integration
Describes how requirements should relate to achieving the objective and deliverables that defied in
the scope through selected tools that will analyze, document, and manage. Requirement to-
requirement relationship. A requirement t traceability matrix using many of the tools and techniques
to collect the requirement and integrated with the scope and its deliverables that should be also
appointed here. This is very important process for a successful scope.
Page 2 of 2


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 of the Scope Management Plan 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.
Scope Statement Development
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 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)
Project Assumptions describes the list of assumptions the project team and stakeholders are working
under to complete the project
WBS Structure
The Work Breakdown Structure (WBS) and Work Breakdown Structure Dictionary are key elements to
effective scope management. This section of the Scope Management Plan 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. Also we should mention what kind of WBS will be
used and how further will be the decomposing.


Page 2 of 2


WBS Dictionary
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. The project
team will use the WBS Dictionary as a statement of work for each WBS element.

Scope Baseline Maintenance
The approved detailed project scope statement and its associated WBS and WBS dictionary are the scope
baseline for the project. The scope baseline is a component of the project management plan. And here it
should be defined how it will be measured and controlled and which tools will be used and when and who
and to what be integrated with upon compare it to the actual progress in the project .
Scope control
Scope control is the process of monitoring the status of the scope of the project. By defining which of the
tools to be used and when and by whom!. it should include how the work performance data will be
collected tasks have been accomplished and the actual spending and analyzing them through the selected
techniques and having work performance information as cost variance and schedule and another
elements that specified and other like Quality Checklists, Scope Baseline, Work Performance
Measurements,

Scope Change
This section of the Scope Management Plan also details the change process for making changes to the scope
baseline.( who initiates, who authorizes, etc.) only through formal control procedure .
Page 2 of 2

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


Deliverable Acceptance
Deliverable Acceptance is the process of reviewing deliverables within a project and gaining the businesss
acceptance that they are 100% complete what are the acceptance criteria , to obtain approval from
authorized business decision makers, the Steering Committee, and other key stakeholders for work done
during phase or stage that already defined . The approval at each stage will mean that the deliverables for
that stage are completed to the satisfaction of all stakeholders. In order for a deliverable to be considered
complete and acceptable, it will be measured against pre-determined acceptance criteria, and reviewed by
the Deliverable Acceptance Review Team, a representative team of customers which will provide a
structured method to support the Deliverable Acceptance Review Team (DART) to ensure that appropriate,
correct, consistent, and complete deliverables are created for the project

Page 2 of 2