7/28/2019 Scope Management Template

1/7

How to u se the Template

Blue textis always intendedas instructions, guidelines, explanations, hints, and tips. It has to be removed when the document isfinalized. To provide a consistent representation of this document to the customer, chapters should not be deleted or inserted.Required addit ionsshould be made as sub-chapters to existing chapters.Chapters that are not relevantshould be marked as such (that is, add not relevant or not applicable).

Be sure to delete these instruct ions w hen you have fin ished!

SCOPE MANAGEMENT

SUBSIDIARY PLAN PROJECT MANAGEMENT PLAN DEFINITION

PROJECT IDENTIFICATION

Delete Project Identification table if not applicable for the document!

Project Name CPI Project Number

Customer Name Customer Number

SAP Project Manager Customer Project Manager

Author Document Location (repository/path/name)

Version Status Date (YYYY-MM-DD) Document Classification

0.1 Final Confidential

7/28/2019 Scope Management Template

2/7

REVISION HISTORY

Delete Revision History section below if not applicable for the document!

Version Date Description

0.1 February 4, 2010

0.2

REVIEW AND APPROVAL

Delete Review and Approval section below if not applicable for the document!

Name

Customer Project Manager

Date (YYYY-MM-DD)

Name

SAP Project Manager

Date (YYYY-MM-DD)

Name

Key Stakeholder

Date (YYYY-MM-DD)

Name

Key Stakeholder

Date (YYYY-MM-DD)

7/28/2019 Scope Management Template

3/7

TABLE OF CONTENT

1. SCOPE MANAGEMENT PLAN .......................................................................................................... 41.1

Introduction .................................................................................................................................. 4

1.2 Purpose ........................................................................................................................................ 41.3 Procedure .................................................................................................................................... 4

7/28/2019 Scope Management Template

4/7

1.Scope Management Plan

1.1 Introduction

Scope Management, as stated in the PMBOK, is focused at ensuring that the project contains all the workrequired and only the work required to complete the project. Therefore, Scope Management contains theprocesses focused at gathering and documenting project requirements, breaking those requirements downto work activities, verification and controlling processes to meet stakeholder expectations.

1.2 Purpose

The Scope Management Plan defines the processes required to ensure that the project includes all of thework required, and only the work required, to complete the project successfully. Project scope managementis primarily concerned with defining and controlling what is and is not included in the deliverables of theproject.

1.3 Procedure

Scope Management is a continuous process composed of 5 steps including regular reporting:

ScopeDefinition

CreateWBS

ScopeVerification

Scope

Planning

ScopeControl

Formalizeacceptanceof project

deliverables

Control

changes toproject

scope

Decomposemajor

deliverablesinto

manageablework

packages

Develop

detailedscope

statement

Create

scopemanagementapproach for

7/28/2019 Scope Management Template

5/7

Scope Management Planning

Defining and managing the project scope influences the projects overall success. The project managementteam will document the scope management decisions in the subsequent steps of this plan. It will describehow the team will define the project scope, develop the detailed scope statement, define and develop the

work breakdown structure, verify the project scope, and control the project scope.

This plan will be developed by SAP Project Manager, Customer

Project Manager, and .

The Scope Management Plan will be completed before the start of Blueprint workshops.

Scope Definition

The preparation of a detailed project scope statement is critical to project success and builds upon the majordeliverables, assumptions, and constraints that are documented in the Statement of Work (SOW). Duringthis step/process, the scope is defined and described with greater specificity because more information

about the project is known. Stakeholders needs, wants, and expectations are analyzed and converted intorequirements.

Note: The Blueprint serves as the process for further elaboration of project requirements. Therefore, theScope Statement cannot be completed until the end of Blueprint.

The Preliminary Scope Statement will be developed in the Project Preparation Phase by SAP Project Manager, Customer Project Manager, and .

Blueprint activities will be will be performed by project teams, further elaborating project

requirements, to include approved change requests that were identified in the Blueprint phase.

The Project Scope Statement will be finalized at the end of Blueprint by SAP ProjectManager, Customer Project Manager, and .

The Project Scope Statement must be approved by the following stakeholders:

- Customer Project Manager

- Customer Project Sponsor

- Steering Committee

- SAP Project Manager

-

Note: Creation of the Project Scope Statement is a significant milestone in the project. The RealizationPhase should not begin until approval is granted and final scope is communicated to all team members andkey project stakeholders.

7/28/2019 Scope Management Template

6/7

Create WBS

The WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the projectteam, to accomplish the project objectives and create the required deliverables. The WBS organizes anddefines the total scope of the project. The WBS subdivides the project work into smaller, more manageable

pieces of work, with each descending level representing an increasingly detailed definition of the projectwork. The planned work contained within the lowest-level of the WBS components, which are called workpackages, can be scheduled, cost estimated, monitored, and controlled.

The Preliminary WBS and WBS Dictionary will be created by SAP Project Manager,

Customer Project Manager, and during the Project

Preparation phase and before the start of Blueprint workshops.

The Project team will utilize the WBS Template for SAP implementation projects. This structure will

serve as the foundation for the Project WBS. Evaluation and further decomposition of deliverables, as

well as elaboration of business scenarios and processes is required to complete a preliminary WBS

and represent key input to the Blueprinting phase. The final Project WBS and WBS Dictionary will be created at the end of Blueprint and incorporate

progressively elaborated requirements defined in the final scope statement.

Scope Verification

Scope verification process will be assessed at the end of each project milestone to obtain stakeholder formalacceptance of the completed project scope and associated deliverables. Verifying the project scope includesreviewing deliverables for the individual project phases to ensure that each is completed satisfactorily and/orreasonable expectations that the deliverables can be met in subsequent project phases per the project

implementation lifecycle.

Scope verification is the process of obtaining the stakeholders formal acceptance of the completed projectscope and associated deliverables. Verifying the project scope includes reviewing deliverables to ensure thateach is completed satisfactorily.

In SAP implementation projects, hundreds of work packages (deliverables) are defined and are subject tothe scope verification process. It is highly recommended that a delegation-of-responsibility be created toaccomplish scope verification.

The Project WBS must serve as the foundation for the delegation-of-responsibility. It is recommended that asimple matrix be created (example below) to manage this process.

The Scope Verification matrix will be created by SAP Project Manager, Customer Project Manager, and during the Project Preparation

phase and updated after completion of the Blueprint workshops.

The Scope Verification matrix and Scope Management Plan must be approved by the following

stakeholders:

7/28/2019 Scope Management Template

7/7

- Customer Project Manager

- Customer Project Sponsor

- Steering Committee

- SAP Project Manager

-

Scope Control

Scope Control is focused on influencing the factors that create project scope changes and controlling the impact ofthose changes. As scope control assures that all requested changes and recommended actions are processed throughand Integrated Change Control process, the project will execute scope control in accordance with the IntegratedChange Control process. Please see the Integrated Change Control Procedure for detailed information.