1. Speaker’s Name, SAP Month 00, 2017
Project Kickoff
Speaker’s Name, SAP
Month 00, 2017
Partner logo

2. Agenda Time Topic Presenter 00:00 – 00:00 Introduction and Welcome
Executive Sponsor
Goals
Customer Project Manager
Lunch
Solution Scope
SAP Application Lead
Delivery Approach
SAP Project Manager
Break
Team Roles and Responsibilities
Critical Success Factors and Communication
Next Steps
All
End of the day

3. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication

4. Workshop Objectives Confirm the Project Scope
Understand the Delivery Approach
Review the system landscape
Introduce roles and responsibilities
Learn about the enablement approach
Examine critical success factors

5. SAP Team Introduction SAP Client Partner
<Name> , Contact Information
SAP Delivery Executive
SAP Project Manager
SAP Team Member(s)
<Name> , Application Lead, Contact Information
<Name> , Technology Lead, Contact Information

6. Customer Team Introduction
Customer/Executive Sponsor
<Name> , Department, Role, Contact Info
Customer Core Project Team Members
Customer Extended Project Team Members
<Name> , Department, Super User, Contact Info
<Name> , Department, UAT Tester, Contact Info

7. What Does Project Success Really Mean?
Functional Goals
Business Goals
Achieving the requested modifications or improvements in the business
Project Goals
Schedule Compliance
Budget Compliance

8. Success Depends on Everybody Involved
Project success is the sum of everybody’s daily work and decisions.
Processes
Management
Project
Key Users
Team
Organization
Technology
We look forward to realize a successful project with you.

9. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication

10. Solution Scope
The “Solution Scope” is related to what is included in the Solution and refers to what the Solution contains in order to meet the business need. Insert relevant slides for the Solution Scope. Use information from the Contract Scope or Statement of Work document.

11. Service Scope
The “Service Scope” summarizes the overall scope of the Service that will be delivered. Insert relevant information from the Contract Scope Document or Statement of Work.

12. Integration Points in Scope
From Product/Solution
To Product/Solution
Type
Description
Short description of integration point
From SAP product that integrates
To SAP product that integrates
Technical nature of integration e.g. ALE
Longer description of scope of integration perhaps covering business objects or data
Customer Master Data
CRM
ERP
CRM Middleware
Optional download and delta loads of customer master data from ERP to Business Partners in CRM
Use information from the Scope Document/Statement of Work. Add details of any integration points that are known and included in the scope of the Service. If not integration points exist, please delete this slide or add a statement that no integration points are in Scope.

13. Landscape
Present Landscape Diagram: Explain the role of Development, Quality Assurance and Production landscapes if applicable.

14. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication
Next Steps

15. Project Planning X Weeks X Weeks X Weeks Prepare Explore Realize
Go-Live
X Weeks
Steps
Prepare
Explore
Realize
Deploy
Prepare Project
XXX
XXX
XXX
XXX
Key Activities
Customer involvement
SAP involvement

16. SAP S/4HANA Cloud Phase Duration
Project duration varies based on implementation scope, project resources, and desired speed of implementation. The below chart represents a general guidance.
Phase\Project Size
Small
Medium
Large
Prepare 5 10
20<
Explore 23 45
60<
Realize 17 30
50<
Deploy 12
Numbers represent working days

17. Project Schedule W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 PhaseW1 W2 W3 W4 W5 W6 W7 W8 W9
W10
W11
W12
Phase
Description 1 2 3 4 5
Prepare
1.1
1.2.
1.3
1.4
1.5
Explore
2.1
2.2
Realize
3.1
3.2
3.3
3.4
3.5
Deploy
4.1
4.2

18. Prepare Phase Key Prepare Activities:
Define project goals, high-level scope, and a project plan
Identify and quantify business value objectives
Secure executive sponsorship
Establish project standards, organization, and governance
Define and secure approval for the implementation/upgrade strategy
Define roles and responsibilities for the project team
Validate the project objectives
Establish project management, tracking, and reporting mechanisms for value delivery
Begin self-enablement
Receive and access the system
Kick off the project

19. Explore Phase Key Explore Activities:
Project Management Execution, Monitoring, and Controlling
Customer Project Team Enablement
Solution Validation
Configuration Definition
Integration Prerequisites Confirmation
Solution Extension Preparation
Data Load Preparation
Phase Closure

20. Realize Phase Key Realize Activities: Establish the solution landscape
Implement the solution in the quality environment using incremental build in time-boxed iterations
Conduct overall end-to-end testing of the solution
Setup production environment
Prepare for data migration and data archiving
Conduct project team and key user training
Finalize end user training materials and documentation
Track and report on value delivery

21. Deploy Phase Key Deploy Activities:
Finalize the solution and business processes for production go-live
Resolve all crucial open issues
Conduct system tests
Proceed with cutover activities including data migration
Execute transition and cutover plans including organizational change management (OCM) plans
Complete all scheduled end user training
Track and report on value delivery

