SCOPE STATEMENT

Template Document

PUBLIC
PROJECT IDENTIFICATION
Project Name CPI Project Number
<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>

DOCUMENT IDENTIFICATION
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Public

REVISION HISTORY
Version Date Description
0.1 February 4, 2010 Initial document
0.2 January 30, 2018 Updated accelerator and template

2
TABLE OF CONTENTS
PROJECT SCOPE................................................................................................................................................ 4
Project Goal.......................................................................................................................................................... 4
Customer Business Processes.......................................................................................................................... 4
Solution/Service Description.............................................................................................................................. 4
Project Requirements.......................................................................................................................................... 4
Proposed Delivery Model.................................................................................................................................... 4
Standardized Service Identified.......................................................................................................................... 4
PROJECT OBJECTIVES...................................................................................................................................... 4
DELIVERABLES................................................................................................................................................... 5
WORK PACKAGES.............................................................................................................................................. 5
PROJECT BOUNDARIES..................................................................................................................................... 5
Out of Scope......................................................................................................................................................... 5
PROJECT ASSUMPTIONS................................................................................................................................... 5
PROJECT CONSTRAINTS................................................................................................................................... 5
RISK ADDESSMENT............................................................................................................................................ 5
IMPLEMENTATION STRATEGY.......................................................................................................................... 5
INITIAL WORK BREAKDOWN STRUCTURE...................................................................................................... 5
PROJECT ORGANIZATION................................................................................................................................. 5
ACCEPTANCE CRITERIA.................................................................................................................................... 6
SCHEDULE MILESTONES................................................................................................................................... 6
RESOURCES PLAN............................................................................................................................................. 6
ORDER OF MAGNITUDE PROJECT COSTS...................................................................................................... 6
CONFIGURATION MANAGEMENT REQUIREMENTS........................................................................................6
NECESSARY TO PROCEED................................................................................................................................ 7

3
PURPOSE
The Scope Statement provides a definition of the project. It documents the products and services that are to be
produced by the project, as well as the boundaries of the project. The Preliminary Scope Statement is developed
during Initiating and additional detail is captured in Planning.

PROJECT SCOPE
Define what work needs to be completed during the project.

Project Goal
Describe the overall goal that is to be achieved by the project.

Customer Business Processes

Solution/Service Description
Document the characteristics of the solution/service the project was undertaken to create. This will be refined
during the Planning Process.

Project Requirements
Document the capabilities or conditions that must be met.

Proposed Delivery Model

Describe the service delivery model, the resource deployment, site/offshore working model and reasons why.

Standardized Service Identified

Describe identified standardized service if it’s applicable for the project.

PROJECT OBJECTIVES
Aligned to corporate, organizational strategies, and project goal. Objective should be “SMART.”
 S-
 M-
 A-
 R-
 T-

4
DELIVERABLES
Produced by the team to ensure success.

WORK PACKAGES
Work packages (WP) is a predefined scope of work with predefined scope, clearly defined deliverables, and
approach for delivery and specified effort and duration consisting of a logical group of processes/configuration
especially when the work is done remotely.

PROJECT BOUNDARIES
Identify specific systems within scope.

Out of Scope

PROJECT ASSUMPTIONS
Items believed to be true for and project limits.

PROJECT CONSTRAINTS
Items beyond the control of the project team that limit options.

RISK ADDESSMENT
Factors that may have a negative impact on the project.

IMPLEMENTATION STRATEGY
The implementation approach selected for the project.

INITIAL WORK BREAKDOWN STRUCTURE

Decomposition of deliverables.

PROJECT ORGANIZATION
Individuals and organizations that have specific roles in the project.

5
ACCEPTANCE CRITERIA
Used for customer acceptance:
 [Text here]
 [Text here]

SCHEDULE MILESTONES
Key project events.

Milestone description Date

RESOURCES PLAN

Onsite Offshore(
Name SAP Organization (Partner) Role Rate/day Grand total cost
(days) days)

Grand Total Cost

ORDER OF MAGNITUDE PROJECT COSTS

ESTIMATED TOTAL PROJECT COSTS THROUGH CLOSING
 Rough $
 Range $ to $


CONFIGURATION MANAGEMENT REQUIREMENTS

The approach for documenting project characteristics.

6
NECESSARY TO PROCEED
Required to move to the next phase, planning.
Estimated Costs through Planning Checkpoint
 Rough $
 Range $ to $


7
www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.