Professional Documents
Culture Documents
(Mandatory)
PUBLIC
Project Charter (Mandatory)
Template
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>
SAP Delivery Executive Customer Project Sponsor(s)
DOCUMENT IDENTIFICATION
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
1 Final <Date> Internal
REVISION HISTORY
Version Date Description
1 November 5, 2017 <Text here>
2 November 1, 2017 Updated document to SAP 2017 template
2
TABLE OF CONTENTS
PROJECT PURPOSE OR PROJECT JUSTIFICATION AND MEASURABLE PROJECT OBJECTIVES 4
HIGH-LEVEL PROJECT DESCRIPTION AND BOUNDARIES 4
PROJECT SUCCESS AND APPROVAL CRITERA 4
ASSUMPTIONS AND CONSTRAINTS 4
HIGH-LEVEL REQUIREMENTS 4
HIGH-LEVEL SOLUTION AND PROJECT SCOPE 5
SUMMARY MILESTONE SCHEDULE 5
SUMMARY BUDGET 5
STAKEHOLDER GROUPS AND KEY NAMED STAKEHOLDERS 5
HIGH-LEVEL RISKS 5
REFERENCES/BIBLIOGRAPHY 7
3
Purpose of this Document
The Project Charter is the document to formally initiate the project, secure acceptance and commitment from
senior management, align stakeholders around the project objectives and to authorize the project
manager(s) to apply resources to the project.
Inputs
Order Form/Contracts
Business Case
Regulatory Requirements (Customer Environment)
Mandatory processes, documentation requirements, policies (Customer Environment)
Change Procedure
Any requests to change the Project Charter indicate a significant issue with the purpose and existence of the
project and require immediate attention from executive management.
The Project Charter needs to mirror the Order Form or Contracts in regards to the purpose of the project as
the Order Form is the legally binding document. The Project Charter can clarify the information from the
order form (for example how the customer objective will be achieved with the project), but it can’t introduce
deviations from the Order Form without a formal Change Order.
4
ASSUMPTIONS AND CONSTRAINTS
Items beyond the control of the Project Team that limit options. Items believed to be true for and project limits – based on the
Discovery and Evaluation Phase, can be further developed
Project Management is tasked to deliver the project within the following constraints:
- Delivery services budget
- Travel expense budget
- Timeline
- Quality
- Risk Profile
Identify any Legal Requirements, Compliance, Policies etc. that need to be followed by the project
- ITAR
- GMP
- Conflict Minerals
- Documentation Requirements
HIGH-LEVEL REQUIREMENTS
This section will outline the SAP solutions in scope and a high-level project scope. The project scope will be
detailed in a separate scope document.
Add any out-of-scope areas that are mentioned in the order form.
SUMMARY BUDGET
5
STAKEHOLDER GROUPS AND KEY NAMED STAKEHOLDERS
This paragraph identifies the organizational units of the customer that are impacted by the project and
key named stakeholders. A separate Stakeholder Register will be developed to identify all
stakeholders.
<Name> <...>
<Name> <...>
HIGH-LEVEL RISKS
Factors that may have a negative impact on the project
REFERENCES/BIBLIOGRAPHY
All sources, to which the text refers, are to be specified here
6
Headline Headline Headline
7
8
www.sap.com/contactsap
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.