22. Testing Approach
Unit Testing – Performed by Configurator – Performed in Development Landscape
Integration Testing – Performed by the Customer –Performed in Quality Assurance Landscape
User Acceptance Testing – Performed by the Customer – Performed in Quality Assurance Landscape
Who and When will Test Plans and Scripts be written
Who will participate in Testing from the Customer?
How long should User Acceptance Testing last?
Explain the Role of Unit Testing and User Acceptance Testing. Discuss who is Responsible for each. Discuss how the customer will staff. Explain the role of the different landscapes in testing.

23. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication
Next Steps

24. Project Team and Roles Customer
Project Sponsor(s)
Champion, Critical Decisions, Escalations
Project Sponsor
Project
Management
Activity, Resource, Risk and Issue Management
Project Manager
Create a chart describing all the parties involved (including sponsors, stakeholders, project leads from both sides and consultants, possible interfaces to other organizations). Take information from the “Project Team Roles and Responsibilities” document.
Consultant
Functional
Expert
Consultants
Process Owners / SMEs
Consultants
Configuration Design
Configuration Validation
Business
Resource
Business
Stakeholders
Training Design and Delivery
Trainer
Trainers
Architecture, Connectivity and Migration
Technical
Resource
Technical
Resources

25. Customer Role Details Adjust as required Project Manager
Technical Resource
25 – 40% dedication for landscape setup
10 – 15% dedication during test phase
Confirm prerequisite components, add-ons, SPs, notes
Key Users
30 – 40% dedication throughout project
Explain business requirements & processes
Perform & confirm configuration
Drive decisions
Testers
10-15% dedication for configuration validation
Confirm configuration
Support decisions
Trainers
25-50% dedication for end user training
Create and execute training plan
Create training content
Adjust as required

26. SAP Role Details Adjust as required Consultants Custom Development
Manage project
Responsible for knowledge transfer to key users
Perform/guide the system configuration
Introduce integration concept
Perform integration setup and support integration testing
Coordinate additional resources as required
Custom Development
Provide
Project Manager
Provide support for incidents reported via self-service tools, web and phone
Customer Engagement
Ensure
Adjust as required

27. Responsibilities of the Steering Committee
The SC is responsible for project control and project coordination as well as the efficient bringing about of technical and organizational decisions.
In SC meetings, project management reports on the project status and introduces relevant issues that have to be decided by the SC.
The SC assures that resources necessary for the project‘s success are available.
The SC is the last escalation level for problems (conflict management).
The SC assumes highest-level control on costs and budget, and is responsible for budget release.
The SC is responsible for inspection and approval of results and of the overall project.
Adjust as required

28. Key Users Adjust as required
What is expected of key users during a SAP solution implementation project?
Make knowledgeable business decisions in your respective area of expertise and help to define the solution
Complete the implementation activities as assigned
Act as a multiplier within your organization to train and support end users
Learn how to configure the new system.
Adjust as required

29. Key User Responsibilities After Go-Live
Incident Management
Search for solutions and process incidents from end users directly and when necessary, request help from SAP
Manage Users and Task Assignment
Deal with user authorization requests
Maintain responsibilities for users in your company
Resolve any unassigned business tasks
Manage Background Jobs, Input and Output
Monitor background jobs
Monitor internal/external communications such as printers and integration with third-parties
Knowledge Transfer
Act as a multiplier within your organization to train and support new users of the SAP solution
Adjust as required

30. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication
Next Steps

31. Critical Success Factors
Scope changes will likely impact the project timeline, your required effort and consulting costs
Stay within the agreed scope
Adjust your processes to fit the standard system functionality in order to simplify future upgrades and scope expansion.
It doesn’t have to be perfect. You can always improve a solution later.
Have a pragmatic mindset
The quicker you can make decisions, the quicker your project will be able to proceed into the right direction.
Make quick decisions
Identify and involve your stakeholder early - executives, employees, labor unions, key customers,…
Involve stakeholders early
The better you represent your business area, the better the SAP cloud solution will support your processes.
Work with your manager to secure sufficient availability for the project.
As a key user, actively contribute to the project
Start cleansing your data as soon as possible to prevent project issues and delays.
Start preparing data early
Only thorough testing will result in a successful go-live and stable system.
Never cut corners on testing

32. Standards of Project Communication
Information
Information Sender
Information Recipient
Frequency
Form
Status Report
Customer PM
SAP PM, SC
Weekly
Project Status Report
Workshop Protocol
SAP
Key User, SAP PM, Customer PM
After each meeting
Result Protocol
Steering Committee Report
Customer PM, SAP PM, Board
Steering Committee Meeting Minutes
PM - Project Management
SC - Steering Committee

33. Agenda Introduction Solution Scope Delivery Approach
Team Roles and Responsibilities
Critical Success Factors and Communication
Next Steps

34. Thank you.
Contact information:
F name L name
Title
Address
Phone number
Partner logo