W Bs Dictionary

WBS # WBS item title
1 Project Preparation
1 1 Project Initiation
Allocate Resources - hard booking with resource

1 1 1
management
1 1 2 Prepare Team Onboarding Document
1 2 Project Governance
1 2 1 Define Project Organization
1 2 2 Assign Roles and Responsibilities
1 2 3 Complete communication management plan
1 3 Project Charter
1 3 1 Prepare Project Charter Document
1 3 2 Identify Stakeholders
1 3 3 Obtain Project Charter Sign-off
1 4 Kick-Off Workshop
1 4 1 Prepare for Kickoff Meeting

1 4 2 Perform Kickoff Meeting
1 5 Scope Statement
1 5 1 Document Customer Requirements
1 5 2 Review Scope Statement with Customer
1 5 3 Create Work Breakdown Structure and WBS Dictionary
1 5 4 Refine Acceptance Criteria
1 5 5 Obtain customer sign off for project scope
1 6 Project Schedule and Budget
1 6 1 Develop delivery schedule and assign resources
1 6 2 Include key workshops into the project schedule

1 6 3 Obtain Customer sign-off for project schedule
1 6 4 Establish Cost and Schedule baseline
1 7 Project Management Plan
1 7 1 Prepare Project Management Plan
1 7 2 Obtain Project Management Plan Sign-Off
1 8 Project and Operational Standards
1 8 1 Conduct ALM Roadmap
1 8 2 Determine Solution Documentation Procedure
1 8 3 Determine Solution Implementation Procedure
1 8 4 Determine Template Management Procedure
1 8 5 Determine Test Management Procedure
1 8 6 Determine Change Control Management Procedure

1 8 7 Determine Application Incident Management Procedure
1 8 8 Determine Technical Operations
1 8 9 Determine Business Process Operations
1 8 10 Determine Maintenance Management
1 8 11 Determine Upgrade Management
1 9 Execution, Monitoring, and Controlling of Results
1 9 1 Direct and manage project execution
1 9 2 Monitor and control project activities
1 9 3 Manage Issues, Risks and Changes

Communicate Status and progress to project
1 9 4
stakeholders
1 10 Organizational Change Management Roadmap
1 10 1 Prepare Organizational Change Management Roadmap
1 11 Project Training Strategy and Plan (team + key-users)
1 11 1 Prepare training strategy and plan document
1 12 Project Team Training
1 12 1 Conduct Solution Training and knowledge transfer
1 13 Business Process Map
1 13 1 Prepare Business Process Map
Prepare Demo Environment for Scope Refinement

1 13 2
Workshops
1 13 3 Prepare Scope Document for Workshop
For <SCOPE OPTION> - Demonstrate the business
1 13 4
processes and predefined options list
Complete Customer Blueprint and Configuration

1 13 5
Requirements Template
1 13 6 Validate and Complete business process map
1 14 Value Determination
1 14 1 Prepare Value Map

1 14 2 Validate and Complete Value Map
1 15 Business Scenario Design
1 15 1 Capture Business Scenario Requirements
1 15 2 Validate and Complete Scenario Design
Store Scenario Level Solution Documentation in SAP

1 15 3
Solution Manager.
1 16 Prepare Testing Policy
1 16 1 Prepare Testing Policy document
1 16 2 Obtain Customer Sign-Off for Testing Policy document
1 17 Data Migration Approach and Strategy
1 17 1 Prepare Data Migration Workshop
1 17 2 Conduct Data Migration Workshop
1 17 3 Conduct Data Audit (Data Health Check)
Prepare Data Migration Scope and Requirements

1 17 4
Document
1 17 5 Present DM scope and requirements document
1 17 6 Conduct Organizational Assessment for Data Migration
1 17 7 Conduct Infrastructure Assessment for Data Migration

Conduct Risk Assessment for Data Migration and
1 17 8
Prepare Mitigation Plan
Complete the Data Migration approach and strategy

1 17 9
document
Technical Requirements and Design and Solution

1 18
Landscape Deployment Plan
1 18 1 Define Solution Landscape Concept
1 18 2 Define Solution Deployment Concept
1 19 Interface Inventory
1 19 1 Prepare Interface Inventory document
1 20 Initial Hardware Sizing Proposal
1 20 1 Complete HW sizing estimation for solution landscape
1 21 Project Support Tools and System Setup

Verify Technical System Requirements (frontend /
1 21 1
backend)
1 21 2 Verify Functional System Requirements
1 21 3 Check availability of SAP Solution Manager
1 21 4 Install or Upgrade SAP Solution Manager
Set up Business Process Hierarchy in SAP Solution

1 21 5
Manager
Setup of project logistics and infrastructure, including

1 21 6
team collaboration environment
1 21 7 Install SAP GUI on project team computers
Test Remote Access and Establish OSS Connection

1 21 8
(both GUI and Web Access)
1 21 9 Prepare SAP Best Practice Activation
Execute Technical Installation of SAP Products (Pre-

1 21 10
defined solution Components)
1 21 11 Perform Installation check
1 21 12 Review installation check and knowledge transfer

Prepare authorization roles in the systems for the project
1 21 13
team (DEV)
1 21 14 Set up of testing tools
1 22 Phase Closure and Sign-Off phase Deliverables
1 22 1 Conduct Knowledge Management Gate

1 22 2 Conduct Project Quality Gate
1 22 3 Conduct Project Management Review Service
1 22 4 Obtain Customer Sign-Off for Phase Completion

1 23 MILESTONE: Project Start to Design
2 Business Blueprint
2 1 Phase Initiation
2 1 1 Allocate Resources and Update Project Schedule
2 2 Execution, Monitoring and Controlling Results
2 2 1 Update Project Management Plan


2 2 5
stakeholders
2 3 Stakeholder Analysis
2 3 1 Conduct classification of project Stakeholders
2 3 2 Identify Key Users
2 4 Change Impact Analysis
2 4 1 Validate organizational alignment approach
2 4 2 Establish Baseline of Current State
2 5 Communication Plan
2 5 1 Define Value Argumentation / Key Messages
2 5 2 Define Communication strategy
2 6 End User Training Strategy and Plan
2 6 1 Conduct Learning Needs Analysis
2 6 2 Develop Detailed End-User Training Plan

2 7 1 Conduct Blueprint Ramp-up Training
2 7 2 Conduct Key User training
2 8 End User Training Content
2 8 1 Adaptation of Pre-delivered Training Content
Prepare and Build Training Content in Project

2 8 2
Environment
2 9 Scope Validation / Fit-Gap Analysis
For <General Settings #1 - n> - Conduct Validation and

2 9 1
Fit-gap Analysis
For <Scenario #1 - n> - Conduct Validation and Fit-gap

2 9 2
Analysis
For <Process #1 - n> - Conduct Validation and Fit-gap
2 9 3
Analysis
Validate pre-defined RICEFW Objects (reports, forms

2 9 4
etc.)
2 9 5 Determine Gap list and effort estimation
2 10 Business Solution Design for Business Objects
2 10 1 Define Business Organization Structure
2 10 2 Define General Settings and Master Data
2 10 3 Define User Role Concept
2 10 4 Define Logical Data Model

2 11 Detailed Design - Business Scenario #1 -n
2 11 1 Capture Business Scenario Requirements
2 11 2 Complete Business Scenario Design Document
2 12 Detailed Design - Business Process #1 - n
2 12 1 Capture Business Process Requirements
2 12 2 Complete Business Process Design Document
2 12 3 Demo or Visualize Standard Functionality
2 13 Value Realization
2 13 1 Prepare Value Dashboard
2 14 Detailed Design - Configuration and Enhancements
2 14 1 Finalize Core Configuration Design
2 14 2 Finalize Delta Configuration Design

2 14 3 Define functional Design - RICEFW Object #1 - n
Define Functional Design - SOA & 3rd party applications

2 14 4
#1 - n
2 15 Visualization
2 15 1 Conduct Visualizations
2 15 2 Prepare Initial Business Process Procedure document
2 16 Legacy Data Migration
2 16 1 Ensure Master Data Management Processes Ownership
Conduct Data Mapping workshops (master data for pre-

2 16 2
defined solutions)
2 16 3 Conduct Data Quality Assessment
2 16 4 Define Automated Data Migration Approach
2 16 5 Define Manual Data Migration Approach
2 16 6 Prepare Data Quality Plan
2 16 7 Prepare Data Security Design and plans
2 17 Legacy Data Archive

Prepare baseline framework for the legacy data
2 17 1
archiving solution
2 18 Technical Solution Design
2 18 1 Prepare technical infrastructure specification
2 19 User Access and Security
2 19 1 Authorization Requirements and Design
2 20 Development Environment (DEV)
Execute Technical Installation of SAP Products for DEV

2 20 1
environment
Execute Technical Upgrade of SAP Products for DEV
2 20 2
environment
2 20 3 Install Solution Documentation in Solution Manager
2 20 4 Execute Technical Installation of 3rd party products

Set up Role assignment / Authorizations / Test Users in
2 20 5
DEV
2 20 6 Perform Manual Configuration in DEV
Validate Role assignment / Authorizations / Test Users in
2 20 7
DEV
Create master data in DEV environment - Master Data
2 20 8
#1 - n
2 21 Testing Strategy
2 21 1 Prepare Test Strategy document
Define Test data approach and validated pre-defined

2 21 2
master data
2 21 3 Review and Validate Testing Strategy with customer
2 21 4 Obtain customer sign-off on Testing Strategy.
2 21 5 Initiate Performance Testing preparation activities
2 22 4 Conduct Design Review Service
2 22 5 Manage Fulfilled Contracts

2 23 MILESTONE: Design to Build
3 Realization

3 2 5
stakeholders
3 3 Organizational Alignment
3 3 1 Execute Role Mapping and Transition Planning
3 3 2 Conduct Sounding Board/Pulse Checks
3 3 3 Refine and Execute Communication Plan
3 4 Educational Readiness Review
3 4 1 Prepare Educational Readiness Report
3 5 Knowledge Transfer
Prepare for Key User Knowledge Transfer for <SCOPE

3 5 1
OPTION>
Perform Solution Walkthrough and knowledge transfer to

3 5 2
Key Users for <SCOPE OPTION>
3 6 End User Training Delivery Enabled
3 6 1 Prepare End User Training Materials and Documentation
3 6 2 Set up Training Environment
3 6 3 Perform Training of the Trainers
3 6 4 Develop End User Training Schedule and Logistics plan
Configured General Settings and Organizational

3 7
Structure
3 7 1 Configure General Settings
3 7 2 Configure Organizational Structure

3 8 Configured Master Data Objects #1 - n
Prepare and Load master data - Master Data Object

3 8 1
<MASTER DATA OBJECT NAME>
3 8 2 Configure Master Data Objects #1 - n
3 9 Core Configuration and Documentation - Process #1 - n
Complete Core Configuration, including documentation

3 9 1
and test cases
3 9 2 Prepare Unit Test Cases
3 9 3 Prepare String Test Cases
3 9 4 Execute Business Process Unit Test
3 9 5 Perform defect resolution for Business Process Unit Test
3 9 6 Execute Business Process String Test
3 9 7 Perform defect resolution for Process String Test
3 10 Delta Configuration - Process #1 - n
3 10 1 Complete Delta Configuration
3 10 2 Complete Delta Process Documentation
3 10 3 Complete Delta Process Test Cases
3 10 4 Execute Business Process Unit and String Test Cases
3 10 5 Perform defect resolution for Unit and String Test

3 11 Enhancement Development - RICEFW Object #1 - n
3 11 1 Develop RICEFW Object #1 - n
3 11 2 Document RICEFW Object #1 - n
3 11 3 Execute Test Cases - RICEFW Object #1 - n
3 11 4 Perform defect resolution for RICEFW Object(s) Test
3 11 5 Conduct Final Code Review
3 12 SOA / Composite Application Development #1 - n
3 12 1 Develop, document and test Enterprise Service #1 - n
Develop, document and test Composite and/or Mobile

3 12 2
Application #1 - n
Conduct Final Code Review for SOA / Composite

3 12 3
Application
3 13 Business Process Procedure
3 13 1 Develop Business Process Procedure Document

Validate and Complete Business Process Procedure
3 13 2
Document
3 14 Value Audits
3 14 1 Perform Value Audit
3 15 Scenario Test #1 - n
3 15 1 Prepare Test Case - Scenario #1 - n

3 15 2 Execute Test Case - Scenario #1 - n
3 15 3 Resolve Issues for Scenario #1 - n
3 15 4 Obtain Customer Sign-off for Testing of Scenario #1 - n
3 16 Quality Assurance Environment (QAS)
Execute Technical Installation of SAP Products for QAS

3 16 1
environment
Execute Technical Upgrade of SAP Products for QAS
3 16 2
environment
Import Configuration and Development Objects to QAS

3 16 3
Environment
Set up Role Assignment / Authorizations / Test Users in

3 16 4
QAS
Prepare and Load Master Data into QAS Environment
3 16 5
for <SCOPE OPTION>
3 16 6 Perform Manual Configuration Settings in QAS
3 17 MILESTONE: Build to Test
3 18 Preliminary Cutover plan
Conduct Organizational Change Management

3 18 1
Readiness Check
3 18 2 Conduct Production Support Readiness Check
Conduct Master Data Process Governance Readiness
3 18 3
Check
3 18 4 Prepare Preliminary Cutover plan
3 18 5 Review Preliminary Cutover Plan with customer
3 18 6 Refine Preliminary Cutover Plan

3 19 Approved Integration Test
Prepare Integration Test Plan, including test of roles and

3 19 1
authorizations
3 19 2 Prepare and document Integration Test Case #1 - n
3 19 3 Execute Integration Test Case #1 - n
3 19 4 Perform defect resolution for Integration Test
3 19 5 Obtain Integration Test Results Sign-off
3 20 Legacy Data Migration
3 20 1 Develop Data Migration Program Units
3 20 2 Execute and validate Manual Data Migration
3 20 3 Obtain Data Quality Reports
3 20 4 Perform SAP Target Load Test
3 20 5 Obtain Data Migration Test Results
3 20 6 Conduct Final Data Quality Assessment
3 21 Approved User Acceptance Test
3 21 1 Prepare UA Test Plan for <SCOPE OPTION>

3 21 2 Tool adaption and delta UAT training
Prepare and Document User Acceptance Test Cases for

3 21 3
<SCOPE OPTION>
3 21 4 Execute UA Test Plan for <SCOPE OPTION>
3 21 5 Perform UA Defect Resolution for <SCOPE OPTION>
3 21 6 Obtain UA Test Results Sign-off
3 22 SAP Data Archiving
3 22 1 Capture Legal and Business Retention Requirements
3 22 2 Prepare Data Archive Plan
3 22 3 Prepare Data Archive Storage Plan
3 22 4 Conduct Data Archive Implementation Test
3 23 Production Environment (PRD)
Execute Technical Installation of SAP Products for PRD

3 23 1
Environment
Execute Technical Upgrade of SAP Products for PRD
3 23 2
Environment
Import Configuration and Development Objects to PRD

3 23 3
Environment
Set up Role assignment / Authorizations / Test Users in

3 23 4
PRD for <SCOPE OPTION>
Populate PRD with Test Master Data for <SCOPE
3 23 5
OPTION>
Prepare and Load master data into PRD environment for
3 23 6
<SCOPE OPTION>
Perform Manual Configuration Settings in PRD for
3 23 7
<SCOPE OPTION>
3 24 Failover Environment
3 24 1 Prepare Failover Environment Design and Plan

Set-up Failover Environment and Execute Identified
3 24 2
Scenarios
3 24 3 Obtain Failover Environment Test Results
3 25 System and Performance Test
3 25 1 Prepare System Test Plan
3 25 2 Prepare Performance Test Plan
3 25 3 Prepare System Test Cases
3 25 4 Prepare Performance Test Cases
3 25 5 Execute Performance Tests
3 25 6 Perform Performance Test Defect Resolution
3 25 7 Obtain Test Results Sign-off
3 26 SAP Going Live Check
Perform SAP Going Live Check - Analysis Session and

3 26 1
schedule the Verification Session
3 27 System User Roles and Authorization Administration
Set up administrative procedures for Roles and

3 27 1
Authorizations
3 28 Technical Operations and Handover Plan
3 28 1 Validate Support Center/Help Desk Staffing Strategy
3 28 2 Establish Support Processes
3 28 3 Set-up Business Process Monitoring
3 29 Technical Integration Check
3 29 1 Conduct TIC Service
3 30 2 Conduct Project Quality Gate(s)

3 30 4 Conduct Design Review Service

3 31 MILESTONE: Test to Deployment
4 Final Preparation

4 2 5
stakeholders
Organizational and Production Support Readiness
4 3
Check
4 3 1 Perform Business validation and Transition Planning
Validate that Master Data Support Processes is

4 3 2
established
4 3 3 Establish Business Process Operations
4 3 4 Establish System Administration and Control
4 3 5 Establish Security / Role and Authorization Management
4 3 6 Execute Transition to Production Support
4 4 Pre Go-Live End-User Training Delivery
4 4 1 Validate and adapt end user training material developed
4 4 2 Deliver End User training
4 4 3 Collect Training Evaluations feedback
4 4 4 Perform People Readiness assessment
4 5 Approved Technical System Tests

4 5 1 Execute Technical System Tests
4 5 2 Perform System Test Defect Resolution
4 5 3 Obtain System Test Results Sign-off
4 6 Production Cutover
4 6 1 Execute Go Live Simulations 1 thru N
4 6 2 Conduct Data Quality Readiness Check
4 6 3 Finalize Cutover Plan
4 6 4 Perform Pre-Cutover Weekend Closing Activities
Final Check of Production Readiness and Sign-Off for

4 6 5
transition to Production
Perform Cutover Weekend Activities including Final

4 6 6
Production Data Load
4 6 7 Obtain Production Data Load Sign-off
Initiate Solution Manager Update - Solution

4 6 8
Documentation

4 8 MILESTONE: Production System Live
5 Go Live Support


5 2 5
stakeholders
5 3 Knowledge Support Strategy
Define Mid-Term and Long-Term Knowledge Support

5 3 1
Strategy for Customer
5 4 Post Go live End-User Training
5 4 1 Prepare End-User Training for <SCOPE OPTION>
5 4 2 Deliver End-User Training for <SCOPE OPTION>
5 4 3 Collect Training Evaluations feedback
5 4 4 Perform People Readiness assessment
5 5 SAP Going Live Check - Verification Session
Conduct SAP Going Live Check - Verification Session

5 5 1
Remote
5 6 Production Support After Go Live
5 6 1 Provide Post Go Live Support
5 6 2 Monitoring Open Issues to Resolution
5 6 3 Resolve Functional Issues

5 6 4 Resolve Technical Issues
Complete Transition to Customers Production Support

5 6 5
organization
Finalize Solution Manager Update - Solution

5 6 6
Documentation
Obtain Solution Transition to Production Acceptance

5 6 7
Protocol Sign-off
5 7 MILESTONE: Deploy to Run
5 8 End User Acceptance Survey
5 8 1 Prepare and distribute Survey to EU
5 9 Project Closure and Sign-Off Project Deliverables

5 9 5 Resolve and close open issues
5 9 6 Finalize Project Closeout Report
Obtain Sign-off for Project Closure and Results

5 9 7
Acceptance
5 10 MILESTONE: Project Complete
6 Operate
6 1 Operations Maturity Assessment
Perform evaluation and assessment of operations

6 1 1
capabilities, including CoE operational set up
6 1 2 Prepare Maturity Assessment Report
6 2 Solution Documentation Optimized
6 2 1 Perform assessment of Solution Documentation set up
6 3 Solution Implementation Optimized
6 3 1 Perform assessment of Solution Implementation set up
6 4 Template Management Optimized
6 4 1 Perform assessment of Template Management set up
6 5 Test Management Optimized

6 5 1 Perform assessment of Test Management set up
6 6 Change Control Management Optimized
Perform assessment of Change Control Management

6 6 1
set up
6 7 Application Incident Management Optimized
6 7 1 Perform assessment of Incident Management set up
6 8 Technical Operations Optimized
6 8 1 Perform assessment of Technical Operations set up
6 9 Business Process Operations Optimized
6 9 1 Perform assessment of Process Operations set up

6 10 Maintenance Management Optimized
Perform assessment of Maintenance Management set

6 10 1
up
6 11 Upgrade Management Optimized
6 11 1 Perform assessment of Upgrade Management set up

Q-Gate
Description
Relevant
This phase provides initial planning and preparation for the project.
Although each project has its own unique objectives, scope, and
priorities, the deliverables outlined below assist in completing the
initiation and planning steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that

a new project exists. It supports the decision to accept the project, align
stakeholders – such as clients, customers, and SAP management – around
a project and its scope, provide updated information for planning, and obtain
a commitment to proceed. It ensures alignment between SAP, the
customer’s strategic direction, and the satisfaction of operational
requirements.
The purpose of phase resources allocation is a confirmation of resource
availability for the particular phase.
The purpose of this activity is to prepare the onboarding package for external
Mandatory
consultants from SAP and partner companies.
The purpose of this deliverable is to ensure that an efficient management
framework is in place for successful project execution.
The purpose of this task is to define the organizational structure, roles and
Mandatory
responsibilities of the project team.
The purpose of this task is to identify and select global company and
external resources for the project in accordance with the required roles, skills
and responsibilities specified in the preceding task. The assignment of
people to roles should also take into account their qualifications and
availability for the whole project time frame.
The purpose of this task is to complete the communications management

plan. This document outlines the processes required to ensure timely
generation, distribution, storage, and retrieval of project information.
The purpose of this deliverable is to clearly and explicitly define the

objectives of the proposed project, analyze all possible benefits and quantify
Mandatory
benefits in financial terms. This information and supporting documents align
key stakeholders around the strategic intent of the project.
The purpose of this activity is to collect all input required for the project
charter and document it into a format suitable for both communication
purpose as for formal sign-off purpose, if possible utilizing the accelerator
file(s) provided
The purpose of this activity is to ensure that the correct groupings of
stakeholders have been identified for the project.
The purpose of this activity is to achieve a formal sign-off of the project
charter.
The purpose of this deliverable is to kick-off the project/phase and ensure
that all needed information is shared with the resources for a successful Mandatory
project execution.
The purpose of this task is to prepare the kickoff meeting which will helps
ensure the involvement of the team and other key resources and their
commitment to the project schedule.
The purpose of this activity is to gather the whole project team, including all
remotely involved resources, to kick-off the project or project phase. The
meeting is also used to examine the approach for the specific project phase.
The purpose of this deliverable is to facilitate an initial understanding of the

project scope and associated project-related assumptions and constraints.
The project scope statement evolves through the initiation and planning of
Mandatory
the project and clearly and explicitly defines the deliverables of the proposed
project. This information and supporting documents align key stakeholders
around what the project is going to deliver.
The purpose of this activity is to collect and document both process-related

as well as project-/non-process-related customer requirements, which in
summary and as appendix become part of the scope statement
The objective of this task is to review the scope statement document with the
customer project manager and key stakeholders in order to confirm the
scope and obtain approval.
The purpose of this task is to create the work breakdown structure (WBS) for
the project, which is a deliverable-oriented, hierarchical decomposition of the
work to be executed by the project team to complete the project. It is the
Mandatory
basis for the organization and coordination of the project. A WBS consists of
WBS elements that describe project tasks and subtasks to perform within a
defined time period.
The purpose of this activity is to clearly define the acceptance criteria against
which project deliverables and results are measured that have been listed in
the Scope Statement. These should also be updated in the Project Quality
Gate Scorecard. In the context of Agile projects this translates to the
definition of Done for the backlog items that are being delivered in the
project.
Purpose of this task is to obtain customer approval (sign-off)
The purpose of the Project Schedule deliverable is to define the work

schedule to be followed, the resources and associated time commitments
required for the project and the phases of the project. The work breakdown
structure (WBS) serves as the foundation for the schedule, the deliverables
to be produced and tasks to be performed, as part of the project. The project
budget, including monitoring and control, outlines all costs associated with
the project, including labor, hardware, software, contracting fees, and
facilities.
At a minimum, the schedule should include:

Deliverables and tasks for the current phase
Estimated effort (work) and duration
Task dependencies (such as predecessors and successors)
Scheduled start and finish dates for each task, based on dependencies
Task constraints (such as must-start-on date and must-finish-on date)
Resources assigned to each task
High-level schedule for subsequent phases
The purpose of this activity is to create the project/phase schedule and

Mandatory
assign resources to the scheduled activities and tasks.
The purpose of this activity is to extract all planned workshops during the
project/phase into a schedule that facilitates workshop planning
The purpose of this activity is to create project schedule and cost baseline
Mandatory
against which tracking, change management and status reporting is done.
The purpose of the project management plan deliverable is to develop the

project management plan and the subsidiary plans on the basis of the project Mandatory
scope defined in the project charter.
The purpose of this activity is to collect input needed for the project
management plan and document it in a format suitable for both
communication purpose as for formal sign-off purpose, if possible utilizing
the accelerator file(s) provided
The purpose of this activity is to achieve a formal sign-off of the project
management plan
The purpose of the Project and Operational Standards deliverable is to
provide consistent means of executing and governing project work in an
efficient and effective manner. The key objective of Project Standards is to
identify, define, approve, and communicate standards related to project
execution.
Where and when applicable, the current customer processes and
procedures, related to the project standards should be taken into account
when defining the most suitable standards for the project.
The purpose of this task is to analyze the Application Lifecycle Management

(ALM) maturity at the customer to understand system landscape,
organizational structure requirements, usage of Solution Manager and other
ALM tools and provide recommendations for implementation of ALM
processes with SAP Solution Manager
The purpose of this task is to determine the customers framework to centrally
document and relate business processes and technical information of SAP
Mandatory
and non-SAP Solutions in Solution Manager, ensuring transparency, efficient
maintenance and collaboration
The purpose of this task, also known as Innovation Management, is to
determine the customers approach for the identification, adaptation and
implementation of new and enhanced business and technical scenarios. It is
part of the application lifecycle and designed to decouple technical Optional
installation from business innovation using SAP Solution Manager to
implement the innovation in the system landscape.
The purpose of this task is to determine the customers template

management approach that allows customers with multi-site SAP
installations to efficiently manage their business processes across
geographical distances – from initial template definition to template
implementation and template optimization, for example as part of a global
rollout
The purpose of this task is to determine the customers approach for
managing functional and performance testing of SAP-centric business
processes to ensure validated system behavior after software change Optional
events.
The purpose of this task is to determine the customers approach of handling

business and technology-driven changes, using a standardized process
Optional
leading to improved reliability of solution and minimized risk through
segregation of duties and transparency of changes.
The purpose of this task is to determine the customers approach of a
centralized and common incident and issue message processing for multiple
organization levels. The process offers a communication channel with all
relevant stakeholders of an incident, including business user, customer-side
SAP experts, SAP Service & Support and Partner Support employees.
The Application incident Management is integrated in all ALM processes of
SAP Solution Manager, in any SAP Business Suite solution and can be
connected to an Non-SAP Help Desk application.
The purpose of this task is to determine the customers approach of

monitoring, alerting, analyzing and administrating of SAP solutions. It allows
customers to reduce TCO by predefined content and centralized tools for all
aspects of operations in SAP Solution Manager, including End-to-End Optional
reporting functionality either out-of-the-box or individually created by
customers
This task uses SAP Business Process Integration & Automation

Management (BPIAM) to cover the most important application related
operations topics necessary to ensure the smooth and reliable flow of the
core business processes to meet a company's business requirements.
The purpose of this task is to determine the customers approach of

Maintenance Management, how SAP Notes are handled and how they are
applied (upon request e.g. current incident in productive environment,
information from SAP about potential issue (Hot News, Security Notes)).
The purpose of this task is to determine the customers approach for the
identification, adaptation and implementation of new and enhanced business
and technical scenarios. It uses Solution Manager to manage the upgrade
project holistically and effectively end-to-end and allows SAP customers to
better understand and manage the major technical risks and challenges in
an upgrade project, and to make the upgrade project a “non-event for the
business.”
The purpose of this deliverable is to execute the project management plan

and control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see
deliverable “Project Management Plan”) guide the approach to management,
execution, and control of project activities. The project manager is
responsible for ensuring that the management plans are applied at the
appropriate level of control.
The purpose of this activity is to assure that the project is executed

according to what was agreed to in project charter, scope statement and
project management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and
risks and changes related to those e.g. changes of project scope, timeline, Mandatory
costs etc.
The purpose of this activity to make sure that project stakeholders are aware
of status and progress of the project including potential disturbances due to Mandatory
existing risks and issues.
The purpose of this deliverable is to present an overview of all planned
change management activities. It guarantees that all activities are related to
Optional
each other as well as to the overall project plan and ensures the
“checkability” of OCM activities.
The purpose of this activity is to collect all required input for the OCM
roadmap and document it in a format suitable for communication and
inclusion into the project management plan
The purpose of this deliverable is to develop a comprehensive training

strategy that provides all team members with a phase-based learning path
for acquiring the skills and knowledge needed to complete the project
successfully. This learning path leads to project readiness as well as
certification on the specific applications the team members will be using.
The purpose of this task is to prepare the training strategy and plan. Optional
The purpose of this deliverable is to provide an overview of the SAP software

to be implemented so that all project team members have an understanding
of the SAP solution for their areas of responsibility.
The purpose of this task is to train the involved project team in the SAP
solutions expected to be used and/or chosen for the project scope
The purpose of the business process map is to derive and agree on the
scope for the start of the business blueprint phase. During blueprinting, the
process map builds the foundation for the process hierarchy – a Mandatory
decomposition of the process design – which is reflected as scenarios,
processes, and process steps in SAP Solution Manager.
The purpose of this task is to complete the Business Process Map with the
content reflecting the process scope of the project
The purpose of this task is to ensure that a proper environment is available
for the options selection workshops
The purpose of this task is to prepare the scope document with the pre-
defined content according to the SOW and solution documentation
The purpose of this task is to demonstrate available options related the
selected processes in scope
The goal of this task is to complete customer blueprint document based on
interviews and assessment sessions. The document details the options
customer selected from the pre-defined solution, all modifications and details
the configuration requirements of the solution.
Validate and Complete Business Process Map with pre-defined content
depending on delivery model (Industrialized and/or Assemble to Order
process content).
The purpose of Value Determination is to ensure the alignment of the
business case value drivers with key process changes and functionality by
Optional
establishing a value tracking framework and identifying business
stakeholders
The purpose of this task is to review the project business case, map key
value drivers to process changes, develop the value tracking framework
(KPI's and PPI's), identify value enablers, as well as assign business
accountability for value realization.
The purpose of this task is to validate that identified key process changes,
key performance indicators, and value enablers are accurate and make Optional
necessary adjustments to the document
The purpose of business scenario design is to provide an understanding of
the essential processes at the scenario level (process level 1-2). It builds the
foundation for the business blueprint phase where process levels 3-5 are
defined.
The purpose of this task is to capture Business requirements and relate them
to business scenarios, business objectives and benefits
The purpose of this task is to complete the Business Scenario Design
document with relevant pre-defined business process content (Assemble to
order and/or Industrialized content)
The purpose of this task is to store Business Scenario content in Solution
Manager, according to Business Process Hierarchy structure defined for the
project.
The purpose of this deliverable is to outline key elements of the testing
methodology that the project will use as guiding principles going forward.
This is should be aligned with the customers "Enterprise" approach on how
to conduct testing (Not to be updated over time)
The purpose of this task is to collect all required information needed for the
Test Policy, and to document it in a format suitable for communication.
The purpose of the data migration approach and Strategy deliverable is to

capture and communicate the approach and strategy for the legacy data
migration. This deliverable is intended to educate the SAP and customer
Optional
project team members on the SAP data migration framework and
methodology used to support the data migration project. In addition, the
scope and requirement for data migration should also be determined
The purpose of this task is to make the necessary arrangements for the
execution of the workshop
The purpose of the data migration workshop deliverable is to perform a two-
day scoping workshop to explain the SAP data migration approach and to
understand the customer’s legacy data systems, business priorities, and
technical infrastructure.
The purpose of the data audit is to identify the legacy systems that will
supply data for the SAP applications and to profile the quality of the legacy
data.
The purpose of this task is to prepare the data migration scope and
requirements document that captures the overall scope and requirements of
the data migration effort.
The purpose of this task is to present data migration scope and requirements
document to customer project team and obtain buy in.
The purpose of this task is to assess customer organization for the demands
of data migration process. The outcome of this task is documented current
state of the organization and required target state.
The purpose of this task is to assess customer infrastructure for the needs of
the data migration process. As a result the project team learns about
available tools and identifies any gaps/requirements to acquire tools to
support the migration process.
The purpose of this task is to assess risk for the data migration activities. The
risk assessment focuses on organization, technical risk, data quality risk and
other risks that may impact the data migration activities. During this task the
team prepares mitigation strategies for the individual risk items in the risk
register.
The purpose of this activity to collect input needed for the Data Migration
Approach and Strategy document, in a format suitable for both
communication purpose as well as for formal sign-off purpose.
The purpose of the technical requirements and design deliverable is to

provide the project with a specification of the target solution from a software
component standpoint. This document is intended to serve as a reference
for the rest of the project team during the Business Blueprint phase.
Optional
Included in this deliverable is the solution landscape deployment plan, which
is a high level description of the overall system landscape approach to be
used for the implementation project.
The purpose of this task is to outline the software components and the
design of the future solution landscape.
The purpose of this task is to describe the concept of how the solution in
scope will be deployed.
The purpose of the interface inventory deliverable is to preliminarily identify
the external systems, applications, and business objects or transactions that
must be integrated with the SAP solution to realize the objectives of the
project
The purpose of this task is to collect necessary information for the interface
inventory document.
The purpose of the initial hardware sizing proposal is to begin the process of
assessing the hardware infrastructure requirements.
The purpose of this task is to completed sizing estimates for the Solution
Manager system and Production and non-Production environments.
The purpose of the project support tools and system setup deliverable is to
establish the basic tools and processes necessary to support the project.
One of the most vital project tools is the SAP Solution Manager, the
centerpiece of SAP’s Application Lifecycle Management tools. The SAP
Solution Manager provides a central point of access for a variety of essential
project support functions, including:
· Solution Implementation – the identification, adaptation, and
implementation of new and enhanced business scenarios. Optional
· Solution Documentation – centralized documentation repository
ensuring the relationship of business process definitions with technical
configuration decisions.
· Change Control Management – synchronized deployment of
application configuration with integrated project control and quality
management.
In addition, customer-specific project management and documentation tools
may require installation and distribution to project team members.
The purpose of this task is to validate all technical system requirements for
delivery of the service or project. The objective is to ensure that all required
technical requirements have been satisfied and work can be performed by
the team.
The purpose of this task is to validate all functional requirements for delivery
of the service or project. The objective is to ensure that all required functional
requirements have been satisfied and work can be performed by the team.
The purpose of this task is to validate that customer has SAP Solution
Manager installed and setup.
The purpose of this task is to validate and ensure a proper Solution Manager
setup.
The purpose of this task is to ensure that the business process structure in
SolMan is supporting the solution documentation and all continued project
activities in the coming phases (business process management, value
management, configuration & development, test, training and cut over).
The objective of this task is to setup project logistics, systems and

infrastructure that will support delivery of the project. This may include setup
of computers, setup of project team room, telephony, etc.
The purpose of this task is to install SAP GUI on project team computers.
The objective of this task is to validate that the remote connection to SAP is
working and connection can be established. This is both for the SAPGUI as
well as Web Access.
The objective of this task is to prepare for activation of the SAP Best
Practices. This consists of reviewing the Best Practice technical and
functional requirements and ensuring that the target system is on the correct
release and support package level, that all required SAP notes have been
applied, etc.
The purpose of this task is to install pre-determined solution components

The objective of this task is to perform check of the installation of the service
pre-configuration, settings and objects
The objective of this task is to review the completeness of the installation
check and completion of the knowledge transfer
The purpose of this task is to prepare authorization roles in the systems for
the project team
The purpose of this task is the initial set up of all relevant testing tools (the
actual configuration will happen during Business Blueprint)
The purpose of the phase closure and sign-off deliverable is to:
· Ensure that all required deliverables from this phase and the project
are complete and accurate, and close any outstanding issues
· Identify lessons learned during the phase to prepare for formal project
closure
· Capture customer feedback and potential Customer References
The purpose of this task is to collect knowledge assets and lessons learned
at the end of each phase of the project that can be reused later by other
projects. Collecting documents, experiences, project highlights and lessons
Optional
learned throughout the duration of the project can help to facilitate the
project by providing quick access and insights into key deliverables from
earlier stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a
quality check at critical stages of the project. Project Quality Gates are an
integral part of SAP’s Quality Built In approach for SAP primed, partner or
client led projects. The objectives of the Project Quality Gate are:
· To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customer’s
satisfaction
· To enable project management to continuously communicate the
process and build quality directly into the project
· To provide a tool to effectively manage project expectations and
monitor customer satisfaction
The purpose of this task is to execute a Project Management Review that

provides a proactive quality assurance review, with an impartial analysis of
all aspects of the project – across all project management disciplines,
enabling early detection of project issues with actionable recommendations.

This milestone signifies transition for Project Startup activities to Design,
Solution Design Validation activities
The purpose of this phase is to create/update the business blueprint,

which is a detailed process-oriented and technical documentation of
the results gathered during requirements and design workshops or
based on validation of predefined solution or service description.
A blueprint consists of multiple documents illustrating how the
company intends to run its business using SAP solutions.
The purpose of the phase initiation deliverable is to formally recognize that a

new project phase starts.
The purpose of this task is to confirm resource availability for the particular
Mandatory
phase.
The purpose of this task is to ensure the involvement of the team and other
key resources and their commitment to the project schedule. The meeting is
also used to examine the approach for the specific project phase.

The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change Mandatory
management process.
costs etc.
The purpose of this task is to ensure that each contract is closed by verifying
that all work specified in the contractual arrangement was completed, and Mandatory
that all defined deliverables were accepted.
The purpose of the stakeholder analysis deliverable is to detect the level of
acceptance or the general attitude regarding the project on the part of all key
stakeholders, as well as the ways they can influence the project. Execute an Optional
analysis of current state ‘as-is’ and future state ‘to-be’ business process
maps to quantify the delta ‘transition gap’
The purpose of this task is to re-visit the stakeholder identification results,
determine the detailed level of change impacts for the identified stakeholder
(groups) in order to create transparency about the organizational and system
changes.
The purpose of this task is to identify key users needed for the different
areas (depending on the scope of this project).
The purpose of the Change impact analysis deliverable is to ensure that the
organizational and technical changes in business processes have been
Optional
identified and documented by comparing the as-is and the to-be business
processes.
The purpose of this task is to validate the chosen approach with key
stakeholders for the continued project execution.
The purpose of this task is to define the baseline for where organizational
change management starts and against which progress and success of the Optional
OCM-activities are measured.
The purpose of the communication plan deliverable is to summarize all
planned communication measures and to help identify the dependencies
among various activities. The communication plan is aligned to the overall
OCM roadmap and addresses mainly external communication to
stakeholders, key users, end users, and suppliers.
The purpose of this task is to provide a set of key messages to describe the
benefit of the SAP solution and the change impact for every stakeholder
group. Due to the individual goals and interests of stakeholder groups, it is
necessary to define specific key messages for each stakeholder group, for
example to specify what to tell particular employees.
The purpose of this task is to define the communication strategy for the
change management activities.
The purpose of the End User Training Strategy and Plan deliverable is to
develop a high level training plan that provides the recommended approach
Mandatory
and corresponding activities to prepare the end users for using the new
system.
The purpose of this task is to perform an analysis of the end-user population

to be trained and determine where the skills levels, knowledge gaps, and
training requirements are located. This analysis contains the key customer
information for definition of the end-user training and documentation of high-
level project plan recommendations, proposals, and preliminary strategies.
The purpose of this task is to develop a working document to track evolution

of documents and progress of processes for all education aspects of the Optional
project
The purpose of the Project Team Training deliverable is to ensure that the
project team is informed about the way of working during the Blueprint Phase
including usage of Solution Manager for Solution Documentation.
The purpose of this task is to clarify deliverables and expectations,

methodology, and tools. Typically two to three days should be reserved for
this training. Once the team members or at minimum the team leads are
identified, they will be brought on board with this ramp-up training before the
phase kickoff meeting. The blueprint ramp-up deliverable:
· Sets project team expectations and blueprint deliverables
· Provides guidance for blueprinting workshops and relevant enabling
tools
· Introduces blueprint quality assurance and its acceptance criteria
· Prepares for essential blueprinting skills, such as workshop facilitation,
requirements gathering, and process modeling
· Fosters teamwork within project teams
The purpose of this task is to train the key users for the solution in scope
(pre-defined content)
The purpose of the end user training content deliverable is to create a

curriculum plan that covers the skills that end users will need to possess to
use the system. This document will be refined throughout the project.
The purpose of this task is to validate and adapt the standard end user
training material being pre-delivered within the solution. (delivery model
3&4).
The purpose of this task is to prepare training content in the system
environment being set up for the project.
The purpose of solution validation / fit-gap analysis deliverable is to validate

the predefined scenarios, processes and enhancements; identify potential
gaps between delivered product and customer requirements. The deliverable
only captures requirements for gaps. It follows an iterative approach. Existing
documentation and models can be altered, changes have to be marked and
documented in Solution Manager.
This task validates predefined general settings and that these are still
relevant for the scope of the implementation, such as organizational
structures or customer or material masters, and to identify potential gap
between delivered product and customer requirements.esign a solution for
these business objects within the SAP solution. These objects are
associated to processes and reflected in applications so understanding these
relationships is essential for overall integration and cross-process integrity.
This task validates predefined scenario solution documentation, identifies

potential gap between delivered product and customer requirements. Only
requirements for gap are being captured. It follows an iterative approach.
Existing documentation and models can be altered, changes have to be
marked and documented in Solution Manager
This task validates predefined process solution documentation, identifies
potential gap between delivered product and customer requirements. Only
requirements for gap are being captured. It follows an iterative approach.
Existing documentation and models can be altered, changes have to be
marked and documented in Solution Manager.
This task validates the pre-defined RICEFW Objects (reports, forms etc.).
Additional customization and enhancements should be kept to a minimum.
This purpose of this task is to analyze identified gaps and additional

requirements and determine effort (and duration) for the realization phase.
The purpose of business objects modeling (cross-process view) is to identify

business objects that are relevant for the scope of the implementation, such
as organizational structures or customer or material masters, and to design a
solution for these business objects within the SAP solution. Business objects
are associated to processes and reflected in applications. Understanding
these relationships is essential for overall integration and cross-process
integrity.
Business object modeling may also build the foundation for service
modeling, if the project is implementing a service-oriented architecture
(SOA).
The purpose of this task is to capture the design and requirements of the
organizational structure. This should reflect multiple views of a company i.e.
Legal, Fiscal, Functional, Product-oriented, Regional and geographical,
Customer-group, Distribution-channels, Purchasing-channels etc. depending Mandatory
on the process scope.
It is best to store all organizational structure deliverables in the process
hierarchy in SAP Solution Manager.
The purpose of General Settings and Master Data is a detailed description of

design and maintenance processes for general settings and master data.
This includes definition of business rules and ownership.
General Settings and Master Data Design also addresses cross-application

general settings and master data for e.g. countries, languages, currencies,
organizational units, units of measure, number ranges, product hierarchies,
material types and shipment rules.
The purpose of the user role concept is to describe all relevant end-user
roles and corresponding responsibilities from a business point of view. This
includes User role concept overview, User role documents - one per role, Mandatory
Consistent user role name and assignment to defined business organization
model, Corresponding SAP default roles, Mapping rules etc.
The purpose of this task is to define a logical data model for master or
transactional data relevant to the implementation scope across the
application landscape, including both legacy and SAP components.
This will help manage the data relationships and align interfaces correctly.
The purpose of the Detailed Design - Business Scenarios deliverable is the
continuation of process decomposition started in project preparation. This
includes documentation of requirements, solution design for the scenarios Mandatory
and processes. This information is populated in the business process
hierarchy in SAP Solution Manager.
This task identifies requirements on a scenario level that will be refined,
iteratively, during the detailed Business process design. Documentation is
stored in Business Process Hierarchy in Solution Manager.
The purpose of this task is to continue collecting input and finalize the
Scenario Design Document, in a format suitable for both communication
purpose as well as for formal sign-off purpose. The documented business
scenario provides an understanding of the essential processes at the
scenario level (PL1-2). It also builds the foundation for the business blueprint
phase where process levels 3–5 are defined.
The purpose of this deliverable is to design, in detail, the to-be business
process down to activity level (PL 3-5) and to describe gaps where the Mandatory
standard solution does not cover all required functionalities.
This task identifies requirements on a process level that will be refined,
iteratively, during the detailed Business process design. Documentation is
stored in Business Process Hierarchy in Solution Manager.
The purpose of this task is to continue collecting input and finalize the
Business Process Design Document, in a format suitable for both
communication purpose as well as for formal sign-off purpose. The
document provides details of the to-be business process down to activity
level (PL 3-5) and describes the gaps where the standard solution does not
cover all required functionalities.
The purpose of this task is to demonstrate standard functionality of the SAP

solution to the Product Owner and Key Users in order to solicit input and
gain acceptance for the standard feature. In case standard functionality
needs to be enhanced product owner captures this requirement in product
backlog in the form of user story.
Features that are complex or time consuming to configure in the system can
be presented in a visualization tool like SAP Visualization by iRise to solicit
input and gain acceptance of the feature requirements.
The purpose of Value Realization is to establish the sustainable mechanisms

to monitor and controls the predefined KPI's and PPI's of the to-be process Optional
and/or process changes.
The purpose of this task is to design the Value Dashboard by specifying the
KPI's and PPI's and how these are monitored and controlled during project
execution and post Go-Live.
The purpose of this deliverable is to specify and detail how to realize the
solution, both Core Configuration and identified gaps and core
enhancements needed to complement standard functionality, in order to fulfill
Mandatory
business requirements. These RICEFW objects are based on process
requirements, and they are specified in business process and solution
design documents.
The purpose of this task is to complete the documentation for identified core
configuration objects related to business processes.
The purpose of this task is to complete the documentation for additionally

identified configuration objects related to business processes.
The purpose of this task is to complete the documentation for identified
RICEFW objects.
These objects are classified as:
· Reports that have to be designed or adjusted
· Interfaces that need to be developed
· Conversions (mostly related to master data)
· Enhancements that need to be performed
· Forms for print-out or other purposes
· Workflows that need to be implemented or designed
The purpose of this task is to prepare functional design document for all SOA
and 3rd party applications / solution enhancements or extensions.
The purpose of the visualizations deliverable is to ensure that the defined
processes are exemplified and easier to understand and judge by the project
team members, key users and stakeholders.
The purpose of this task is to provide visualization for identified configuration
and/or RICEFW objects.
Visualization complement functional specifications, help to verify the solution
design early and serve as a collaboration tool for feedback and requirements
identification.
The purpose of this task is to initiate the work to document the business
process procedure, beginning with the pre-define process scope. This
document will be completed during the realization phase.
The purpose of the legacy data migration deliverables is to develop the
designs, plans, and procedures to support the migration of legacy data Mandatory
during the implementation of the SAP applications.
The purpose of this task is to ensure that defined processes and procedures
needed to ensure correct quality and handling of master data are operational
in the organization.
This task ensures that provided master data for Assemble to order and/or
Industrialized content, can be utilized by the project.
The purpose of this task is to conduct a detailed analysis of legacy data in
order to determine:
· The availability and quality of existing data to support the SAP
Mandatory
applications to be implemented
· The complexities and risks associated with the data and migration
process
The purpose of this task is to design the specific architecture, programs,
processes, and tasks required to support the extraction, validation,
harmonization, enrichment, and cleansing of the legacy data.
The purpose of Manual Data Migration design is to develop the approach for
manually bringing legacy data into the SAP database when automated
programs are not available or the data volume does not justify the
investment in developing such programs.
The purpose of the data quality plan is to define the metrics that track and
monitor data quality during the data migration process.
The purpose of data Security Design is to identify and develop the necessary
architectural designs and plans to support the security requirements.
The purpose of legacy data archive is to make legacy master data not
considered currently active available for reference in a format compatible
with the master data formats of the SAP solution.
The purpose of this task is to establish the framework for legacy data
archiving, meaning the planning for usage of legacy-data archive objects, the
legacy archive specifications, and data retention rules for master-data
archive objects.
The purpose of the Technical Solution Design deliverable is to provide a
detailed technical and integration design of the solution to be implemented,
accounting for all decisions made during the Business Blueprint phase
including business process definitions, integration with external systems, and
physical server deployment.
The purpose of this task is to complete the technical infrastructure

specification which provides a technical description of the entire technology
landscape from a physical standpoint, showing where each of the SAP and
non-SAP systems are installed, and the physical or virtual servers assigned
to each system along with their specifications
The purpose of this deliverable is to ensure proper set up of a Roles and
Authorizations procedure and approach for the project.
The purpose of this task is to document the authorization requirements at the
level of business scenario and process, to evaluate chosen authorizations
Mandatory
concepts against SAP standards and to determine a feasible implementation
approach.
The purpose of the development environment deliverable is to install a
viable, correctly configured technical development environment that is Mandatory
available for use by the project team to begin the realization phase.
The purpose of this task is to install SAP components needed for the
realization of project scope.
The purpose of this task is to upgrade SAP components needed for the
This task ensures that all solution documentation is made available for the
project team. Preferably the repository for this should be Solution Manager.
This task deals with the installation of 3rd party products needed to realize
scope of the project.
The purpose of this task is to set up users in the development environment.
The objective of this task is to perform any remaining manual configuration
changes in the Development environment.
The objective of this task is to validate the assignment of user role profiles /
authorizations to the test users in the development landscape.
Prepare master data required for a business process
The purpose of this deliverable is to create project related test framework,

which gets content input from the existing Test Policy (1.16.), to build a
central foundation around the taken approach (e.g. Test Approach and
Methodology, Test Standards and Guidelines, Test Case Development,
Defect Management, Reporting and Analysis, Roles and Responsibilities) Mandatory
on functional testing (unit-, string-, integration-, scenario-, user acceptance,
regression testing etc.) and performance testing. The actual test strategy
documentation for functional testing and performance testing have to be
separated.
The objective of this task is to create a centralized document for functional-
and performance testing, which incorporates standard and procedures which
will be used for the detailed test plan preparation / documentation.
Determine overall test data approach by aligning with the overall data
migration approach. The test data approach will be documented as part of
the testing strategy.
The objective of this task is to communicate the testing strategy (functional

and performance) to the customer project team and validate it.
Purpose of this task is to start the requirements gathering process (e.g. KPI
and benchmarks). This activity is aligned with the documented overall
performance test strategy and will continue until the finalization of the
performance test concept
Mandatory
closure
Optional
satisfaction
The purpose of this task is to execute a Project Management Review that

provides a proactive quality assurance review, with an impartial analysis of
all aspects of the project – across all project management disciplines,
enabling early detection of project issues with actionable recommendations.
The purpose of this task is to execute a Design Review of SAP Solution

service that provides a proactive quality assurance review of the design of
the SAP solution which is being implemented. It delivers an impartial analysis
of all aspects of the solution design – across all relevant design perspectives
– and leads to an early detection of potential solution risks and offers
actionable risk mitigation recommendations.
that all work specified in the contractual arrangement was completed, and
This milestone signifies completion of Design activities and transition to Build
activities
The purpose of the realization phase is to implement the business

scenario and process requirements based on the business blueprint
completed in the previous phase.
Objectives of this phase include:

· Establishment of the solution landscape
· Implementation of the final solution in the development
environment
· Overall testing of the solution within the quality environment
· Release of the solution for production (live) operations
· Delivery of training materials
· Preparation for data migration and data archiving
· Identification of value delivery concepts
· Performance testing

Mandatory
phase.

management process.
costs etc.
The purpose of Organizational Alignment is to ensure a smooth transition
process towards the new way of working. This includes the alignment of
roles and responsibilities and activities to ensure that all employees are fully
aligned to the goals of the project and organization.
The purpose of this task is to use the results from previous change impact
analysis and the role mapping information (mapping of new business user
Optional
roles to existing roles and organizational structure) and determine an
appropriate transition approach for the business.
The purpose of this task is to get to get complex organizational feedback
regarding the progress and acceptance of the project from the customer’s
view.
The purpose of this task is update communication plan and execute
accordingly
The purpose of this deliverable is to determine the potential issues with the
SAP education strategy and solution before they impact the quality of the
SAP software deployment.
The purpose of this task is to capture feedback on both the training strategy
and approach, determine issues and propose resolutions for identified
issues.
The purpose of the Knowledge Transfer deliverable is to ensure that key
users get a good understanding of the implemented solution.
In this task the SAP project team prepares for training and enablement of the
customer project team to understand the solution and how it is implemented
in their area, as well as trains the key users as defined in the statement of
work.
The purpose of this task is to execute knowledge transfer by means of
solution walkthrough sessions, system demos on scenario and/or process
level, functional reviews etc., etc.
The purpose of the deliverable End User Training Content Enabled is to
ensure availability of end user training material, training environment, Optional
logistics infrastructure and skilled instructors.
This task ensures a consistent appearance of the training materials and

documentation by providing the development team with standard templates.
The purpose of this task is to ensure that the training environment is

Optional
correctly populated with correct data for training.
The purpose of this task is to provide a detailed outline of presentations and
activities that serve to educate and prepare the trainers scheduled to instruct
end-user training classes
The purpose of this task is to prepare the execution of end-user training by
mapping end users to appropriate training courses, developing a training Optional
schedule and logistics plan, and inviting end users to courses
The purpose of the Configured General Settings and Organizational

Structure deliverable is to complete and document the initial configuration of
Mandatory
the system on the basis of the decisions made in the business blueprint
phase.
The purpose of this task is to implement the configuration related to general

settings, and to document this in Solution Manager.
The purpose of this task is to implement the configuration related to
organizational structure, and to document this in Solution Manager.
The purpose of the Configured Master Data Objects 1-n deliverable is to
configure the master data in the SAP software system according to the Mandatory
business process requirements specified in the business blueprint phase.
The purpose of this task is to prepare master data required for all business
processes' unit and string tests in DEV.
The purpose of this task is to complete configuration of master data in the
system
The purpose of the Core Configuration and Documentation deliverable is to

ensure that the configuration is implemented, tested and documented. Mandatory
The purpose of this task is to implement the Core Configuration, write valid
test cases and to document this in Solution Manager.
The purpose of this task is to prepare the test cases
The purpose of this task is to prepare the test cases
The purpose of this task is to perform unit test for the configuration Optional
The objective of this task is to resolve any issues identified during the
Business Process Unit Test. It is crucial that the issues are re-tested by users
that reported them (or designated re-testers) and that they are confirmed.
The purpose of this task is to perform string test for the configuration Optional
Process String Test. It is crucial that the issues are re-tested by users that
reported them (or designated re-testers) and that they are confirmed.
The purpose of the Delta Configuration deliverable is to ensure that the

configuration is implemented, tested and documented. Mandatory
The purpose of this task is to implement the Delta Configuration, write valid
test cases and to document this in Solution Manager.
The objective of this task is to develop process documentation for any
changed processes or for any new processes added to the standard.
The objective of this task is to develop process test cases for any changed
processes or for any new processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration Optional
The objective of this task is to resolve any issues identified during the Unit
and String Test. It is crucial that the issues are re-tested by users that
The purpose of this deliverable is to develop and test the RICEFW objects.
Mandatory
Documentation to be stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the
functional specification,
The purpose of this task is to document the RICEFW object information in a
technical specification and define the appropriate test case(s).
Documentation is stored in Solution Manager.
The purpose of this task is to perform unit and string test of the
Optional
developments.
RICEFW object(s) Test. It is crucial that the issues are re-tested by users that
The purpose of this task is to perform final code review of the development
objects and confirm readiness for transport into QAS.
The purpose of the SOA / composite application development deliverable is

to implement and document the enterprise services, including developing
and realizing the composite application. The technical design and
specifications from the business blueprint phase serve as input.
The purpose of this task is to develop the Enterprise Service according to the
functional specification, document this in a technical specification and define
the appropriate test case(s). Documentation is stored in Solution Manager.
The purpose of this task is to develop the Composite and/or Mobile

Application according to the functional specification, document this in a
technical specification and define the appropriate test case(s).
Documentation is stored in Solution Manager.
The purpose of this task is to perform final code review of the development
objects and confirm readiness for transport into QAS.
The purpose of the Business Process Procedures deliverable is to provide
the basis for end-user training, end-user training documentation and test
case creation. The procedures may also be used by security to develop roles
and authorizations.
The purpose of this task is to validate and complete Business Process
Procedures from the blueprint phase.
The purpose of this task is to validate and complete Business Process
Procedures from the blueprint phase.
The purpose of the value audit deliverable during the realization phase is to
monitor and control the implementation of key process changes and value
Optional
enablers, as well as to ensure the design and implementation of the Value
Dashboard for KPI tracking purposes.
The purpose of this task is to perform value audit according to defined Value
Dashboard, and provide mitigation strategies for identified risks that could
jeopardize the value identified during the business case development.
The purpose of this deliverable is to provide evidence that the scenarios

designed can be supported by the solution implemented.
The purpose of this task is to identify and document applicable test case(s)
for the scenario.
The purpose of this task is to perform scenario test. Optional
scenario testing. It is crucial that the issues are re-tested by users that
The purpose of the quality assurance infrastructure and environment design

and setup deliverable is to install a viable, correctly configured technical QA
Mandatory
environment that is available for use by the project team to perform QA
testing.
The purpose of this task is to install SAP components needed for the
The purpose of this task is to upgrade SAP components needed for the
The purpose of this task is to build the quality assurance (QA) environment
with changes that have been unit-tested and released from the development
environment.
The purpose of this task is to set up users in the Quality Assurance

environment.
processes in QAS.
The objective of this task is to perform any remaining manual configuration
changes in the Quality Assurance environment.
This milestone signifies completion of Build activities and transition to

Integration Testing, User Acceptance Testing and Non-Functional Testing
The purpose of the preliminary cutover plan deliverable is to document the

strategy, scope and timelines for moving from the as-is solution to the to-be Mandatory
solution and the hyper care period immediately following go-live.
The purpose of this task is to assess to what level the organization is

Optional
prepared for the cut over/transition
This purpose of this task is to check to what extent the support organization
is operational and ready for cut over
This task checks that proper governance of master data quality is defined.
The purpose of the preliminary cutover plan task is to document the strategy,
scope and timelines for moving from the as-is solution to the to-be solution
and the hyper care period immediately following go-live. This includes
documenting activities such as the transfer of data from the legacy systems
to the SAP software production system, setting up and initializing the
production system, closing the legacy systems, manually entering certain
data in the new system, setting up and verifying interface connections,
importing transports and all manual configurations.
The purpose of the review of the preliminary cutover plan is to validate the
plan for completeness, dependencies, timing and other constraints. At the
end of the review the project team will have understanding of necessary
adjustments to the preliminary cutover plan.
The purpose of this task is to refine the preliminary cutover plan based on
information the project team learned in the cutover plan review with
customer.
The purpose of Approved Integration Test is to ensure functional correctness.
It test the integration of SAP solutions with non-SAP applications and
Mandatory
interfaces and can be executed in an iterative manner.
The purpose of this task is to define and document integration test cases,
end-to-end customer business process scenarios, according to the test plan.
Test plans and test case documentation is stored in Solution Manager.
The purpose of this task is to document the integration test case outlined in
the integration test plan
The objective of this task is to perform the Integration test according to
previously defined plan. During the test all issues must be logged and
documented in the system for traceability purpose.
Integration Test. It is crucial that the issues are re-tested by users that
The purpose of this task is to obtain customer approval (sign-off) of the
integration test.
The purpose of the legacy data migration deliverable is to develop,

implement, and test the data migration programs and processes defined in
the business blueprint phase. This activity consists of iterative development
and testing cycles focused on the analysis of data, refinement of business
rules, and deployment of migration programs and processes designed to
move, cleanse, transform, and enrich legacy data required to support the Mandatory
various test cycles and ultimately the production cutover. The test cycles
enable the migration team to improve data quality to an acceptable
production level, develop a detailed cutover sequencing plan, and exercise
data reconciliation and validation processes required to support the
production cutover.
The purpose of this task is develop the specific architecture, programs, and
processes that support the extraction, validation, harmonization, enrichment,
and cleansing of the legacy data.
The purpose of this task is to execute and validate the manual conversion as
described in the manual data migration approach
The purpose of this task is to visualize the data quality metrics defined in the
data quality plan
The purpose of this task is to load the cleansed legacy data into the SAP
software target structures using a standard SAP load utility such as LSMW.
The purpose of this task is to obtain the results of the various test cycles so
the team can monitor the accuracy and efficiency of the data migration Mandatory
solution.
The purpose of this task is to provide one final assessment at the end of the
Mandatory
realization phase to report on the quality of the converted legacy data
The purpose of this deliverable is to execute the User acceptance test (UAT).
This is the last test cycle of an SAP solution implementation and is an Mandatory
essential part of gaining end-user acceptance of the software system.
The purpose of this task is to define and document UAT test cases according
to the test plan. Test plans and test case documentation is stored in Solution
Manager
The purpose oft his task is to adapt testing tools if needed (e.g. add of field
values and additional security roles) and train project team members, as
usually the test team gets extended before and during the UAT test cycle.
The purpose of this task is to document the integration test case outlined in
the UAT test plan
The objective of this task is to perform the End User Acceptance test
according to previously defined plan. During the test all issues must be
logged and documented in the system for traceability purpose.
The objective of this task is to resolve any issues identified during the User
Acceptance Test. It is crucial that the issues are re-tested by users that Mandatory
The purpose of this task is to execute the testing, document the results and
obtain customer approval (sign-off)
The purpose of the SAP data archiving deliverable is to provide a method to

check, remove, and store data that has completed its lifecycle within the
solution. Data that meets the check criteria of data retention rules and is no
longer actively used in the system can be archived and deleted. Storage of
the data is a secondary process to enable data that has been archived and
deleted to still be viewed and reported on even though the data is no longer
stored on the transactional system.
The purpose of this task is to identify legal and business retention

requirements needed in prier to establish the baseline for data arched and
removal plan.
The purpose of this task is to develop the data archive plan that outlines the
planning for data archiving of the business objects at the customer site.
The purpose of this task is to develop the data archive storage plan needed
for the execution of each data archive run and creates the indexes for each
archive execution.
The purpose of this task is to test the data archive implementation execution
in QAS.
The purpose of the production infrastructure and environment design and
setup deliverable is to install a viable, correctly configured technical
Mandatory
production environment to support productive operations of the delivered
solution.
The purpose of this task is to install and set up the production environment.
The purpose of this task is to upgrade the production environment.
The purpose of this task is to build the production (PRD) environment with
changes that have been tested and released from the quality assurance
(QA) environment.
The purpose of this task is to set up users in the production environment.

The purpose of this task is to ensure that appropriate master data is
available for testing in the production environment (system test).
processes in PRD.
The purpose of this task is to perform any remaining manual configuration
changes in the production environment.
The purpose of this deliverable is to execute the setup of Availability and

Optional
Continuity Management (ACM)
The purpose of this task is to define the approach and plan for Availability
and Continuity Management.
The purpose of this task is to set and execute the identified failure scenarios.
The purpose of this task is to obtain the results from the failover scenario
execution and determine the appropriate mitigation actions for the test
findings.
The purpose of planned Performance and System Test is to checks the
entire system, consisting of databases, applications servers, front ends,
Mandatory
printers etc. The performance test measures the throughput and response
times of the system.
The task defines and documents the identified test cases related to system
and performance test. Outcome is documented in a test plan.
The task defines and documents the identified test cases related to system
and performance test. Outcome is documented in a test plan.
The purpose of this task is to document the test case outlined in the test plan
The purpose of this task is to execute the performance tests and present the
findings for these tests. The outcome should be formally approved by the
customer.
The objective of this task is to resolve issues identified during the
performance or load testing. Upon resolution the issues need to be re-tested
and confirmed by responsible testers.
The purpose of this task is to obtain customer approval (sign-off)
The purpose of this service is to support the start of production of an SAP
Solution. During this service, SAP service engineers check the solution for
Optional
potential risks and give recommendations ensuring optimal performance and
system availability for core business processes.
The purpose of this task is to perform the first session of the SAP GoingLive
Check.
The service consiste of two sessions - Analysis and Verification, and
includes:
- Verification of the technical capabilities of the production environment
(sizing plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components
and Plug-Ins
The purpose of the System User Roles and Authorization Administration

Optional
deliverable is to establish an effective operation processes for security
The purpose of this task is to set-up, document and execute the

administrative procedure for Roles and Authorizations.
The purpose of the technical operations and handover strategy deliverable is
to update refine two prior deliverables from the Business Blueprint phase,
Optional
and prepare a strategy to hand off operations of the solution landscape to
the post-production support organization.
The purpose of this task is to ensure that proper staffing(people and
competence) is in place for the support org/team
The purpose of this task is to ensure that adequate support processes are in
place for the Go Live phase and beyond.
This task describes the considerations that are required to recognize and
solve critical situations during business process operation.
The primary goal of the SAP Technical Integration Check service is to identify
technical integration issues related to the core business processes, the
Optional
solution landscape, and the interfaces to SAP and non-SAP software
systems.
The primary goal of the SAP Technical Integration Check service is to identify
technical integration issues related to the core business processes, the
solution landscape, and the interfaces to SAP and non-SAP software
systems. The check assesses your project from the technical perspective
and generates a list of actions that you should take to ensure maximum
availability and performance as well as smooth operations with your solution
after going live.

Mandatory
closure
Optional
satisfaction
The purpose of Project Management Review is to provide a proactive quality

assurance review, with an impartial analysis of all aspects of the project –
across all project management disciplines, enabling early detection of project
issues with actionable recommendations.
The purpose of this task is to execute a Design Review of SAP Solution
service that provides a proactive quality assurance review of the design of
the SAP solution which is being implemented. It delivers an impartial analysis
of all aspects of the solution design – across all relevant design perspectives
– and leads to an early detection of potential solution risks and offers
actionable risk mitigation recommendations.
This milestone concludes testing activities and start of deployment of the
functionality to Production Environment
The purpose of the final preparation phase is to finalize readiness of

the solution and its supporting tools and processes for production go
live. This includes, but is not limited to, system tests, end-user training,
system management, and cutover activities (including data migration).
The phase deliverables also serve to enable the resolution of all crucial
open issues. On successful completion of this phase, the business is
ready to run the live SAP software system.

Mandatory
phase.

management process.
costs etc.
The purpose of this survey is to take the pulse of the organization, prior to
go-live, to determine the general comfort level with the upcoming changes. If
that comfort level is not there, it is critical to determine where additional OCM
work needs to be focused. In addition the check of production support
readiness is to ensure that the resources and processes are in place to
support the solution after cutover.
The purpose of this task is to validate the outcome of the role mapping and
change impact analysis. This is done with the impacted business Optional
stakeholders in order to gain sponsors approval.
The purpose of this task is to ensure the customer establishes the means to
Optional
manage their data in an integrated environment.
This task provide a single defined support approach for monitoring and
measuring the customer’s day-to-day support operations. The following four
topics needs to be covered:
- Exception Handling and Business Process and Interface Monitoring
- Data Volume Management Optional
- Job Scheduling Management
- Transactional Consistency and Data Integrity
This task describes how all SAP technologies can be administered to run a
customer solution efficiently. The execution is mainly done locally but can be Optional
triggered and managed from a central administration system.
The task ensure that the customer establishes the means to manage
Optional
security, roles and authorizations in their productive environment.
The purpose of this task is to extract the knowledge about the scope,
customizations, and business processes of the customer’s production Optional
environment and transfer that knowledge to a long-term SAP support center
The purpose of the EU training delivery and readiness checklist is to provide

a checklist summarizing end-user training delivery to ensure readiness for
adoption of the solution. In the checklist, items governing training delivery,
communications, and future planning clarify the status of all aspects of the
training initiative.
The purpose of this task is to prepare the training delivery.

The objective of this task is to deliver end user training to identified end user
groups according to the previously developed training schedule.
The purpose of this task is to capture feedback on both the training session
Optional
and the trainer delivering the material
This task checks how prepared the people in the organization are with
Optional
regards to the identified changes and received EU training.
The purpose of this deliverable is to present the findings and

recommendations from the results of technical tests such as disaster
recovery tests, backup and restore tests, and other required technical or
basis-related tests to the customer or project team for final signoff in order to
exit system testing.
The purpose of this task is to prepare and execute the system tests. The
outcome/results should be approved by the customer.
The objective of this task is to resolve issues identified during the system
testing. Upon resolution the issues need to be re-tested and confirmed by
responsible testers.
The purpose of production cutover is to perform the cutover to the production
software and go live. At this point, the organizational, business, functional,
technical, and system aspects of the project are ready to be used in
production.
The purpose of this task is to rehearse or simulate the cutover activities.
During simulation, the main objective is to validate and document the tasks, Mandatory
sequence, and duration of items on the cutover plan.
This task verifies that master data support is set up and process is
Mandatory
operational
The purpose of this task is to complete the Cut Over plan with results
Mandatory
obtained from the Go Live simulations.
The objective of this task is to perform all the cutover preparation activities
remaining to be closed prior to cutover weekend. The detailed cutover plan
contains the complete listing of all pre-cutover activities, their dependencies,
owners, and timing.
This task will confirm that the productive system is ready for Go Live. Optional
The purpose of this task is the loading of production data from legacy
systems into the production environment. Once all preparations and
configurations on both the technical and application levels are completed,
the final productive solution can be set up and data loaded. The solution is
live in a production environment
Purpose of this task is to obtain customer approval (sign-off) Mandatory
Purpose of this task is to hand over the finalized implementation project and
it's content, and set up as a productive solution in SAP Solution Manager. Optional
This provides the basis for the follow up activities in the Run Phase.

Mandatory
closure
Optional
satisfaction

The purpose of this task is to obtain customer approval (sign-off)
This milestone signifies formal transition to production environment.
Production is up and running, cutover sustainment activities, end-user on-
boarding and support are under way.
The purpose of this phase is to provide support for the solution during
the period immediately following production cutover. Exceptional items
such as additional production support, exceptional business
monitoring processes, and extraordinary technical support are planned
and executed in this phase. At the end of the designated extra-care
period, sustaining production support processes planned in final
preparation and executed as part of go-live support become the core
support for continuous improvement in the ongoing solution.

Mandatory
phase.

management process.
costs etc.
The purpose of knowledge support strategy is to provide an approach for
identifying and addressing ongoing learning needs, required knowledge
support, and processes for managing training for all solution users.
The purpose of this task is to define knowledge support strategy is to provide

a strategy for identifying and addressing ongoing learning needs, required
knowledge support, and processes for managing training for all solution
users. Since each user demographic has specific needs, the project needs to
put in place a set of ongoing learning plans and techniques.
The purpose of EU training during go-live support is to ensure that end users
have adopted the solution, knowledge resources are maintained, and Optional
responses to the end-user acceptance survey are positive.
This purpose of this task is to adapt available training material and make it
suitable for End User training.
This task executes the delivery of EU training as well as capturing feedback
on both the training session and the trainer.
The purpose of this task is to capture feedback on both the training session
and the trainer delivering the material
This task checks how prepared the people in the organization are with
regards to the identified changes and received EU training.
The purpose of the production support and transfer to solution deliverable is
to confirm that the resources and processes are in place to support the
ongoing solution and to complete the steps required to close the project and
finish documentation.
The purpose of this task is to verify that the requirements identified in earlier
sessions are met.
The purpose of the production support and transfer to solution deliverable is
to confirm that the resources and processes are in place to support the
Optional
ongoing solution and to complete the steps required to close the project and
The purpose of this task is to implement ongoing production support to the
SAP software system users and to monitor and optimize system
performance.
The purpose of this activity is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.
The objective of this task is to resolve any functional issues identified during
the hyper care period after cutover. It is crucial that the issues are re-tested
and confirmed by users that reported them.
The objective of this task is to resolve any technical issues identified during
the hyper care period after cutover. It is crucial that the issues are re-tested
and confirmed by users that reported them.
The purpose of this task is to ensure knowledge transfer regarding the

scope, customizations, and business processes in the customer’s production Optional
environments to the long-term SAP support center team.
Purpose of this task is to hand over the finalized implementation project and
it's content, and set up as a productive solution in SAP Solution Manager. Optional
This provides the basis for the follow up activities in the Operate Phase.
This milestone signifies formal transition from post production sustainment

support to long term support and operation of the new environment
The purpose of the End User Acceptance Survey deliverable is to ensure the
end-user acceptance, which is a key indicator of success for any SAP
implementation. The success of a project depends on how usable and
beneficial end users perceive the new processes and systems to be after go-
live. One of the key issues is to identify levels of acceptance and analyze
what cause them to vary.
The result of this task will determine the level of acceptance of the
organization and provides information needed for the analysis of what
causes the acceptance levels to vary.
Mandatory
closure
Optional
satisfaction

The purpose of this activity is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.
The purpose of this activity is to document the results of the project, both
regarding achieved objectives, deliverables as well as adherence to
schedule, costs and delivered value.
The purpose of this activity is to formally close the project by obtaining
customer signatures on dedicated deliverables/documents e.g. Project
Quality Gate, Project Closeout Report
This milestone marks official closure of the project
Solution operations are initially set up during the implementation

project. The primary goal of this phase is to further optimize and
automate the operability of the solution. Operability is the ability to
maintain IT systems in a functioning and operating condition,
guaranteeing systems availability and required performance levels to
support the execution of the enterprise’s business operations.
The Operations Maturity Assessment evaluates the SAP customer's support

operations to determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements
for operations and to define what aspects of the operations need to be
adjusted, enhanced or implemented.
The report should detail assessment results and finding, including proposed
actions for how to bridge identified gaps.
Centrally document and relate business processes and technical information
of SAP and non-SAP Solutions ensuring transparency, efficient maintenance
and collaboration
Re-visit result of ALM roadmap workshop from the project preparation,
lessons learned findings from the implementation project and determine if
potential gaps exist for the Solution Documentations area.
Represents the identification, adaptation and implementation of new and
enhanced future-proof business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical
installation from business innovation
Uses the SAP Solution Manager to implement the innovation in the system
landscape

potential gaps exist for the Solution Implementation area.
The template management approach allows customers with multi-site SAP
installations to efficiently manage their business processes across
geographical distances – from initial template definition to template
implementation and template optimization, for example as part of a global
rollout
potential gaps exist for the Template Management area.
Functional and performance testing of SAP-centric business processes to
ensure validated system behavior after software change events
potential gaps exist for the Test Management area.
Workflow-based management of business and technology-driven changes,

with integrated project management and synchronized deployment
capabilities.
Standardized process leading to improved reliability of solution and
minimized risk through segregation of duties and transparency of changes
Efficient solution management – all project and system information is saved
in SAP Solution Manager

potential gaps exist for the Change Control Management area.
Enables a centralized and common incident and issue message processing

in multiple organization levels
Offers a communication channel with all relevant stakeholders of an incident.
The process includes business user, SAP experts@customer, SAP
Service&Support and Partner Support employees.
Is integrated in all ALM processes of SAP Solution Manager, in any SAP
Business Suite solution and could be connected to an Non-SAP Help Desk
application
Includes follow up activities as knowledge research, root cause analysis or
Change Management

potential gaps exist for the Incident Management area.
Represents all capabilities for monitoring, alerting, analysis and
administration of SAP solutions
Allows customers to reduce TCO by predefined content and centralized tools
for all aspects of operations in SAP Solution Manager
Provides End-to-End reporting functionality either out-of-the-box or
individually created by customers

potential gaps exist for the Technical Operations area.
SAP Business Process Integration & Automation Management (BPIAM)
comprises the most important application related operations topics
necessary to ensure the smooth and reliable flow of the core business
processes to meet a company's business requirements.

potential gaps exist for the Process Operations area.
SAP Notes provide a solution for known issues. SAP Notes are usually
applied upon request (e.g. current incident in productive environment,
information from SAP about potential issue (Hot News, Security Notes)).
SAP Notes are collected and released as Support Packages. Support
Packages are applied to SAP solutions to comply with legal requirements or
run on latest technology.

potential gaps exist for the Maintenance Management area.
Is the identification, adaptation and implementation of new and enhanced
business and technical scenarios
Uses the SAP Solution Manager to manage the upgrade project holistically
and effectively end-to-end
Allows SAP customers to better understand and manage the major technical
risks and challenges in an upgrade project, and to make the upgrade project
a “non-event for the business.”

potential gaps exist for the Upgrade Management area.
Q-Gate Key Deliverable Work Stream Accountable Role
_Phase
PM - Project Management
PM - Project Management Project Manager

Project Guideline (incl.
Travel Guideline)
Steering Committee
Definition, Org-Structure, PM - Project Management Project Manager
Roles
Project Charter PM - Project Management
OCM - Organizational
Project Manager
Change Management
Phase Kick Off Meeting PM - Project Management

Scope Statement
Document
Work Breakdown
Structure (WBS)
Project Schedule (incl.

milestones)
Project Budgetplan
(internal & external)
Project Management
Plan(s)
ALM - Application Lifecycle

Management

Technology Architect
Management
Solution Manager Usage

guideline, ALM - Application Lifecycle Business Consultant
Business Process Management
Modeling Standards
Software System
Configuration Standards, ALM - Application Lifecycle Business Consultant
Enhancement and Management
Modification Standards

Application Consultant
Management
Test Management Test Management

ISM - Test Management
Standards Consultant
Change Request and

TSM - Technical Solution
Transport Management Application Consultant
Management
Standards (CTS)
Management
Post Implementation TSM - Technical Solution

Technology Consultant
Service and Support Management

Management

Management

Management
Risk List (internal &

external), Project
Change log, Project
Issues log
Project (Performance)
Report (internal & PM - Project Management Project Manager
external)
OCM Roadmap
Change Management
OCM - Organizational Business Consultant

Change Management
Training - Training
Project Team Training Education Consultant

Training - Training
Plan & Schedule
Training - Training
Education Consultant
Training - Training
Business Process Map BPM - Business Process

Business Process List Management
BPM - Business Process

Management
Management
Management
Management

Management

Management
Value Map VM - Value Management
Business Consultant
VM - Value Management
Business Consultant
Value Audit of Scope VM - Value Management

Management
BPM - Business Process Business Consultant

Management

Management

Management
ISM - Test Management Technology Consultant
ISM - Test Management Project Manager
Data Migration
Approach, Start and DM - Data Migration
Scope
DM - Data Migration Application Consultant
DM - Data Migration Technology Architect
DM - Data Migration Technology Architect

Solution Landscape TSM - Technical Solution

Design Management

Solution Architect
Management
Management

Management

Management
Management

Solution Architect
Management
Proj Support Tools & Sys TSM - Technical Solution

Setup Management
Management

Management

Management
Management

Management

Management

Management

Management

Management

Management
Management
Management
Management
Management
Project (phase) Lessons

Learned (internal)
PM - Project Management Business Manager

_Milestone
_Phase
milestones)
Project Management
Plan(s)

external), Project
Change log, Project
Issues log
external
Stakeholder Analysis OCM - Organizational

(Internal) Change Management

Change Management
OCM - Organizational Education Consultant

Change Management
Organizational Change OCM - Organizational

Management Plan Change Management

Change Management
Business Readiness OCM - Organizational Business Consultant

Approach Change Management
Change Management

Change Management

Change Management
Training Project Plan Training - Training
Training - Training
End User Training and

Documentation Training - Training
Developed
Training - Training
Business Consultant
Training - Training
Training - Training Instructor
Training - Training
Training - Training
Training - Training

Management

Management

Management
Management
BPM - Business Process Integration Development

Management Consultant

Management

Management
Business Blueprint
Documents(Org Application Consultant
Management
Structure)

Management

User Role Document Application Consultant
Management

Management
Solution Documentation
Management

Management

Management

Management

Management

Management

Management
Business Consultant
Development list(incl.
RICEFW, SOA,
Management
Migration)

Management

Management


Management

Management

Management
Data Migration Design /

DM - Data Migration
Plan
Test Cases & Results DM - Data Migration Application Consultant
DA - Data Archiving
DA - Data Archiving Technology Architect

Management

Management

Management
Authorization
Requirements and Technology Consultant
Management
Design

Design Management

Management
Management

Management

Management
Management
Management
Management
Management
Test Strategy Plans &

Results
Delivery of projects
Results
Delivery Acceptance
Protocol

Learned (internal)

_Milestone
_Phase
milestones)
Project Management
Plan(s)

external), Project
Change log, Project
Issues log
external
Change Management

User Role Document
Change Management

Change Management

Change Management
Training - Training
Training - Training
Training - Training
Training - Training Application Consultant

Developed
Training - Training
Training Environment Education Consultant

Training - Training
Population and Testing
Training - Training
End User Training

Training - Training Education Coordinator
Schedule and Logistics
(incl. Process list,
Configuration,
Management
Interfaces,
Developments)

Management
Management
Configuration,
Management
Interfaces,
Developments)

Management
Management
Configuration,
Management
Interfaces,
Developments)

Management
Management
Management
Test cases & Results Application Consultant
Management

Management

Management

Management
Configuration,
Management
Interfaces,
Developments)

Management
Management

Management

Management

Management
Development list(incl.
RICEFW, SOA,
Management
Migration)


Test cases & Results



Management




Management

Management
Management
Business Consultant
ISM - Test Management Application Consultant

Test cases & Results ISM - Test Management Application Consultant

Design Management

Management
Management

Management

Management
Management
_Milestone
CutOver - Cut Over

Production Cutover Plan
Management
Business Readiness OCM - Organizational

Project Manager
Approach Change Management
Project Manager
Change Management
CutOver - Cut Over

Management
CutOver - Cut Over

Project Manager
Management
CutOver - Cut Over

Project Manager
Management
Results

DM - Data Migration
Plan
Test cases & Results DM - Data Migration Application Consultant
Test cases & Results DM - Data Migration Technology Architect
Testplans & Results -

UAT


Regression
DA - Data Archiving
DA - Data Archiving Technology Architect
DA - Data Archiving Application Consultant

Design Management

Management
Management

Management

Management

Management
Failover Environment
Design, Setup and Test
Management
Results
Management
Management

Management
Test Plans & Results ISM - Test Management
Test Management
Consultant

SAP Going Live Check
Management

Management
System User Roles and

Authorization
Administration TSM - Technical Solution
and Management
System Authentication
Management
Management
Technical Operations TSM - Technical Solution
and Handover Strategy Management

Management
Management
Management
Technical Integration CutOver - Cut Over

Check Management
CutOver - Cut Over

Management
Results
Delivery Acceptance
Protocol

Learned (internal)


_Milestone
_Phase
milestones)
Project Management
Plan(s)

external), Project
Change log, Project
Issues log
external
Change Management
Functional/Technical
Requirements and OCM - Organizational Business Consultant
Production Support Change Management
Processes Defined
Master Data Support
Processes Established
Business Process ALM - Application Lifecycle

Operation Management
System Administration ALM - Application Lifecycle

and Control Management
Security / Role and

Authorization Technology Consultant
Management
Management

Transition to Support Technology Consultant
Management
Training - Training

Training - Training
Training Evaluations Training - Training Education Coordinator
End User Training

Delivery and Readiness
Change Management
Checklist

CutOver - Cut Over

Management
CutOver - Cut Over

Testplans & Results Application Consultant
Management

Plan
CutOver - Cut Over
Production Cutover Plan Application Consultant
Management
CutOver - Cut Over

Management
Readiness for Cutover - CutOver - Cut Over

Signoff Management
CutOver - Cut Over

Management
CutOver - Cut Over

Production Cutover Plan Project Manager
Management
Solution Manager
CutOver - Cut Over
Update, Technology Consultant
Management
Results
Delivery Acceptance
Protocol

Learned (internal)
_Milestone
_Phase
milestones)
Project Management
Plan(s)

external), Project
Change log, Project
Issues log
external
Training - Training
Training - Training
Go-Live Training
Training - Training
Sessions
Training - Training
Training - Training

Change Management

Management
CutOver - Cut Over

Management
Support Process
CutOver - Cut Over
Enabled, Governance
Management
Model for Operations
CutOver - Cut Over

Management
CutOver - Cut Over

Project Manager
Management
CutOver - Cut Over

Management
CutOver - Cut Over
Management
Transition to Standard
Support Processes, ALM - Application Lifecycle
System Administration Management
and Control
Solution Manager
Update, Technology Consultant
Management
_Milestone
Change Management

Change Management
Results
Delivery Acceptance
Protocol

Learned (internal)

_Milestone
_Phase
Business Consultant

Management

Management

Management

Management

Management

Management

Management
ALM - Application Lifecycle Test Management

Management

Management

Management

Management

Management

Management

Management

Management
Management

Management

Management

Management
Q-
WBS Gate Q-Gate Key
WBS item title Description
# Relev Deliverable
ant
This phase provides initial planning and
preparation for the project. Although each
project has its own unique objectives,
### Project Preparation scope, and priorities, the deliverables
outlined below assist in completing the
initiation
The purposeandofplanning steps
this project in andeliverable
initiation efficient
and effective manner.
is to formally recognize that a new project
exists. It supports the decision to accept the
project, align stakeholders – such as clients,
customers, and SAP management – around a
###1 Project Initiation project and its scope, provide updated
information for planning, and obtain a
commitment to proceed. It ensures alignment
between SAP, the customer’s strategic
direction, and the satisfaction of operational
Allocate Resources - requirements.
The purpose of phase resources allocation is a
###1###hard booking with confirmation of resource availability for the
resource management particular phase.
Project
The purpose of this activity is to prepare the
Prepare Team Mand Guideline
###1 2 onboarding package for external consultants
Onboarding Document atory (incl. Travel
from SAP and partner companies.
Guideline)
The purpose of this deliverable is to ensure that
###2 Project Governance an efficient management framework is in place
for successful project execution.
The purpose of this task is to determine the
structure and composition of agile teams in
order to optimally setup the project organization
in line with agile principles. It is required to
setup agile teams as cross functional groups
Define Agile Project
###2 1 that consist of SCRUM master, Product Owner
Organization and Roles
and team members. Team size should be 7 +/-
2 members. The cross-functional team needs to
be composed of business analyst, functional
experts, technical experts and testers required
to
Thefully implement
purpose feature
of this task isintoiteration.
complete the
Complete communications management plan. This
###2###communication document outlines the processes required to
management plan ensure timely generation, distribution, storage,
and retrieval
The purpose ofof project information.
this deliverable is to clearly and
explicitly define the objectives of the proposed
project, analyze all possible benefits and
Mand Project
###3 Project Charter quantify benefits in financial terms. This
atory Charter
information and supporting documents align key
stakeholders around the strategic intent of the
project.
The purpose of this activity is to collect all input
required for the project charter and document it
Prepare Project Charter
###3### into a format suitable for both communication
Document
purpose as for formal sign-off purpose, if
possible utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the
###3###Identify Stakeholders correct groupings of stakeholders have been
identified for the project.
The purpose of this task is to build agile
awareness of key stakeholders, secure
Set Stakeholder commitment to adopt standard SAP
###3###Expectations for Agile functionality where possible. It is recommended
Project to conduct informal and formal meetings to set
the expectations and confirm the project
approach with key project stakeholders.
Obtain Project Charter The purpose of this activity is to achieve a
###3###
Sign-off formal sign-off of the project charter.
The purpose of this deliverable is to kick-off the
project/phase and ensure that all needed Mand Phase Kick
###4 Kick-Off Workshop
information is shared with the resources for a atory Off Meeting
The purpose
successful of thisexecution.
project task is to prepare the
kickoff meeting which will helps ensure the
Prepare for Kickoff
###4### involvement of the team and other key
Meeting
resources and their commitment to the project
The purpose of this activity is to gather the
schedule.
whole project team, including all remotely
involved resources, to kick-off the project or
###4###Perform Kickoff Meeting
project phase. The meeting is also used to
examine the approach for the specific project
The
phase.purpose of this deliverable is to facilitate an
initial understanding of the project scope and
associated project-related assumptions and
constraints. The project scope statement
Scope
evolves through the initiation and planning of Mand
###5 Scope Statement Statement
the project and clearly and explicitly defines the atory
Document
deliverables of the proposed project. This
information and supporting documents align key
stakeholders around what the project is going
to
Thedeliver.
purpose of this activity is to collect and
document both process-related as well as
Document Customer
###5### project-/non-process-related customer
Requirements
requirements, which in summary and as
appendix become part of the scope statement
The objective of this task is to review the scope
Review Scope
statement document with the customer project
###5 2 Statement with
manager and key stakeholders in order to
Customer
confirm the scope and obtain approval.
The purpose of this task is to determine all gaps
Determine Gap List and
###5 3 for customer solution, document them formally
Effort Estimation
and estimate effort to cover the identified gaps.
Communicate result of The objective of this task is to present the
fit gap analysis results of fit gap analysis to customer including
###5 4
including effort the effort estimates to cover the identified gaps
estimates as part of the project/service delivery.
breakdown structure (WBS) for the project,
which is a deliverable-oriented, hierarchical
decomposition of the work to be executed by Work
Create Work
the project team to complete the project. It is Mand Breakdown
###5 5 Breakdown Structure
the basis for the organization and coordination atory Structure
and WBS Dictionary
of the project. A WBS consists of WBS (WBS)
elements that describe project tasks and
subtasks to perform within a defined time
The purpose of this activity is to clearly define
the acceptance criteria against which project
deliverables and results are measured that
have been listed in the Scope Statement.
Refine Acceptance
###5 6 These should also be updated in the Project
Criteria
Quality Gate Scorecard. In the context of Agile
projects this translates to the definition of Done
for the backlog items that are being delivered in
the project.
Obtain customer sign Purpose of this task is to obtain customer
###5 7
off for project scope approval (sign-off)
deliverable is to define the work schedule to be
followed, the resources and associated time
commitments required for the project and the
phases of the project. The work breakdown
structure (WBS) serves as the foundation for
the schedule, the deliverables to be produced
and tasks to be performed, as part of the
project. The project budget, including
monitoring and control, outlines all costs
associated with the project, including labor,
hardware, software, contracting fees, and
Project Schedule and
###6 facilities.
Budget
Task dependencies (such as predecessors and
successors)
Scheduled start and finish dates for each task,
based on dependencies
Task constraints (such as must-start-on date
and must-finish-on date)
Resources
The purposeassigned to each
of this task is to task
define a high level
release plan, determine the length and number
of sprints per release. During this activity the
project team needs to take into accounts
business needs, project objectives & goals,
available technical environment, complexity of
Define Initial Release
the solution, geographical and organizational
###6 1 and Sprint schedule,
scope of the project and other aspects (like
Assign Resources
seasonality of customer's business). The
outcome of this task is high level release plan
that includes key features targeted in each
release and number/duration of sprints (note
that the sprint duration should be fixed for all
The purpose
project teamsofand
thisshould
activitynot
is vary).
to extract all
Include key workshops
planned workshops during the project/phase
###6 2 into the project
into a schedule that facilitates workshop
schedule
planning
Obtain Customer sign- Purpose of this task is to obtain customer
###6 3
off for project schedule approval (sign-off)
The purpose of this activity is to create project Project
Establish Cost and schedule and cost baseline against which Mand Budgetplan
###6 4
Schedule baseline tracking, change management and status atory (internal &
reporting is done. external)
The purpose of the project management plan
deliverable is to develop the project Project
Project Management Mand
###7 management plan and the subsidiary plans on Management
Plan atory
the basis of the project scope defined in the Plan(s)
The purpose of this activity is to collect input
project charter.
needed for the project management plan and
Prepare Project document it in a format suitable for both
###7###
Management Plan communication purpose as for formal sign-off
purpose, if possible utilizing the accelerator
file(s) provided
Obtain Project
The purpose of this activity is to achieve a
###7###Management Plan Sign-
formal sign-off of the project management plan
Off
The purpose of the Project and Operational
Standards deliverable is to provide consistent
means of executing and governing project work
in an efficient and effective manner. The key
objective of Project Standards is to identify,
Project and Operational define, approve, and communicate standards
###8
Standards related to project execution.
Where and when applicable, the current
customer processes and procedures, related to
the project standards should be taken into
account when defining the most suitable
The purpose
standards for of
thethis task is to define and set up SCRUM standards and tools, such as SCRU
project.
* Ready for Build (e.g. backlog item has proper size, it is clearly defined and understood, tes
Define and Set Up Agile
* Ready for Demo (e.g. backlog item is fully developed and unit tested)
###8 1 Project Standards and
* Ready for Integration Test (e.g. backlog item integration test is defined (automated), test d
ALM Tools
* Ready for Release (e.g. backlog item user level documentation is complete, ALM Solution
Note that definition of Ready for one step in the implementation process == definition of don
Solution
The purpose of this task is to determine the Manager
customers framework to centrally document Usage
Determine Solution
and relate business processes and technical Mand guideline,
###8 2 Documentation
information of SAP and non-SAP Solutions in atory Business
Procedure
Solution Manager, ensuring transparency, Process
efficient maintenance and collaboration Modeling
Standards
The purpose of this task, also known as
Innovation Management, is to determine the
Software
customers approach for the identification,
System
adaptation and implementation of new and
Configuration
Determine Solution enhanced business and technical scenarios. It
Optio Standards,
###8 3 Implementation is part of the application lifecycle and designed
nal Enhancement
Procedure to decouple technical installation from business
and
innovation using SAP Solution Manager to
Modification
implement the innovation in the system
Standards
landscape.
customers template management approach that
allows customers with multi-site SAP
Determine Template installations to efficiently manage their business
###8 4
Management Procedure processes across geographical distances –
from initial template definition to template
implementation and template optimization, for
example
The purposeas part of atask
of this global
is torollout
determine the
customers approach for managing functional
Test
Determine Test and performance testing of SAP-centric Optio
###8 5 Management
Management Procedure business processes to ensure validated system nal
Standards
behavior after software change events.
Change
customers approach of handling business and
Request and
Determine Change technology-driven changes, using a
Optio Transport
###8 6 Control Management standardized process leading to improved
nal Management
Procedure reliability of solution and minimized risk through
Standards
segregation of duties and transparency of
(CTS)
changes.
customers approach of a centralized and
common incident and issue message
processing for multiple organization levels. The
process offers a communication channel with all
relevant stakeholders of an incident, including
Determine Application
business user, customer-side SAP experts,
###8 7 Incident Management
SAP Service & Support and Partner Support
Procedure
employees.
The Application incident Management is
integrated in all ALM processes of SAP Solution
Manager, in any SAP Business Suite solution
and can be connected to an Non-SAP Help
The
Deskpurpose of this task is to determine the
application.
customers approach of monitoring, alerting,
analyzing and administrating of SAP solutions.
It allows customers to reduce TCO by Post
Determine Technical predefined content and centralized tools for all Optio Implementati
###8 8
Operations aspects of operations in SAP Solution Manager, nal on Service
including End-to-End reporting functionality and Support
either out-of-the-box or individually created by
customers
This task uses SAP Business Process
Integration & Automation Management (BPIAM)
to cover the most important application related
Determine Business operations topics necessary to ensure the
###8 9
Process Operations smooth and reliable flow of the core business
processes to meet a company's business
requirements.
customers approach of Maintenance
Management, how SAP Notes are handled and
Determine Maintenance
###8 10 how they are applied (upon request e.g. current
Management
incident in productive environment, information
from SAP about potential issue (Hot News,
Security Notes)).
customers approach for the identification,
adaptation and implementation of new and
enhanced business and technical scenarios. It
uses Solution Manager to manage the upgrade
Determine Upgrade project holistically and effectively end-to-end
###8 11
Management and allows SAP customers to better understand
and manage the major technical risks and
challenges in an upgrade project, and to make
the upgrade project a “non-event for the
business.”
The purpose of this deliverable is to execute
the project management plan and control and
monitor the work defined in the project scope
statement.
Management plans developed during the
Execution, Monitoring,
project preparation phase (see deliverable
###9 and Controlling of
“Project Management Plan”) guide the
Results
approach to management, execution, and
control of project activities. The project
manager is responsible for ensuring that the
management plans are applied at the
The purposelevel
appropriate of this activity is to assure that the
of control.
Direct and manage project is executed according to what was
###9###
project execution agreed to in project charter, scope statement
The purposemanagement
and project of this activity is to assure that
plan.
resources are assigned to all scheduled project
Monitor and control
###9### activities (and tasks) and that work is
project activities
progressing and deliverables are produced as
expected.
Risk List
(internal &
The purpose of this activity is to capture and
external),
Manage Issues, Risks manage project issues and risks and changes Mand
###9### Project
and Changes related to those e.g. changes of project scope, atory
Change log,
timeline, costs etc.
Project
Issues log
Project
The purpose of this activity to make sure that
Communicate Status (Performance
project stakeholders are aware of status and Mand
###9###and progress to project ) Report
progress of the project including potential atory
stakeholders (internal &
disturbances due to existing risks and issues.
external)
The purpose of this deliverable is to present an
overview of all planned change management
Organizational Change activities. It guarantees that all activities are Optio OCM
###
###
Management Roadmap related to each other as well as to the overall nal Roadmap
project plan and ensures the “checkability” of
OCMpurpose
The activities.
of this activity is to collect all
Prepare Organizational required input for the OCM roadmap and
###
###
###Change Management document it in a format suitable for
Roadmap communication and inclusion into the project
management
The purpose ofplan
this deliverable is to develop a
comprehensive training strategy that provides
all team members with a phase-based learning
Project Training
path for acquiring the skills and knowledge
###
### Strategy and Plan
needed to complete the project successfully.
(team + key-users)
This learning path leads to project readiness as
well as certification on the specific applications
the team members will be using.
Prepare training Project Team
The purpose of this task is to prepare the Optio
###
###
###strategy and plan Training Plan
training strategy and plan. nal
document & Schedule
The purpose of this deliverable is to provide an
overview of the SAP software to be
###
### Project Team Training implemented so that all project team members
have an understanding of the SAP solution for
their areas of of
The purpose responsibility.
this task is to educate project
Conduct Agile Training
###
###1 team on Agile implementation approach,
for the Project Team
principles
The purposeandoftechniques.
the business process map is to
derive and agree on the scope for the start of
the business blueprint phase. During Business
blueprinting, the process map builds the Mand Process Map
###
### Business Process Map
foundation for the process hierarchy – a atory Business
decomposition of the process design – which is Process List
reflected as scenarios, processes, and process
steps in SAP Solution Manager.
The purpose of this task is to complete the
Prepare Business
###
###
### Business Process Map with the content
Process Map
reflecting the process scope of the project
Prepare Demo The purpose of this task is to ensure that a

###
###
###Environment for Scope proper environment is available for the options
Refinement Workshops selection workshops
The purpose of this task is to prepare the scope

Prepare Scope
document with the pre-defined content
###
###
###Document for
according to the SOW and solution
Workshop
documentation
For <SCOPE OPTION>
The purpose of this task is to demonstrate
- Demonstrate the
###
###
### available options related the selected
business processes and
processes in scope
predefined options list
The goal of this task is to complete customer

Complete Customer blueprint document based on interviews and
Blueprint and assessment sessions. The document details
###
###5
Configuration the options customer selected from the pre-
Requirements Template defined solution, all modifications and details
the configuration requirements of the solution.
Validate and Complete Business Process Map
Validate and Complete with pre-defined content depending on delivery
###
###6
business process map model (Industrialized and/or Assemble to Order
process content).
The purpose of Value Determination is to
ensure the alignment of the business case
value drivers with key process changes and Optio
###
### Value Determination Value Map
functionality by establishing a value tracking nal
framework and identifying business
The purpose of this task is to review the project
stakeholders
business case, map key value drivers to
process changes, develop the value tracking
###
###
###Prepare Value Map
framework (KPI's and PPI's), identify value
enablers, as well as assign business
The purpose of this task is for the Product
accountability for value realization.
Owner to prepare the initial product backlog
which consists of the following elements:
■ Vision and Business Case: Why do we want
to do this? What is the value? What are current
pain points?
Define and Prioritize
###
###
### ■ High-Level Business Process scope: What
Epics
are the business scenarios and processes
(level 1 and level 2) to be implemented?
■ Who will work with the processes and what
are their primary business requirements? This
will be used as input for the definition of the
The
user purpose
stories. of this task is to validate that
identified key process changes, key
Validate and Complete Optio Value Audit of
###
###
### performance indicators, and value enablers are
Value Map nal Scope
accurate and make necessary adjustments to
the document
The purpose of business scenario design is to
provide an understanding of the essential
Business Scenario processes at the scenario level (process level
###
###
Design 1-2). It builds the foundation for the business
blueprint phase where process levels 3-5 are
defined.
The purpose of this task is to capture Business
Capture Business
###
###
### requirements and relate them to business
Scenario Requirements
scenarios, business objectives and benefits
Business Scenario Design document with
Validate and Complete
###
###
### relevant pre-defined business process content
Scenario Design
(Assemble to order and/or Industrialized
content)
Store Scenario Level The purpose of this task is to store Business
Solution Documentation Scenario content in Solution Manager,
###
###
###
in SAP Solution according to Business Process Hierarchy
Manager. structure defined for the project.
The purpose of this deliverable is to outline key
elements of the testing methodology that the
project will use as guiding principles going
###
### Prepare Testing Policy
forward. This is should be aligned with the
customers "Enterprise" approach on how to
conduct testing (Not to be updated over time)
The purpose of this task is to collect all required
Prepare Testing Policy information needed for the Test Policy, and to
###
###
###
document document it in a format suitable for
communication.
Obtain Customer Sign-
Purpose of this task is to obtain customer
###
###
###Off for Testing Policy
approval (sign-off)
document
The purpose of the data migration approach
and Strategy deliverable is to capture and
communicate the approach and strategy for the
Data
legacy data migration. This deliverable is
Migration
Data Migration intended to educate the SAP and customer Optio
###
### Approach,
Approach and Strategy project team members on the SAP data nal
Start and
migration framework and methodology used to
Scope
support the data migration project. In addition,
the scope and requirement for data migration
should also be
The purpose ofdetermined
this task is to make the
Prepare Data Migration
###
###
### necessary arrangements for the execution of
Workshop The purpose of the data migration workshop
the workshop
deliverable is to perform a two-day scoping
Conduct Data Migration workshop to explain the SAP data migration
###
###
###
Workshop approach and to understand the customer’s
legacy data systems, business priorities, and
The purpose
technical of the data audit is to identify the
infrastructure.
Conduct Data Audit legacy systems that will supply data for the SAP
###
###
###
(Data Health Check) applications and to profile the quality of the
legacy data.
Prepare Data Migration The purpose of this task is to prepare the data
Scope and migration scope and requirements document
###
###
###
Requirements that captures the overall scope and
Document requirements of the data migration effort.
The purpose of this task is to present data
Present DM scope and
###
###
### migration scope and requirements document to
requirements document
customer project team and obtain buy in.
The purpose of this task is to assess customer
Conduct Organizational organization for the demands of data migration
###
###
###Assessment for Data process. The outcome of this task is
Migration documented current state of the organization
and required target state.
The purpose of this task is to assess customer
infrastructure for the needs of the data
Conduct Infrastructure
migration process. As a result the project team
###
###
###Assessment for Data
learns about available tools and identifies any
Migration
gaps/requirements to acquire tools to support
the migration process.
The purpose of this task is to assess risk for the
data migration activities. The risk assessment
Conduct Risk
focuses on organization, technical risk, data
Assessment for Data
###
###
### quality risk and other risks that may impact the
Migration and Prepare
data migration activities. During this task the
Mitigation Plan
team prepares mitigation strategies for the
individual risk items in the risk register.
The purpose of this activity to collect input
Complete the Data needed for the Data Migration Approach and
###
###
###Migration approach and Strategy document, in a format suitable for both
strategy document communication purpose as well as for formal
sign-off purpose.
The purpose of the technical requirements and
design deliverable is to provide the project with
a specification of the target solution from a
software component standpoint. This
document is intended to serve as a reference
Technical Requirements
for the rest of the project team during the Solution
and Design and Optio
###
### Business Blueprint phase. Landscape
Solution Landscape nal
Design
Deployment Plan
Included in this deliverable is the solution
landscape deployment plan, which is a high
level description of the overall system
landscape approach to be used for the
implementation project.
The purpose of this task is to outline the
Define Solution
###
###
### software components and the design of the
Landscape Concept
future solution landscape.
The purpose of this task is to describe the

Define Solution
###
###
### concept of how the solution in scope will be
Deployment Concept
deployed.
The purpose of the interface inventory
deliverable is to preliminarily identify the
external systems, applications, and business
###
### Interface Inventory
objects or transactions that must be integrated
with the SAP solution to realize the objectives
of the project
The purpose of this task is to collect necessary
Prepare Interface
###
###
### information for the interface inventory
Inventory document
document.
The purpose of the initial hardware sizing

Initial Hardware Sizing
###
### proposal is to begin the process of assessing
Proposal
the hardware infrastructure requirements.
Complete HW sizing The purpose of this task is to completed sizing

###
###
###estimation for solution estimates for the Solution Manager system and
landscape Production and non-Production environments.
system setup deliverable is to establish the
basic tools and processes necessary to support
the project.
One of the most vital project tools is the SAP

Solution Manager, the centerpiece of SAP’s
Application Lifecycle Management tools. The
SAP Solution Manager provides a central point
of access for a variety of essential project
support functions, including:
· Solution Implementation – the
Proj Support
Project Support Tools identification, adaptation, and implementation of Optio
###
### Tools & Sys
and System Setup new and enhanced business scenarios. nal
Setup
· Solution Documentation – centralized
documentation repository ensuring the
relationship of business process definitions with
technical configuration decisions.
· Change Control Management –
synchronized deployment of application
configuration with integrated project control and
quality management.
In addition, customer-specific project
management and documentation tools may
require installation and distribution to project
The purpose of this task is to validate all
technical system requirements for delivery of
Verify Technical System
the service or project. The objective is to ensure
###
###
###Requirements (frontend
that all required technical requirements have
/ backend)
been satisfied and work can be performed by
The purpose of this task is to validate all
the team.
functional requirements for delivery of the
Verify Functional service or project. The objective is to ensure
###
###
###
System Requirements that all required functional requirements have
been satisfied and work can be performed by
the team.
The purpose of this task is to validate that
Check availability of
###
###
### customer has SAP Solution Manager installed
SAP Solution Manager
and setup.
Install or Upgrade SAP The purpose of this task is to validate and

###
###
###
Solution Manager ensure a proper Solution Manager setup.
The purpose of this task is to ensure that the
business process structure in SolMan is
Set up Business supporting the solution documentation and all
###
###
###Process Hierarchy in continued project activities in the coming
SAP Solution Manager phases (business process management, value
management, configuration & development,
test, training and cut over).
Setup of project The objective of this task is to setup project
logistics and logistics, systems and infrastructure that will
###
###
###infrastructure, including support delivery of the project. This may include
team collaboration setup of computers, setup of project team room,
environment telephony, etc.
Install SAP GUI on The purpose of this task is to install SAP GUI
###
###
###
project team computers on project team computers.
Test Remote Access The objective of this task is to validate that the
and Establish OSS remote connection to SAP is working and
###
###
###
Connection (both GUI connection can be established. This is both for
and Web Access) the SAPGUI as well as Web Access.
Prepare authorization The purpose of this task is to prepare

###
###
###roles in the systems for authorization roles in the systems for the project
the project team (DEV) team
The purpose of this task is the initial set up of

all relevant testing tools (the actual
###
###
###Set up of testing tools
configuration will happen during Business
Blueprint)
The purpose of the phase closure and sign-off
deliverable is to:
· Ensure that all required deliverables from
Phase Closure and this phase and the project are complete and
###22 Sign-Off phase accurate, and close any outstanding issues
Deliverables · Identify lessons learned during the phase
to prepare for formal project closure
· Capture customer feedback and potential
Customer References
The purpose of this task is to collect knowledge
assets and lessons learned at the end of each
phase of the project that can be reused later by Project
other projects. Collecting documents, (phase)
Conduct Knowledge Optio
###22### experiences, project highlights and lessons Lessons
Management Gate nal
learned throughout the duration of the project Learned
can help to facilitate the project by providing (internal)
quick access and insights into key deliverables
from earlier
Quality Gatestages of the project.
by conducting a quality check at
critical stages of the project. Project Quality
Gates are an integral part of SAP’s Quality Built
In approach for SAP primed, partner or client
led projects. The objectives of the Project
Quality Gate are:
· To assure that all key deliverables and
Conduct Project Quality
###22### actions of the gate have been completed in
Gate
compliance with recommended practices and to
the customer’s satisfaction
· To enable project management to
continuously communicate the process and
build quality directly into the project
· To provide a tool to effectively manage
project
The expectations
purpose and is
of this task monitor customer
to execute a Project
Management Review that provides a proactive
Conduct Project quality assurance review, with an impartial
###22###Management Review analysis of all aspects of the project – across all
Service project management disciplines, enabling early
detection of project issues with actionable
recommendations.
###22###Off for Phase
approval (sign-off)
Completion
This milestone signifies transition for Project
MILESTONE: Project
###23 Startup activities to Design, Solution Design
Start to Design
Validation
The purpose activities
of this phase is to
create/update the business blueprint, which
is a detailed process-oriented and technical
documentation of the results gathered
during requirements and design workshops
### Lean Blueprint
or based on validation of predefined
solution or service description.
A blueprint consists of multiple documents
illustrating how the company intends to run
its business
The purpose ofusing SAP solutions.
the phase initiation deliverable
###1 Phase Initiation is to formally recognize that a new project
phase starts.
Project
Allocate Resources and
The purpose of this task is to confirm resource Mand Schedule
###1###Update Project
availability for the particular phase. atory (incl.
Schedule
milestones)
The purpose of this task is to ensure the
involvement of the team and other key
###1###Perform Kickoff Meeting resources and their commitment to the project
schedule. The meeting is also used to examine
The purpose of
the approach forthis
thedeliverable is to execute
specific project phase.
statement.
Execution, Monitoring project preparation phase (see deliverable
###2
and Controlling Results “Project Management Plan”) guide the
The purpose of this task is to plan, setup and
conduct various SCRUM meetings in order to
keep the project teams aligned around common
vision, share information amongst the SCRUM
The
teams purpose of this
and align task is to
individuals update
within each theteam.
project
Project
Update Project management plan and the subsidiary
The purpose of these standard meetings is to plans Mand
###2### Management
Management Plan based on
inform the changes
others about work agreed during theteam
that individual atory
Plan(s)
projects
members change
do on management
given day and process.
The purpose of this activity is tosurface assureany that the
Direct and manage blockers that team members need
project is executed according to what help was
###2### addressing
project execution agreed to in. project charter, scope statement
In
andAgile implementation
project managementproject plan. the teams
conduct following meetings:
1. Daily SCRUM meeting - short (about 15
minutes) session within each SCRUM team
facing the SCRUM board team members report
to the team about what they work on and
whether they are encountering any issues that
they need help with. Objective of this session is
to inform and align the team work.
2. Regular SCRUM of SCRUMs meeting -
session in which SCRUM Masters from
individual SCRUM teams share information
Conduct SCRUM about what each SCRUM team works on,
###2###
Meetings surface any cross team alignment topics and
resolve any issues that arise between the
teams. The session is very similar to integration
team meetings conducted in traditional projects.
Note: Cadence of these sessions needs to be
calibrated, but they should be done on at least
bi-weekly basis. The more often they are done
the shorter they can be.
3. Sprint Demo - the purpose of this meeting is
to demonstrate the results of the sprint to
customer and obtain acceptance to release the
features
The developed
purpose of this during
activitythe
is tosprint.
assure Thethat
meeting is are
resources attended by Product
assigned Owner team,
to all scheduled project
Monitor and control End users(and
andtasks)
SCRUM
###2### activities andteam. It is conducted
that work is at
project activities the end of sprint.
4. Sprint Retrospective - or process
expected.
improvement meeting is conducted right after Risk List
Sprint Demo meeting prior to (internal &
The purpose of this activity is closing
to capture the and
sprint.
The objective of this meeting is for the SCRUM external),
###2### team toto
conduct retrospective of project
the sprint, Project
and Changes related those e.g. changes of scope, atory
identify potential improvements of the process, Change log,
prioritize and select top improvements to Project
implement in the next sprint. Issues log
The purpose of this task is to ensure that each Project

Communicate Status contract is closed by verifying that all work (Performance
Mand
###2###and progress to project specified in the contractual arrangement was ) Report
atory
stakeholders completed, and that all defined deliverables (internal &
were accepted. external
The purpose of the stakeholder analysis
deliverable is to detect the level of acceptance
or the general attitude regarding the project on
Stakeholder
the part of all key stakeholders, as well as the Optio
###3 Stakeholder Analysis Analysis
ways they can influence the project. Execute an nal
(Internal)
analysis of current state ‘as-is’ and future state
‘to-be’ business process maps to quantify the
The
deltapurpose of gap’
‘transition this task is to re-visit the
stakeholder identification results, determine the
Conduct classification detailed level of change impacts for the
###3###
of project Stakeholders identified stakeholder (groups) in order to
create transparency about the organizational
and system changes.
The purpose of this task is to identify key users
###3###Identify Key Users needed for the different areas (depending on
the scope of this project).
The purpose of the Change impact analysis
deliverable is to ensure that the organizational Organizationa
and technical changes in business processes Optio l Change
###4 Change Impact Analysis
have been identified and documented by nal Management
comparing the as-is and the to-be business Plan
processes.
The purpose of this task is to validate the
Validate organizational
###4### chosen approach with key stakeholders for the
alignment approach
continued project execution.
The purpose of this task is to define the
baseline for where organizational change Business
Establish Baseline of Optio
###4### management starts and against which progress Readiness
Current State nal
and success of the OCM-activities are Approach
measured.
The purpose of the communication plan
deliverable is to summarize all planned
communication measures and to help identify
the dependencies among various activities. The
###5 Communication Plan
communication plan is aligned to the overall
OCM roadmap and addresses mainly external
communication to stakeholders, key users, end
The purpose
users, of this task is to provide a set of
and suppliers.
key messages to describe the benefit of the
SAP solution and the change impact for every
Define Value
stakeholder group. Due to the individual goals
###5###Argumentation / Key
and interests of stakeholder groups, it is
Messages
necessary to define specific key messages for
each stakeholder group, for example to specify
what to tell particular employees.
The purpose of this task is to define the
Define Communication
###5### communication strategy for the change
strategy
management activities.
The purpose of the End User Training Strategy
and Plan deliverable is to develop a high level
End User Training training plan that provides the recommended Mand Training
###6
Strategy and Plan approach and corresponding activities to atory Project Plan
prepare the end users for using the new
The purpose of this task is to perform an
system.
analysis of the end-user population to be
trained and determine where the skills levels,
knowledge gaps, and training requirements are
Conduct Learning
###6### located. This analysis contains the key
Needs Analysis
customer information for definition of the end-
user training and documentation of high-level
project plan recommendations, proposals, and
preliminary strategies.
The purpose of this task is to develop a working End User
Develop Detailed End- document to track evolution of documents and Optio Training and
###6###
User Training Plan progress of processes for all education aspects nal Documentatio
of the project n Developed
The purpose of the Project Team Training
deliverable is to ensure that the project team is
###7 Project Team Training informed about the way of working during the
Blueprint Phase including usage of Solution
Manager for Solution Documentation.
The purpose of this task is to clarify
deliverables and expectations, methodology,
and tools. Typically two to three days should be
reserved for this training. Once the team
members or at minimum the team leads are
identified, they will be brought on board with
this ramp-up training before the phase kickoff
meeting. The blueprint ramp-up deliverable:
Conduct Blueprint · Sets project team expectations and
###7###
Ramp-up Training blueprint deliverables
· Provides guidance for blueprinting
workshops and relevant enabling tools
· Introduces blueprint quality assurance
and its acceptance criteria
· Prepares for essential blueprinting skills,
such as workshop facilitation, requirements
gathering, and process modeling
The purpose of this task is to train the key
Conduct Key User
###7### users for the solution in scope (pre-defined
training
content)
The purpose of the end user training content
deliverable is to create a curriculum plan that
End User Training
###8 covers the skills that end users will need to
Content
possess to use the system. This document will
be refined throughout the project.
The purpose of this task is to validate and
Adaptation of Pre-
adapt the standard end user training material
###8###delivered Training
being pre-delivered within the solution. (delivery
Content
model 3&4).
Prepare and Build The purpose of this task is to prepare training
###8###Training Content in content in the system environment being set up
Project Environment for the project.
analysis deliverable is to validate the predefined
scenarios, processes and enhancements;
identify potential gaps between delivered
product and customer requirements. The
###9 Scope Validation
deliverable only captures requirements for
gaps. It follows an iterative approach. Existing
documentation and models can be altered,
changes
This task have to bepredefined
validates marked and documented
general settingsin
and that these are still relevant for the scope of
the implementation, such as organizational
structures or customer or material masters, and
to identify potential gap between delivered
For <General Settings
product and customer requirements.esign a
#1 - n> - Conduct
###9### solution for these business objects within the
Validation and Fit-gap
SAP solution. These objects are associated to
Analysis
processes and reflected in applications so
understanding these relationships is essential
for overall integration and cross-process
integrity.
This task validates predefined scenario solution
documentation, identifies potential gap between
delivered product and customer requirements.
For <Scenario #1 - n> -
Only requirements for gap are being captured.
###9###Conduct Validation and
It follows an iterative approach. Existing
Fit-gap Analysis
changes have to be marked and documented in
This taskManager
Solution validates predefined process solution
documentation, identifies potential gap between
delivered product and customer requirements.
For <Process #1 - n> -
Only requirements for gap are being captured.
###9###Conduct Validation and
It follows an iterative approach. Existing
Fit-gap Analysis
changes have to be marked and documented in
Solution Manager.
This task validates the pre-defined RICEFW
Validate pre-defined
Objects (reports, forms etc.). Additional
###9###RICEFW Objects
customization and enhancements should be
(reports, forms etc.)
kept to a minimum.
The purpose of this task is to capture all
identified delta requirements from the validation
sessions in the product backlog.
Determine Gap list and
The requirements are captured in form of user
###9 5 Update Product
stories that define the requirement from end-
Backlog
user perspective, provide details on how to test
the feature when it is completed, priority of the
backlog item and business value.
(cross-process view) is to identify business
objects that are relevant for the scope of the
implementation, such as organizational
structures or customer or material masters, and
to design a solution for these business objects
within the SAP solution. Business objects are
Business Solution
associated to processes and reflected in
###
### Design for Business
applications. Understanding these relationships
Objects
is essential for overall integration and cross-
process integrity.
Business object modeling may also build the

foundation for service modeling, if the project is
The purpose of
implementing a this task is to capture
service-oriented the
architecture
design and requirements of the organizational
structure. This should reflect multiple views of a
company i.e. Legal, Fiscal, Functional, Product-
Business
oriented, Regional and geographical,
Define Business Mand Blueprint
###
###
### Customer-group, Distribution-channels,
Organization Structure atory Documents(O
Purchasing-channels etc. depending on the
rg Structure)
process scope.
It is best to store all organizational structure
deliverables in the process hierarchy in SAP
The purpose
Solution of General Settings and Master
Manager.
Data is a detailed description of design and
maintenance processes for general settings
and master data. This includes definition of
business rules and ownership.
Define General Settings
###
###
###
and Master Data General Settings and Master Data Design also
addresses cross-application general settings
and master data for e.g. countries, languages,
currencies, organizational units, units of
measure, number ranges, product hierarchies,
material types and shipment rules.
describe all relevant end-user roles and
corresponding responsibilities from a business
point of view. This includes User role concept
Define User Role Mand User Role
###
###
### overview, User role documents - one per role,
Concept atory Document
Consistent user role name and assignment to
defined business organization model,
Corresponding SAP default roles, Mapping
The purpose of this task is to define a logical
data model for master or transactional data
relevant to the implementation scope across the
Define Logical Data
###
###
### application landscape, including both legacy
Model
and SAP components.
This will help manage the data relationships
and align interfaces correctly.
The purpose of the Detailed Design - Business
Scenarios deliverable is the continuation of
process decomposition started in project
Detailed Design - Solution
preparation. This includes documentation of Mand
###
### Business Scenario #1 Documentatio
requirements, solution design for the scenarios atory
-n n
and processes. This information is populated in
the business process hierarchy in SAP Solution
Manager.
collecting input and finalize the Scenario Design
Document, in a format suitable for both
communication purpose as well as for formal
Complete Business
sign-off purpose. The documented business
###
###1 Scenario Design
scenario provides an understanding of the
Document
essential processes at the scenario level (PL1-
2). It also builds the foundation for the business
blueprint
Owner team phase where process
to decompose the levels 3–5 are
initial product
backlog EPICS into more granular backlog
items that the SCRUM teams can design,
develop and deliver in the sprint. The Product
Backlog which consists of the following
elements:
■ Vision and Business Case: Why do we want
to do this? What is the value? What are current
pain points?
■ Detailed Business Process scope: What are
Refine Epics and
the business scenarios and processes (down to
###
###2 Update Product
level 3) to be implemented?
Backlog
■ Who will work with the processes and what
are their primary business requirements? This
will be used as input for the definition of the
user stories.
■ Priority of each backlog item
■ Estimated size and effort (the effort is
estimated by the SCRUM team not the PO
team)
■ Business Value
■ How
The to testof
purpose the backlog
this item upon
deliverable completion
is to design, in
Detailed Design - detail, the to-be business process down to Solution
Mand
###
### Business Process #1 - activity level (PL 3-5) and to describe gaps Documentatio
atory
n where the standard solution does not cover all n
required
The functionalities.
purpose of this task is to continue
collecting input and finalize the Business
Process Design Document, in a format suitable
Complete Business for both communication purpose as well as for
###
###1 Process Design formal sign-off purpose. The document provides
Document details of the to-be business process down to
activity level (PL 3-5) and describes the gaps
where the standard solution does not cover all
The purpose
required of this task is to demonstrate
functionalities.
standard functionality of the SAP solution to the
Product Owner and Key Users in order to solicit
input and gain acceptance for the standard
feature. In case standard functionality needs to
be enhanced product owner captures this
Demo or Visualize
###
###2 requirement in product backlog in the form of
Standard Functionality
user story.
Features that are complex or time consuming to
configure in the system can be presented in a
visualization tool like SAP Visualization by iRise
to solicit input and gain acceptance of the
feature requirements.
The purpose of this task is to capture all
identified delta requirements from the demo /
visualization sessions in the product backlog.
The requirements are captured in form of user
stories that define the requirement from end-
Define User Stories and
user perspective, provide details on how to test
###
###3 Update Product
the feature when it is completed, priority of the
Backlog
backlog item and business value. It is
responsibility of Product Owner team to
maintain the product backlog and detail the
user stories so they are understood by the
The
SCRUMpurpose
team.of Value Realization is to establish
the sustainable mechanisms to monitor and Optio Value Audit of
###
### Value Realization
controls the predefined KPI's and PPI's of the nal Scope
to-be process and/or process changes.
The purpose of this task is to design the Value
Prepare Value Dashboard by specifying the KPI's and PPI's
###
###
###
Dashboard and how these are monitored and controlled
during projectofexecution
The purpose and post
this deliverable Go-Live.
is to specify and
detail how to realize the solution, both Core
Configuration and identified gaps and core Development
Detailed Design - enhancements needed to complement standard list(incl.
Mand
###
### Configuration and functionality, in order to fulfill business RICEFW,
atory
Enhancements requirements. These RICEFW objects are SOA,
based on process requirements, and they are Migration)
specified in business process and solution
design documents.
Finalize Core
###
###
### documentation for identified core configuration
Configuration Design
objects related to business processes.

Finalize Delta documentation for additionally identified
###
###
###
Configuration Design configuration objects related to business
processes.
documentation for identified RICEFW objects.
These objects are classified as:
· Reports that have to be designed or
adjusted
Define functional · Interfaces that need to be developed
###
###
###Design - RICEFW · Conversions (mostly related to master
Object #1 - n data)
· Enhancements that need to be
performed
· Forms for print-out or other purposes
· Workflows that need to be implemented
The purpose of this task is to prepare functional
Define Functional
design document for all SOA and 3rd party
###
###
###Design - SOA & 3rd
applications / solution enhancements or
party applications #1 - n
extensions.
The purpose of Baseline Build Plan is to define
plan to setup fully functional environment to
###
### Baseline Build Plan demonstrate the standard functionality of the
SAP solution to the customer product owner
team, key users
The purpose andtask
of this stakeholders.
is to determine which
user stories will be built in the system and
which ones will be visualized. The decision
process is based on customer requirements,
Define Baseline Build
###
###
### understanding of the solution, complexity of the
Feature Set
setup and availability of proper visualization
tools. Result of this activity is prioritized list of
features that will be built in the system and list
of features that will be visualized.
The purpose of this task is to define plan for
building the baseline build system and
visualizations that will be used for demo of the
solution to the product owner team and key
users. The plan may include multiple sprints
Conduct Baseline Sprint depending on the size and complexity of the
###
###
###
Planning Meeting baseline build. Teams may also choose to
conduct the baseline build as one sprint. The
SCRUM meetings should be already in place
and followed during the baseline build to
establish regular routine and cadence for the
The purpose of Baseline Build is to setup fully
team.
functional environment to demonstrate the
standard functionality of the SAP solution to the
customer product owner team, key users and
###
### Baseline Build
stakeholders. The results of the demo is either
acceptance of standard feature or new delta
requirement that is captured in the form of user
The
storypurpose of this backlog.
in the product task is to build the baseline
functionality defined in the baseline user story.
This is conducted in iterative fashion through
Build Baseline User
###
###
### out the baseline build. The outcome of this task
Stories (Iterative)
is fully functional baseline build of user story
that is unit tested and ready for demo to the
baseline build feature
product owner and key(user story) to the key
users.
users and product owner team to obtain
acceptance or solicit input for delta
requirement.
Demo Baseline Feature
The results of the demo is either acceptance of
###
###
###Set and Solicit
standard feature or new delta requirement that
Feedback (Iterative)
is captured in the form of user story in the
product backlog. The demo is conducted in
iterations that correspond to the cadence of
sprints chosen
The purpose offor
thethe baseline build
visualizations during the
deliverable is
to ensure that the defined processes are
###
### Visualization exemplified and easier to understand and judge
by the project team members, key users and
stakeholders.
The purpose of this task is to initiate the work to
Capture Initial
document the visualization requirements as part
###
###1 Visualization
of the business process requirements
Requirements
documentation.
The purpose of this task is to create
visualization of the functionality as defined in
the baseline user story. This task is conducted
Build Visualization
###
###2 in iterative fashion through out the baseline
(Iterative)
build. The outcome of this task is visualization
of the baseline build user story that is ready for
The
demopurpose of this task
to the product is to
owner demo
and key the
users.
baseline build visualization to the key users and
product owner team to obtain acceptance or
solicit input for delta requirement.
Demo Visualizations The results of the demo is either acceptance of
###
###3 and Solicit Feedback standard feature or new delta requirement that
(Iterative) is captured in the form of user story in the
product backlog. The demo is conducted in
iterations that correspond to the cadence of
sprints chosen for the baseline build during the
Baseline
The purpose BuildofPlanning session.is to obtain final
this deliverable
sign-off for the baseline build (and
###
### Baseline Build Sign-Off
visualizations) and product backlog prior to
proceeding to the Realization phase.
The purpose of this task is to demo the
baseline build functionality and visualizations to
the key users and product owner team along
with the product backlog to obtain acceptance
of the baseline build and product backlog.
Conduct Baseline Build
The results of the demo is either acceptance of
###
###
###and Visualizations
standard feature or in exceptional cases new
Demo
delta requirement that is captured in the form of
user story in the product backlog. This demo is
conducted at the end of the Baseline Build to
serve as an input to formal sign-off for the
The purpose
baseline build.of this task is for the key users
and product owner team to conduct acceptance
Conduct Acceptance
test of the features built in the baseline build.
###
###
###Testing of Baseline
This may also include walk-throughs of the
Build
visualizations for features that have not been
fully built in the system.
documentation of the baseline build and
capture it in SAP Solution Manager. In
Finalize Documentation particular this pertains to configuration
###
###
###
of Baseline Build documents, test cases, test scripts,
visualizations, etc. as defined in the project
documentation
The purpose of standards
this task isdefined in previous
to formally signoff
the baseline build, visualizations and product
Signoff Baseline Build backlog. This signals to the project team that
###
###
###
and Visualizations they can proceed to the next phase to
iteratively build the features defined in product
backlog.
The purpose of the legacy data migration
deliverables is to develop the designs, plans, Data
Mand
###
### Legacy Data Migration and procedures to support the migration of Migration
atory
legacy data during the implementation of the Design / Plan
SAP applications.
The purpose of this task is to ensure that
Ensure Master Data
defined processes and procedures needed to
###
###
###Management
ensure correct quality and handling of master
Processes Ownership
data are operational in the organization.
Conduct Data Mapping
This task ensures that provided master data for
workshops (master data
###
###
### Assemble to order and/or Industrialized content,
for pre-defined
can be utilized by the project.
solutions)
The purpose of this task is to conduct a detailed
analysis of legacy data in order to determine:
· The availability and quality of existing
Conduct Data Quality Mand Test Cases &
###
###
### data to support the SAP applications to be
Assessment atory Results
implemented
· The complexities and risks associated
with the data and migration process
The purpose of this task is to design the
specific architecture, programs, processes, and
Define Automated Data
###
###
### tasks required to support the extraction,
Migration Approach
validation, harmonization, enrichment, and
cleansing of the legacy data.
The purpose of Manual Data Migration design
is to develop the approach for manually
Define Manual Data bringing legacy data into the SAP database
###
###
###
Migration Approach when automated programs are not available or
the data volume does not justify the investment
in developing such programs.
The purpose of the data quality plan is to define
Prepare Data Quality
###
###
### the metrics that track and monitor data quality
Plan
during the data migration process.
The purpose of data Security Design is to
Prepare Data Security identify and develop the necessary architectural
###
###
###
Design and plans designs and plans to support the security
requirements.
The purpose of legacy data archive is to make
legacy master data not considered currently
###
### Legacy Data Archive active available for reference in a format
compatible with the master data formats of the
SAPpurpose
The solution.of this task is to establish the
Prepare baseline framework for legacy data archiving, meaning
framework for the the planning for usage of legacy-data archive
###
###
###
legacy data archiving objects, the legacy archive specifications, and
solution data retention rules for master-data archive
The purpose of the Technical Solution Design
objects.
deliverable is to provide a detailed technical
and integration design of the solution to be
implemented, accounting for all decisions made
Technical Solution during the Business Blueprint phase including
###
###
Design business process definitions, integration with
external systems, and physical server
deployment.

technical infrastructure specification which
provides a technical description of the entire
Prepare technical
technology landscape from a physical
###
###
###infrastructure
standpoint, showing where each of the SAP
specification
and non-SAP systems are installed, and the
physical or virtual servers assigned to each
The purpose
system alongof thistheir
with taskspecifications
is to define system
environment that will be used for the baseline
Identify System build. At minimum the environment needs to
Environment for have two systems Development and Quality
###
###
###
Baseline Build and Assurance. It is recommended to also provide
Baseline Acceptance team with Sandbox environment where they
can experiment with the functionality during the
baseline build.
The purpose of this deliverable is to ensure
User Access and
###
### proper set up of a Roles and Authorizations
Security
procedure and approach for the project.
The purpose of this task is to document the
authorization requirements at the level of
Authorization Authorization
business scenario and process, to evaluate Mand
###
###
###Requirements and Requirements
chosen authorizations concepts against SAP atory
Design and Design
standards and to determine a feasible
implementation approach.
The purpose of the development environment
deliverable is to install a viable, correctly Solution
Development Mand
###
### configured technical development environment Landscape
Environment (DEV) atory
that is available for use by the project team to Design
begin the realization phase.
Execute Technical
The purpose of this task is to install SAP
Installation of SAP
###
###
### components needed for the realization of
Products for DEV
project scope.
environment
Execute Technical
The purpose of this task is to upgrade SAP
Upgrade of SAP
###
###
### components needed for the realization of
Products for DEV
project scope.
environment
This task ensures that all solution
Install Solution
documentation is made available for the project
###
###
###Documentation in
team. Preferably the repository for this should
Solution Manager
be Solution Manager.
Execute Technical
This task deals with the installation of 3rd party
###
###
###Installation of 3rd party
products needed to realize scope of the project.
products
Set up Role assignment
The purpose of this task is to set up users in
###
###
###/ Authorizations / Test
the development environment.
Users in DEV
The objective of this task is to perform any

Perform Manual
###
###
### remaining manual configuration changes in the
Configuration in DEV
Development environment.
Validate Role
The objective of this task is to validate the
assignment /
###
###
### assignment of user role profiles / authorizations
Authorizations / Test
to the test users in the development landscape.
Users in DEV
Create master data in

Prepare master data required for a business
###
###
###DEV environment -
process
Master Data #1 - n
The purpose of this deliverable is to create
project related test framework, which gets
content input from the existing Test Policy
(1.16.), to build a central foundation around the
taken approach (e.g. Test Approach and
Methodology, Test Standards and Guidelines,
Test Strategy
Test Case Development, Defect Management, Mand
###
### Testing Strategy Plans &
Reporting and Analysis, Roles and atory
Results
Responsibilities)
on functional testing (unit-, string-, integration-,
scenario-, user acceptance, regression testing
etc.) and performance testing. The actual test
strategy documentation for functional testing
The objective of this task is to create a
and performance testing have to be separated.
centralized document for functional- and
Prepare Test Strategy performance testing, which incorporates
###
###
###
document standard and procedures which will be used for
the detailed test plan preparation /
documentation.
Review and Validate The objective of this task is to communicate the
###
###
###Testing Strategy with testing strategy (functional and performance) to
customer the customer project team and validate it.
Obtain customer sign- Purpose of this task is to obtain customer

###
###
###
off on Testing Strategy. approval (sign-off)
The purpose of this deliverable is to refine the
Release and Sprint Initial Release Plan that was defined earlier. At
###
###
Plan this time the team also defined sprint plan for
the first
The few iterations.
purpose of this task is to refine the Product
Backlog with vital information required for
release and sprint planning activities. The
Product Owner Team has responsibility to refine
Update Product
###
###
### the user stories so they are clearly understood
Backlog
by the SCRUM teams. Each user story needs
to have clear definition of the requirement in the
language of the customer, defined test criteria
The purpose ofbusiness
and assigned this taskvalue.
is to conduct release
planning meeting to define scope of product
releases based on the prioritized product
Conduct Release
###
###
### backlog. The meeting is lead by Product Owner
Planning Meeting
and its objective is to define scope of the first
release and outline key features slated for
follow-on releases.
The purpose of this task is to review the release
and sprint plans against the statement of work
for the project. The objective of this task is to
identify any new features that have been
Validate Release and
surfaced during the baseline build that may not
###
###
###Sprint Plan Against
be part of the original scope and may require
SOW
amendment of SOW or Change Request. This
task is the responsibility of SAP Project
Manager and Chief Product Owner/Sponsor
from the customer side.
deliverable is to:
Delivery of
projects
Mand Results
###
### Sign-Off phase accurate, and close any outstanding issues
atory Delivery
Acceptance
Protocol
Customer References
###
###
### experiences, project highlights and lessons Lessons
Management Gate nal
from earlier
Quality Gate are:
###
###
### actions of the gate have been completed in
Gate
The purpose
project of this task
expectations and is to conduct
monitor customer
retrospective meeting with the SCRUM team to
identify potential improvements of the SCRUM
process. The objective of this task is to serve as
continuous improvement mechanism for the
Execute Baseline
###
###
### team to adjust to changing project environment
Retrospective
and needs. The team will select one or two key
improvements to implement in the next iteration
and handles them as user stories that are
added to the product
The purpose backlog,
of this task prioritized
is to execute and
a Project
tracked
Management along Review
with other
thatuser stories.
provides a proactive
Conduct Project quality assurance review, with an impartial
###
###
###Management Review analysis of all aspects of the project – across all
Service project management disciplines, enabling early
detection of project issues with actionable
recommendations.
Review of SAP Solution service that provides a
proactive quality assurance review of the
design of the SAP solution which is being
Conduct Design Review implemented. It delivers an impartial analysis of
###
###
###
Service all aspects of the solution design – across all
relevant design perspectives – and leads to an
early detection of potential solution risks and
offers actionable risk mitigation
The purpose of this task is to ensure that each
contract is closed by verifying that all work
Manage Fulfilled
###
###
### specified in the contractual arrangement was
Contracts
completed, and that all defined deliverables
were accepted.
###
###
###Off for Phase
approval (sign-off)
Completion
MILESTONE: Design to This milestone signifies completion of Design
###
###
Build activities and transition to Build activities
implement the business scenario and
process requirements based on the
business blueprint completed in the
previous phase.

· Establishment of the solution
landscape
· Implementation of the final solution in
### Realization the development environment
· Overall testing of the solution within
the quality environment
· Release of the solution for production
(live) operations
· Preparation for data migration and
data archiving
· Identification of value delivery
concepts
The purpose of the phase initiation deliverable
phase starts.
Project
Schedule
milestones)
the approach for the specific project phase.
Sprint Initiation The purpose of this deliverable is to initiate
###2
(Iterative) sprint in formal
The purpose of Sprint Planning
this task Meeting.
is to initiate sprint by
selecting the set of user stories that will be
implemented in the sprint (scope of the sprint).
During the sprint planning meeting the SCRUM
Conduct Sprint team estimates the stories and clarifies with
###2###Planning Meeting product owner team any questions that may still
(Iterative) remain open. The team commits to deliver set
of highest priority stories from the backlog. This
meeting formally sets the scope for the sprint.
This purpose
The meeting ofis conducted in theisbeginning
this deliverable to executeof
eachproject
the sprint.management plan and control and
statement.
###3
The purposelevel
appropriate of this task is to update the project
of control. Project
Update Project management plan and the subsidiary plans Mand
###3### Management
Management Plan based on the changes agreed during the atory
Plan(s)
projects change management process.
Team Activities
■ The team performs their sprint tasks as to the
sprint backlog, taking priority and done criteria
into account
■ The team attends the Daily Stand-up
Meeting. The Daily Stand-up Meeting serves for
information exchange among the team
members. It should not exceed 15 minutes and
occurs same time same place each day. After
the meeting, the team updates the sprint
backlog (what are remaining tasks and efforts).
For more information please refer to the Scrum
Meeting Guidelines.
■ Scrum-of Scrum Meetings are conducted to
coordinate the work between different scrum
teams. Scrum of Scrum meetings allow teams
Perform Sprint
to discuss their work, focusing especially on
###3###Execution Activities
areas of overlap and integration. For more
(Iterative)
information please refer to the Scrum Meeting
Guidelines
Product Owner Activities
■ Prepares ready-state user stories for the next
sprint(s).
■ Aligns expectations and requirements with his
business stakeholders.
■ Is available for answering questions from the
team.
Scrum Master Activities
■ Makes sure that the Scrum process is
followed (organizing and facilitating Daily
Scrums, daily updates of remaining tasks and
effort by team, organization of sprint review and
retrospective meetings)
■ Solves
The blocks
purpose andactivity
of this supports team,
is to including
assure that the
###3###
plan.
Monitor and control
project activities
expected.
Risk List
(internal &
external),
###3### Project
Change log,
Project
Issues log
Project
external
coordinate the work between different project
SCRUM teams. SCRUM of SCRUMs meetings
allow teams to discuss their work, focusing
especially on areas of overlap and integration.
The meeting cadence is defined for the entire
Perform Scrum-Of-
project and follows the same structure. Some
###3###Scrums Meeting
teams conduct daily SCRUM of SCRUMs
(Iterative)
meeting while others consider weekly meeting
sufficient. The main driver for the meeting
cadence is the level of collaboration between
the individual SCRUM teams and level of
dependencies between the features built in
The purpose of Organizational Alignment is to
ensure a smooth transition process towards the
new way of working. This includes the
Organizational
###4 alignment of roles and responsibilities and
Alignment
activities to ensure that all employees are fully
aligned to the goals of the project and
The purpose of this task is to use the results
organization.
from previous change impact analysis and the
role mapping information (mapping of new
Execute Role Mapping Optio User Role
###4### business user roles to existing roles and
and Transition Planning nal Document
organizational structure) and determine an
appropriate transition approach for the
business.
The purpose of this task is to get to get
Conduct Sounding complex organizational feedback regarding the
###4###
Board/Pulse Checks progress and acceptance of the project from
the customer’s view.
The purpose of this task is to communicate the
scope and plan for the sprint to the users
Communicate Sprint outside of the core project team. This may
###4###Scope and Plan include end users, key stakeholders, people
(Iterative) external to the project that have interest in
information about the project plans and
The purpose of this task is to communicate the
progress.
sprint results to the users outside of the core
project team. This may include end users, key
Communicate Sprint
###4### stakeholders, people external to the project that
Result (Iterative)
have interest in information about the progress
of the project and accomplishments of the
project team.
Refine and Execute The purpose of this task is update
###4###
Communication Plan communication plan and execute accordingly
The purpose of this deliverable is to determine

Educational Readiness the potential issues with the SAP education
###5
Review strategy and solution before they impact the
quality of the of
The purpose SAPthissoftware deployment.
task is to capture feedback
Prepare Educational on both the training strategy and approach,
###5###
Readiness Report determine issues and propose resolutions for
identified issues.
The purpose of the deliverable End User
End User
Training Content Enabled is to ensure
End User Training Optio Training and
###6 availability of end user training material, training
Delivery Enabled nal Documentatio
environment, logistics infrastructure and skilled
n Developed
instructors.
This task ensures a consistent appearance of
Prepare End User
the training materials and documentation by
###6###Training Materials and
providing the development team with standard
Documentation
templates.
Training
The purpose of this task is to ensure that the
Set up Training Optio Environment
###6### training environment is correctly populated with
Environment nal Population
correct data for training.
and Testing
The purpose of this task is to provide a detailed
Perform Training of the outline of presentations and activities that serve
###6###
Trainers to educate and prepare the trainers scheduled
to instruct end-user training classes
The purpose of this task is to prepare the
End User
Develop End User execution of end-user training by mapping end
Optio Training
###6###Training Schedule and users to appropriate training courses,
nal Schedule and
Logistics plan developing a training schedule and logistics
Logistics
plan, and inviting end users to courses
Solution
The purpose of the Configured General Documentatio
Configured General Settings and Organizational Structure n (incl.
Settings and deliverable is to complete and document the Mand Process list,
###7
Organizational initial configuration of the system on the basis atory Configuration,
Structure of the decisions made in the business blueprint Interfaces,
phase. Development
s)
The purpose of this task is to implement the

Configure General
###7### configuration related to general settings, and to
Settings
document this in Solution Manager.
Configure The purpose of this task is to implement the

###7###Organizational configuration related to organizational structure,
Structure and to document this in Solution Manager.
Solution
Documentatio
The purpose of the Configured Master Data
n (incl.
Objects 1-n deliverable is to configure the
Configured Master Data Mand Process list,
###8 master data in the SAP software system
Objects #1 - n atory Configuration,
according to the business process requirements
Interfaces,
specified in the business blueprint phase.
Development
s)
Prepare and Load

The purpose of this task is to prepare master
master data - Master
###8### data required for all business processes' unit
Data Object <MASTER
and string tests in DEV.
DATA OBJECT NAME>
Configure Master Data The purpose of this task is to complete

###8###
Objects #1 - n configuration of master data in the system
Solution
Documentatio
The purpose of the Core Configuration and
n (incl.
Core Configuration and Documentation deliverable is to ensure that the
Mand Process list,
###9 Documentation - configuration is implemented, tested and
atory Configuration,
Process #1 - n documented.
Interfaces,
Development
s)
Complete Core
Configuration, including
###9### Core Configuration, write valid test cases and to
documentation and test
document this in Solution Manager.
cases
Prepare Unit Test The purpose of this task is to prepare the test
###9###
Cases cases
Prepare String Test The purpose of this task is to prepare the test
###9###
Cases cases
Execute Business The purpose of this task is to perform unit test Optio Test cases &
###9###
Process Unit Test for the configuration nal Results
The objective of this task is to resolve any
issues identified during the Business Process
Perform defect
Unit Test. It is crucial that the issues are re-
###9###resolution for Business
tested by users that reported them (or
Process Unit Test
designated re-testers) and that they are
confirmed.
Execute Business The purpose of this task is to perform string test Optio Test cases &
###9###
Process String Test for the configuration nal Results

Perform defect issues identified during the Process String Test.
###9###resolution for Process It is crucial that the issues are re-tested by
String Test users that reported them (or designated re-
testers) and that they are confirmed.
Solution
Documentatio
The purpose of the Delta Configuration n (incl.
Delta Configuration - deliverable is to ensure that the configuration is Mand Process list,
###10
Process #1 - n implemented, tested and documented. atory Configuration,
Interfaces,
Development
s)

Complete Delta
###10### Delta Configuration, write valid test cases and
Configuration
to document this in Solution Manager.
The objective of this task is to develop process

Complete Delta
###10### documentation for any changed processes or
Process Documentation
for any new processes added to the standard.
The objective of this task is to develop process

Complete Delta test cases for any changed processes or for
###10###
Process Test Cases any new processes added to the standard
solution.
Execute Business
The purpose of this task is to perform unit and Optio Test cases &
###10###Process Unit and String
string test for the configuration nal Results
Test Cases
Perform defect issues identified during the Unit and String Test.
###10###resolution for Unit and It is crucial that the issues are re-tested by
String Test users that reported them (or designated re-
Development
Enhancement The purpose of this deliverable is to develop list(incl.
Mand
###11 Development - RICEFW and test the RICEFW objects. Documentation RICEFW,
atory
Object #1 - n to be stored in Solution Manager. SOA,
Migration)
The purpose of this task is to develop the

Develop RICEFW
###11### RICEFW object according to the functional
Object #1 - n
specification,
RICEFW object information in a technical
Document RICEFW
###11### specification and define the appropriate test
Object #1 - n
case(s). Documentation is stored in Solution
Manager.
Execute Test Cases - The purpose of this task is to perform unit and Optio Test cases &
###11###
RICEFW Object #1 - n string test of the developments. nal Results

Perform defect issues identified during the RICEFW object(s)
###11###resolution for RICEFW Test. It is crucial that the issues are re-tested by
Object(s) Test users that reported them (or designated re-
The purpose of this task is to perform final code
Conduct Final Code
###11### review of the development objects and confirm
Review
readiness for transport into QAS.
The purpose of the Business Process
Procedures deliverable is to provide the basis
Business Process for end-user training, end-user training
###12
Procedure documentation and test case creation. The
procedures may also be used by security to
develop roles and authorizations.
Develop Business The purpose of this task is to validate and
###12###Process Procedure complete Business Process Procedures from
Document the blueprint phase.
Validate and Complete The purpose of this task is to validate and

###12###Business Process complete Business Process Procedures from
Procedure Document the blueprint phase.
The purpose of the value audit deliverable
during the realization phase is to monitor and
control the implementation of key process Optio Value Audit of
###13 Value Audits
changes and value enablers, as well as to nal Scope
ensure the design and implementation of the
Value Dashboard for KPI tracking purposes.
The purpose of this task is to perform value
audit according to defined Value Dashboard,
and provide mitigation strategies for identified
###13###Perform Value Audit
risks that could jeopardize the value identified
during the business case development.
The purpose of this deliverable is to provide

###14 Scenario Test #1 - n evidence that the scenarios designed can be
supported by the solution implemented.
The purpose of this task is to identify and
Prepare Test Case -
###14### document applicable test case(s) for the
Scenario #1 - n
scenario.
Execute Test Case - The purpose of this task is to perform scenario Optio Test cases &
###14###
Scenario #1 - n test. nal Results
issues identified during the scenario testing. It is
Resolve Issues for
###14### crucial that the issues are re-tested by users
Scenario #1 - n
that reported them (or designated re-testers)
and that they are confirmed.
###14###off for Testing of
approval (sign-off)
Scenario #1 - n
The purpose of the quality assurance
infrastructure and environment design and
Solution
Quality Assurance setup deliverable is to install a viable, correctly Mand
###15 Landscape
Environment (QAS) configured technical QA environment that is atory
Design
available for use by the project team to perform
QA testing.
Execute Technical
The purpose of this task is to install SAP
Installation of SAP
###15### components needed for the realization of
Products for QAS
project scope.
environment
Execute Technical
The purpose of this task is to upgrade SAP
Upgrade of SAP
###15### components needed for the realization of
Products for QAS
project scope.
environment
The purpose of this task is to build the quality
Import Configuration
assurance (QA) environment with changes that
and Development
###15### have been unit-tested and released from the
Objects to QAS
development environment.
Environment
Set up Role Assignment

The purpose of this task is to set up users in
###15###/ Authorizations / Test
the Quality Assurance environment.
Users in QAS
Prepare and Load

Master Data into QAS
###15### data required for all business processes in
Environment for
QAS.
<SCOPE OPTION>
Perform Manual The objective of this task is to perform any

###15 6 Configuration Settings remaining manual configuration changes in the
in QAS Quality Assurance environment.
This milestone signifies completion of Build
MILESTONE: Build to activities and transition to Integration Testing,
###16
Test User Acceptance Testing and Non-Functional
Testing
The purpose of this deliverable is to formally
close the sprint by conducting the Sprint
###17 Sprint Closing Review Meeting with key users, product owner
group and key stakeholders; formally sign-off
the results and conduct sprint retrospective.
The purpose of this task is to demonstrate the
results of the sprint to product owner team, key
users and key project stakeholders. The results
of the demo is either acceptance of backlog
Conduct Sprint Review item or in cases the feature is not accepted the
###17###
Meeting user story is amended by the product owner
team, prioritized and remains in the product
backlog ready for next sprint planning meeting.
The demo in sprint review meeting serves as an
input to formal sign-off for the sprint.
acceptance and signoff of the sprint results
following the sprint review meeting. The product
owner team is the party that provides the sign-
###17###Signoff Sprint Results off to the project team. In case some features
are not accepted they are brought back into the
product backlog as requirement, properly
The purpose
prioritized andofincluded
this taskinisplanning
to conduct
for next
retrospective meeting with the SCRUM team to
Conduct Sprint
###17### team to adjust to changing project environment
Retrospective
added to the product backlog, prioritized and
The purpose
tracked alongofwith
theother
preliminary cutover plan
user stories.
deliverable is to document the strategy, scope
Preliminary Cutover Mand Production
###18 and timelines for moving from the as-is solution
plan atory Cutover Plan
to the to-be solution and the hyper care period
immediately following go-live.
Conduct Organizational The purpose of this task is to assess to what Business
Optio
###18###Change Management level the organization is prepared for the cut Readiness
nal
Readiness Check over/transition Approach
Conduct Production This purpose of this task is to check to what

###18###Support Readiness extent the support organization is operational
Check and ready for cut over
Conduct Master Data

This task checks that proper governance of
###18###Process Governance
master data quality is defined.
Readiness Check The purpose of the preliminary cutover plan
task is to document the strategy, scope and
timelines for moving from the as-is solution to
the to-be solution and the hyper care period
immediately following go-live. This includes
documenting activities such as the transfer of
Prepare Preliminary
###18### data from the legacy systems to the SAP
Cutover plan
software production system, setting up and
initializing the production system, closing the
legacy systems, manually entering certain data
in the new system, setting up and verifying
interface connections, importing transports and
all manual
The purpose configurations.
of the review of the preliminary
cutover plan is to validate the plan for
Review Preliminary
completeness, dependencies, timing and other
###18###Cutover Plan with
constraints. At the end of the review the project
customer
team will have understanding of necessary
adjustments to the preliminary cutover plan.
The purpose of this task is to refine the
Refine Preliminary preliminary cutover plan based on information
###18###
Cutover Plan the project team learned in the cutover plan
review with customer.
The purpose of Approved Integration Test is to
ensure functional correctness. It test the
Test Strategy
Approved Integration integration of SAP solutions with non-SAP Mand
###19 Plans &
Test applications and interfaces and can be atory
Results
executed in an iterative manner.
The purpose of this task is to define and
document integration test cases, end-to-end
Prepare Integration Test
customer business process scenarios,
###19###Plan, including test of
according to the test plan. Test plans and test
roles and authorizations
case documentation is stored in Solution
Manager.
Prepare and document The purpose of this task is to document the
###19###Integration Test Case integration test case outlined in the integration
#1 - n test plan
The objective of this task is to perform the
Integration test according to previously defined
Execute Integration Test
###19### plan. During the test all issues must be logged
Case #1 - n
and documented in the system for traceability
purpose.
Perform defect issues identified during the Integration Test. It is
###19###resolution for crucial that the issues are re-tested by users
Integration Test that reported them (or designated re-testers)
and that they are confirmed.
Obtain Integration Test The purpose of this task is to obtain customer
###19###
Results Sign-off approval (sign-off) of the integration test.
deliverable is to develop, implement, and test
the data migration programs and processes
defined in the business blueprint phase. This
activity consists of iterative development and
testing cycles focused on the analysis of data,
refinement of business rules, and deployment
of migration programs and processes designed Data
Mand
###20 Legacy Data Migration to move, cleanse, transform, and enrich legacy Migration
atory
data required to support the various test cycles Design / Plan
and ultimately the production cutover. The test
cycles enable the migration team to improve
data quality to an acceptable production level,
develop a detailed cutover sequencing plan,
and exercise data reconciliation and validation
processes required to support the production
The purpose of this task is develop the specific
architecture, programs, and processes that
Develop Data Migration
###20### support the extraction, validation,
Program Units
harmonization, enrichment, and cleansing of
the
Thelegacy
purposedata.
of this task is to execute and
Execute and validate
###20### validate the manual conversion as described in
Manual Data Migration
the manual data migration approach
Obtain Data Quality The purpose of this task is to visualize the data
###20###
Reports quality metrics defined in the data quality plan
The purpose of this task is to load the cleansed
Perform SAP Target legacy data into the SAP software target
###20###
Load Test structures using a standard SAP load utility
such as LSMW.
The purpose of this task is to obtain the results
Obtain Data Migration of the various test cycles so the team can Mand Test cases &
###20###
Test Results monitor the accuracy and efficiency of the data atory Results
migration
The purposesolution.
of this task is to provide one final
Conduct Final Data assessment at the end of the realization phase Mand Test cases &
###20###
Quality Assessment to report on the quality of the converted legacy atory Results
data
the User acceptance test (UAT). This is the last
Approved User Mand Testplans &
###21 test cycle of an SAP solution implementation
Acceptance Test atory Results - UAT
and is an essential part of gaining end-user
acceptance of the software system.
The purpose of this task is to define and
Prepare UA Test Plan document UAT test cases according to the test
###21###
for <SCOPE OPTION> plan. Test plans and test case documentation is
stored in Solution Manager
Prepare and Document
User Acceptance Test
###21### integration test case outlined in the UAT test
Cases for <SCOPE
plan
OPTION>
The objective of this task is to perform the End
User Acceptance test according to previously
Execute UA Test Plan
###21### defined plan. During the test all issues must be
for <SCOPE OPTION>
logged and documented in the system for
traceability purpose.
Perform UA Defect issues identified during the User Acceptance Testplans &
Mand
###21###Resolution for <SCOPE Test. It is crucial that the issues are re-tested by Results -
atory
OPTION> users that reported them (or designated re- Regression
The purpose of this task is to execute the
Obtain UA Test Results
###21### testing, document the results and obtain
Sign-off
customer approval (sign-off)
The purpose of the SAP data archiving
deliverable is to provide a method to check,
remove, and store data that has completed its
lifecycle within the solution. Data that meets the
check criteria of data retention rules and is no
###22 SAP Data Archiving longer actively used in the system can be
archived and deleted. Storage of the data is a
secondary process to enable data that has
been archived and deleted to still be viewed
and reported on even though the data is no
The purpose
longer stored of
onthis
thetask is to identify
transactional legal and
system.
Capture Legal and
business retention requirements needed in prier
###22###Business Retention
to establish the baseline for data arched and
Requirements
removal plan.of this task is to develop the data
The purpose
Prepare Data Archive archive plan that outlines the planning for data
###22###
Plan archiving of the business objects at the
customer site.
The purpose of this task is to develop the data
archive storage plan needed for the execution
Prepare Data Archive
###22### of each data archive run and creates the
Storage Plan
indexes for each archive execution.
Conduct Data Archive The purpose of this task is to test the data
###22###
Implementation Test archive implementation execution in QAS.
The purpose of the production infrastructure
and environment design and setup deliverable Solution
Production Environment Mand
###23 is to install a viable, correctly configured Landscape
(PRD) atory
technical production environment to support Design
productive operations of the delivered solution.
Execute Technical
Installation of SAP The purpose of this task is to install and set up
###23###
Products for PRD the production environment.
Environment
Execute Technical
Upgrade of SAP The purpose of this task is to upgrade the
###23###
Products for PRD production environment.
Environment
Import Configuration The purpose of this task is to build the
and Development production (PRD) environment with changes
###23###
Objects to PRD that have been tested and released from the
Environment quality assurance (QA) environment.
Set up Role assignment

/ Authorizations / Test The purpose of this task is to set up users in
###23###
Users in PRD for the production environment.
<SCOPE OPTION>
Populate PRD with Test The purpose of this task is to ensure that
###23###Master Data for appropriate master data is available for testing
<SCOPE OPTION> in the production environment (system test).
Prepare and Load
master data into PRD
###23### data required for all business processes in
environment for
PRD.
<SCOPE OPTION>
Perform Manual
The purpose of this task is to perform any
Configuration Settings
###23 7 remaining manual configuration changes in the
in PRD for <SCOPE
production environment.
OPTION>
Failover
The purpose of this deliverable is to execute Environment
Optio
###24 Failover Environment the setup of Availability and Continuity Design,
nal
Management (ACM) Setup and
Test Results
Prepare Failover The purpose of this task is to define the
###24###Environment Design approach and plan for Availability and
and Plan Continuity Management.
Set-up Failover
Environment and The purpose of this task is to set and execute
###24###
Execute Identified the identified failure scenarios.
Scenarios
The purpose of this task is to obtain the results
Obtain Failover
from the failover scenario execution and
###24###Environment Test
determine the appropriate mitigation actions for
Results
the test findings.
The purpose of planned Performance and
System Test is to checks the entire system,
System and consisting of databases, applications servers, Mand Test Plans &
###25
Performance Test front ends, printers etc. The performance test atory Results
measures the throughput and response times
of the system.
The task defines and documents the identified
Prepare System Test
###25### test cases related to system and performance
Plan
test. Outcome is documented in a test plan.
The task defines and documents the identified
Prepare Performance
###25### test cases related to system and performance
Test Plan
test. Outcome is documented in a test plan.
Prepare System Test The purpose of this task is to document the test
###25###
Cases case outlined in the test plan
Prepare Performance The purpose of this task is to document the test
###25###
Test Cases case outlined in the test plan
The purpose of this task is to execute the
Execute Performance performance tests and present the findings for
###25###
Tests these tests. The outcome should be formally
approved by the customer.
The objective of this task is to resolve issues
Perform Performance identified during the performance or load
###25###
Test Defect Resolution testing. Upon resolution the issues need to be
re-tested and confirmed by responsible testers.
Obtain Test Results The purpose of this task is to obtain customer
###25###
Sign-off approval (sign-off)
The purpose of this service is to support the
start of production of an SAP Solution. During
this service, SAP service engineers check the
Optio SAP Going
###26 SAP Going Live Check solution for potential risks and give
nal Live Check
recommendations ensuring optimal
performance and system availability for core
business processes.
The purpose of this task is to perform the first
session of the SAP GoingLive Check.
The service consiste of two sessions - Analysis
Perform SAP Going and Verification, and includes:
Live Check - Analysis - Verification of the technical capabilities of the
###26###
Session and schedule production environment (sizing plausibility)
the Verification Session - Check of system configuration (database,
system components)
- Check of version and release compatibility of
all involved SAP components and Plug-Ins
System User
Roles and
Authorization
The purpose of the System User Roles and Administratio
System User Roles and
Authorization Administration deliverable is to Optio n
###27 Authorization
establish an effective operation processes for nal and
Administration
security System
Authenticatio
n
Management
Set up administrative The purpose of this task is to set-up, document

###27###procedures for Roles and execute the administrative procedure for
and Authorizations Roles and Authorizations.
The purpose of the technical operations and
Technical
handover strategy deliverable is to update
Operations
Technical Operations refine two prior deliverables from the Business Optio
###28 and
and Handover Plan Blueprint phase, and prepare a strategy to hand nal
Handover
off operations of the solution landscape to the
Strategy
post-production support organization.
Validate Support The purpose of this task is to ensure that
###28###Center/Help Desk proper staffing(people and competence) is in
Staffing Strategy place for the support org/team
The purpose of this task is to ensure that

Establish Support
###28### adequate support processes are in place for the
Processes
Go Live phase and beyond.
This task describes the considerations that are

Set-up Business
###28### required to recognize and solve critical
Process Monitoring
situations during business process operation.

deliverable is to:
Delivery of
projects
Mand Results
atory Delivery
Acceptance
Protocol
Customer References
Management Gate nal
from earlier stages of the project.
Quality Gate by conducting a quality check at
Quality Gate are:
Gate(s)
project expectations and monitor customer
The purpose of Project Management Review is
to provide a proactive quality assurance review,
Conduct Project
with an impartial analysis of all aspects of the
###29###Management Review
project – across all project management
Service
disciplines, enabling early detection of project
Review of SAP Solution service that provides a
proactive quality assurance review of the
design of the SAP solution which is being
Conduct Design Review implemented. It delivers an impartial analysis of
###29###
Service all aspects of the solution design – across all
relevant design perspectives – and leads to an
early detection of potential solution risks and
offers actionable risk mitigation
Manage Fulfilled
###29### specified in the contractual arrangement was
Contracts
were accepted.
approval (sign-off)
Completion
This milestone concludes testing activities and
MILESTONE: Test to
###30 start of deployment of the functionality to
Deployment The purpose of the final preparation phase
Production Environment
is to finalize readiness of the solution and
its supporting tools and processes for
production go live. This includes, but is not
limited to, system tests, end-user training,
system management, and cutover activities
### Final Preparation
(including data migration). The phase
deliverables also serve to enable the
resolution of all crucial open issues. On
successful completion of this phase, the
business is ready to run the live SAP
The purpose
software of the phase initiation deliverable
system.
phase starts.
Project
Schedule
milestones)
the approach for the specific project phase.
statement.
###2
The purposelevel
of control. Project
###2### Management
Plan(s)
projects change
The purpose management
of this process.
activity is to assure that the
###2###
plan.
Monitor and control
project activities
expected.
Risk List
(internal &
external),
###2### Project
Change log,
Project
Issues log
Project
external
The purpose of this survey is to take the pulse
of the organization, prior to go-live, to determine
the general comfort level with the upcoming
Organizational and changes. If that comfort level is not there, it is
###3 Production Support critical to determine where additional OCM work
Readiness Check needs to be focused. In addition the check of
production support readiness is to ensure that
the resources and processes are in place to
support the solution after cutover.
Functional/Te
chnical
The purpose of this task is to validate the
Requirements
Perform Business outcome of the role mapping and change
Optio and
###3###validation and impact analysis. This is done with the impacted
nal Production
Transition Planning business stakeholders in order to gain sponsors
Support
approval.
Processes
Defined
Validate that Master Master Data

Data Support Optio Support
###3### customer establishes the means to manage
Processes is nal Processes
their data in an integrated environment.
established Established
This task provide a single defined support
approach for monitoring and measuring the
customer’s day-to-day support operations. The
following four topics needs to be covered:
- Exception Handling and Business Process Business
Establish Business Optio
###3### and Interface Monitoring Process
Process Operations nal
- Data Volume Management Operation
- Job Scheduling Management
- Transactional Consistency and Data Integrity
This task describes how all SAP technologies

Establish System can be administered to run a customer solution System
Optio
###3###Administration and efficiently. The execution is mainly done locally Administratio
nal
Control but can be triggered and managed from a n and Control
central administration system.
Security /
Establish Security / The task ensure that the customer establishes
Optio Role and
###3###Role and Authorization the means to manage security, roles and
nal Authorization
Management authorizations in their productive environment.
Management
The purpose of this task is to extract the
knowledge about the scope, customizations,
Execute Transition to Optio Transition to
###3### and business processes of the customer’s
Production Support nal Support
production environment and transfer that
knowledge to a long-term SAP support center
The purpose of the EU training delivery and
readiness checklist is to provide a checklist
summarizing end-user training delivery to
Pre Go-Live End-User ensure readiness for adoption of the solution. In
###4
Training Delivery the checklist, items governing training delivery,
communications, and future planning clarify the
status of all aspects of the training initiative.
Validate and adapt end

The purpose of this task is to prepare the
###4###user training material
training delivery.
developed
The objective of this task is to deliver end user
Deliver End User
###4### training to identified end user groups according
training
to the previously developed training schedule.
The purpose of this task is to capture feedback
Collect Training Optio Training
###4### on both the training session and the trainer
Evaluations feedback nal Evaluations
delivering the material
End User
This task checks how prepared the people in Training
Perform People Optio
###4### the organization are with regards to the Delivery and
Readiness assessment nal
identified changes and received EU training. Readiness
Checklist
The purpose of this deliverable is to present the
findings and recommendations from the results
of technical tests such as disaster recovery
Approved Technical
###5 tests, backup and restore tests, and other
System Tests
required technical or basis-related tests to the
customer or project team for final signoff in
order to exit system testing.
The purpose of this task is to prepare and
Execute Technical
###5### execute the system tests. The outcome/results
System Tests
should be approved by the customer.
The objective of this task is to resolve issues
Perform System Test identified during the system testing. Upon
###5###
Defect Resolution resolution the issues need to be re-tested and
confirmed by responsible testers.
Obtain System Test Purpose of this task is to obtain customer
###5###
Results Sign-off approval (sign-off)
The purpose of production cutover is to perform
the cutover to the production software and go
###6 Production Cutover live. At this point, the organizational, business,
functional, technical, and system aspects of the
project are ready to be used in production.
The purpose of this task is to rehearse or
simulate the cutover activities. During
Execute Go Live Mand Testplans &
###6### simulation, the main objective is to validate and
Simulations 1 thru N atory Results
document the tasks, sequence, and duration of
items on the cutover plan.
Data
Conduct Data Quality This task verifies that master data support is set Mand
###6### Migration
Readiness Check up and process is operational atory
Design / Plan
The purpose of this task is to complete the Cut

Mand Production
###6###Finalize Cutover Plan Over plan with results obtained from the Go
atory Cutover Plan
Live simulations.
The objective of this task is to perform all the
cutover preparation activities remaining to be
Perform Pre-Cutover
closed prior to cutover weekend. The detailed
###6###Weekend Closing
cutover plan contains the complete listing of all
Activities
pre-cutover activities, their dependencies,
owners, and timing.
Final Check of
Readiness for
Production Readiness This task will confirm that the productive system Optio
###6### Cutover -
and Sign-Off for is ready for Go Live. nal
Signoff
The purpose of this task is the loading of
production data from legacy systems into the
Perform Cutover production environment. Once all preparations
Weekend Activities and configurations on both the technical and
###6###
including Final application levels are completed, the final
Production Data Load productive solution can be set up and data
loaded. The solution is live in a production
environment
Obtain Production Data Purpose of this task is to obtain customer Mand Production
###6###
Load Sign-off approval (sign-off) atory Cutover Plan
Solution
Purpose of this task is to hand over the
Manager
Initiate Solution finalized implementation project and it's
Optio Update,
###6###Manager Update - content, and set up as a productive solution in
nal Solution
Solution Documentation SAP Solution Manager. This provides the basis
Documentatio
for the follow up activities in the Run Phase.
n
The purpose of this deliverable is to formally
###7 Release Closing close the release and prepare for next release
and/or sprint planning
The purpose meeting.
of this task is to 'groom' the
product backlog. Product Owner Team needs to
detail the user stories to ready them for next
Prepare Product
release/sprint planning meeting. The stories
###7###Backlog for Next
need to meet definition of Ready for Build so
Release/Sprint
they are understood by the SCRUM team and
can be estimated during the sprint planning
The purpose of this task is to conduct
meeting.
retrospective meeting with the project team to
Conduct Release
###7### team to adjust to changing project environment
Retrospective
added to the product backlog, prioritized and
tracked along with other user stories.
The purpose of this task is to update the
Release and Sprint Plan according to changed
Update the Release priorities and focus of the team. It is
###7###
and Sprint plan accountability of Product Owner to maintain the
Release and Sprint plan and keep it current
during the project.
deliverable is to:
Delivery of
projects
Mand Results
atory Delivery
Acceptance
Protocol
Customer References
Management Gate nal
from earlier
Quality Gate are:
Gate
Conduct Project
Service
Manage Fulfilled
Contracts
were accepted.
The purpose of this task is to obtain customer
approval (sign-off)
Completion
This milestone signifies formal transition to
MILESTONE: production environment. Production is up and
###9
Production System Live running, cutover sustainment activities, end-
user on-boarding and support are under way.
The purpose of this phase is to provide
support for the solution during the period
immediately following production cutover.
Exceptional items such as additional
production support, exceptional business
monitoring processes, and extraordinary
technical support are planned and executed
### Go Live Support
in this phase. At the end of the designated
extra-care period, sustaining production
support processes planned in final
preparation and executed as part of go-live
support become the core support for
continuous improvement in the ongoing
The purpose of the phase initiation deliverable
solution.
phase starts.
Project
Schedule
milestones)
The purpose of
the approach forthis
thedeliverable is to execute
specific project phase.
statement.
###2
The purposelevel
of control. Project
###2### Management
Plan(s)
projects change
The purpose management
of this process.
activity is to assure that the
###2###
plan.
Monitor and control
project activities
expected.
Risk List
(internal &
external),
###2### Project
Change log,
Project
Issues log
Project
external
The purpose of EU training during go-live
support is to ensure that end users have Go-Live
Post Go live End-User Optio
###3 adopted the solution, knowledge resources are Training
Training nal
maintained, and responses to the end-user Sessions
acceptance survey are positive.
Prepare End-User This purpose of this task is to adapt available
###3###Training for <SCOPE training material and make it suitable for End
OPTION> User training.
Deliver End-User This task executes the delivery of EU training
###3###Training for <SCOPE as well as capturing feedback on both the
OPTION> training session and the trainer.
The purpose of this task is to capture feedback
Collect Training
###3### on both the training session and the trainer
Evaluations feedback
delivering the material
This task checks how prepared the people in
Perform People
###3### the organization are with regards to the
Readiness assessment
identified changes and received EU training.
The purpose of the production support and
transfer to solution deliverable is to confirm that
SAP Going Live Check the resources and processes are in place to
###4
- Verification Session support the ongoing solution and to complete
the steps required to close the project and
Conduct SAP Going The purpose of this task is to verify that the
###4###Live Check - Verification requirements identified in earlier sessions are
Session Remote met.
The purpose of the production support and Support

transfer to solution deliverable is to confirm that Process
Production Support the resources and processes are in place to Optio Enabled,
###5
After Go Live support the ongoing solution and to complete nal Governance
the steps required to close the project and Model for
finish documentation. Operations
The purpose of this task is to implement
Provide Post Go Live ongoing production support to the SAP software
###5###
Support system users and to monitor and optimize
system performance.
Monitoring Open Issues
###5### closure of all open project issues which is a
to Resolution
prerequisite for the final project closure.
functional issues identified during the hyper
Resolve Functional
###5### care period after cutover. It is crucial that the
Issues
issues are re-tested and confirmed by users
that reported them.
technical issues identified during the hyper care
Resolve Technical
###5### period after cutover. It is crucial that the issues
Issues
are re-tested and confirmed by users that
reported them.
Transition to
The purpose of this task is to ensure knowledge Standard
Complete Transition to transfer regarding the scope, customizations, Support
Optio
###5###Customers Production and business processes in the customer’s Processes,
nal
Support organization production environments to the long-term SAP System
support center team. Administratio
n and Control
Solution
Purpose of this task is to hand over the
Manager
Finalize Solution finalized implementation project and it's
Optio Update,
###5###Manager Update - content, and set up as a productive solution in
nal Solution
Solution Documentation SAP Solution Manager. This provides the basis
Documentatio
for the follow up activities in the Operate Phase.
n
Obtain Solution
Transition to Production Purpose of this task is to obtain customer
###5###
Acceptance Protocol approval (sign-off)
Sign-off
This milestone signifies formal transition from
MILESTONE: Deploy to post production sustainment support to long
###6
Run term support and operation of the new
environment
deliverable is to:
Delivery of
projects
Project Closure and this phase and the project are complete and
Mand Results
###7 Sign-Off Project accurate, and close any outstanding issues
atory Delivery
Acceptance
Protocol
Customer References
Management Gate nal
from earlier
Quality Gate are:
Gate
Conduct Project
Service
Manage Fulfilled
Contracts
were accepted.
Resolve and close open
###7### closure of all open project issues which is a
issues
prerequisite for the final project closure.
The purpose of this activity is to document the
Finalize Project results of the project, both regarding achieved
###7###
Closeout Report objectives, deliverables as well as adherence to
schedule, costs and delivered value.
The purpose of this activity is to formally close
Obtain Sign-off for
the project by obtaining customer signatures on
###7 7 Project Closure and
dedicated deliverables/documents e.g. Project
Results Acceptance
Quality Gate, Project Closeout Report
MILESTONE: Project This milestone marks official closure of the
###8
Complete project
Solution operations are initially set up
during the implementation project. The
primary goal of this phase is to further
optimize and automate the operability of the
solution. Operability is the ability to
### Operate
maintain IT systems in a functioning and
operating condition, guaranteeing systems
availability and required performance levels
to support the execution of the enterprise’s
business operations.
The Operations Maturity Assessment evaluates
Operations Maturity
###1 the SAP customer's support operations to
Assessment
determine areas in need of optimization
Perform evaluation and The purpose of this activity is to assess

assessment of business and technical requirements for
###1###operations capabilities, operations and to define what aspects of the
including CoE operations need to be adjusted, enhanced or
operational set up implemented.
The report should detail assessment results
Prepare Maturity
###1### and finding, including proposed actions for how
Assessment Report
to bridge identified gaps.
Centrally document and relate business
Solution
processes and technical information of SAP
###2 Documentation
and non-SAP Solutions ensuring transparency,
Optimized
efficient maintenance and collaboration
Re-visit result of ALM roadmap workshop from
Perform assessment of the project preparation, lessons learned
###2###Solution Documentation findings from the implementation project and
set up determine if potential gaps exist for the Solution
Documentations area.
Represents the identification, adaptation and
implementation of new and enhanced future-
proof business and technical scenarios
Solution Is a part of the application lifecycle and is
###3 Implementation designed to decouple technical installation from
Optimized business innovation
Uses the SAP Solution Manager to implement
the innovation in the system landscape

###3###Solution Implementation findings from the implementation project and
set up determine if potential gaps exist for the Solution
Implementation area.
The template management approach allows
customers with multi-site SAP installations to
efficiently manage their business processes
Template Management
###4 across geographical distances – from initial
Optimized
template definition to template implementation
and template optimization, for example as part
of a global
Re-visit rollout
result of ALM roadmap workshop from
###4###Template Management findings from the implementation project and
set up determine if potential gaps exist for the
Template Management area.
Functional and performance testing of SAP-
Test Management centric business processes to ensure validated
###5
Optimized system behavior after software change events

###5###Test Management set findings from the implementation project and
up determine if potential gaps exist for the Test
Management area.
Workflow-based management of business and
technology-driven changes, with integrated
project management and synchronized
deployment capabilities.
Standardized process leading to improved
Change Control reliability of solution and minimized risk through
###6
Management Optimized segregation of duties and transparency of
changes
Efficient solution management – all project and
system information is saved in SAP Solution
Manager
###6###Change Control findings from the implementation project and
Management set up determine if potential gaps exist for the Change
Control Management area.
and issue message processing in multiple
organization levels
Offers a communication channel with all
relevant stakeholders of an incident. The
process includes business user, SAP
experts@customer, SAP Service&Support and
Application Incident Partner Support employees.
###7
Management Optimized Is integrated in all ALM processes of SAP
Solution Manager, in any SAP Business Suite
solution and could be connected to an Non-
SAP Help Desk application
Includes follow up activities as knowledge
research, root cause analysis or Change
Management
###7###Incident Management findings from the implementation project and
set up determine if potential gaps exist for the Incident
Managementallarea.
Represents capabilities for monitoring,
alerting, analysis and administration of SAP
solutions
Allows customers to reduce TCO by predefined
Technical Operations content and centralized tools for all aspects of
###8
Optimized operations in SAP Solution Manager
Provides End-to-End reporting functionality
either out-of-the-box or individually created by
customers
###8###Technical Operations findings from the implementation project and
Technical
SAP Operations
Business Processarea.
Integration &
Automation Management (BPIAM) comprises
the most important application related
Business Process operations topics necessary to ensure the
###9
Operations Optimized smooth and reliable flow of the core business
processes to meet a company's business
requirements.
###9###Process Operations set findings from the implementation project and
up determine if potential gaps exist for the Process
Operations area.
SAP Notes provide a solution for known issues.
SAP Notes are usually applied upon request
(e.g. current incident in productive environment,
information from SAP about potential issue (Hot
Maintenance News, Security Notes)).
###
###
Management Optimized SAP Notes are collected and released as
Support Packages. Support Packages are
applied to SAP solutions to comply with legal
requirements or run on latest technology.
###
###
###Maintenance findings from the implementation project and
Management set up determine if potential gaps exist for the
Maintenance
implementation Management
of new and area.
enhanced business
and technical scenarios
Uses the SAP Solution Manager to manage the
upgrade project holistically and effectively end-
Upgrade Management to-end
###
###
Optimized Allows SAP customers to better understand and
manage the major technical risks and
challenges in an upgrade project, and to make
the upgrade project a “non-event for the
business.”
###
###
###Upgrade Management findings from the implementation project and
Upgrade Management area.
Accountabl
Work Stream
e Role
_Phase
PM - Project
Management
PM - Project Project
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
OCM -
Organizational Project
Change Manager
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
PM - Project Application
Management Manager
Management Manager
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
ALM -
Application
Lifecycle
Management
Management Manager
ALM -
Business
Application
Consultant
Lifecycle
Management
ALM -
Business
Application
Consultant
Lifecycle
Management
ALM -
Application Application
Lifecycle Consultant
Management
Test
ISM - Test Managemen
Management t Consultant
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
ALM -
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
Training -
Training
Education
Training -
Consultant
Training
Training -
Training
Management Manager
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
VM - Value
Management
Business
VM - Value
Consultant
Management
Business
VM - Value
Consultant
Management
BPM - Business
Process
Management
BPM - Business Business

Process Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
ISM - Test
Management
ISM - Test Technology

ISM - Test Project

Management Manager
DM - Data
Migration
DM - Data Application
Migration Consultant
DM - Data Technology
Migration Architect
Migration Architect
TSM - Technical
Solution
Management
TSM - Technical
Solution
Solution
Architect
Management
TSM - Technical
Technology
Solution
Architect
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Architect
Management
TSM - Technical
Solution
Management
TSM - Technical
Solution
Solution
Architect
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
PM - Project
Management
Management Manager
PM - Project Business
Management Manager
Management Manager
Management Manager
_Milestone
_Phase
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
OCM -
Education
Organizational
Consultant
Change
Management
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
Training -
Training
Education
Training -
Consultant
Training
Education
Training -
Consultant
Training
Training -
Training
Business
Training -
Consultant
Training
Training -
Instructor
Training
Training -
Training
Education
Training -
Consultant
Training
Education
Training -
Consultant
Training
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
VM - Value
Management
Business
VM - Value
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Project
Process
Manager
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Project
Process
Manager
Management
DM - Data
Migration
DA - Data
Archiving
DA - Data Technology
Archiving Architect
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Architect
Management
BPM - Business
Technology
Process
Architect
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
ISM - Test
Management



PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
_Milestone
_Phase
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
Management Manager
Management Manager
OCM -
Business
Organizational
Consultant
Change
Management
Training -
Training
Education
Training -
Consultant
Training
Training -
Training
Education
Training -
Consultant
Training
Education
Training -
Consultant
Training
Education
Training -
Consultant
Training
Training - Education
Training Coordinator
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Process
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
Integration
BPM - Business
Developmen
Process
t Consultant
Management
BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management
VM - Value
Management
Business
VM - Value
Consultant
Management
ISM - Test
Management
ISM - Test Application



TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
_Milestone
PM - Project
Management
Management Manager
Management Manager
Management Manager
CutOver - Cut
Over
Management
OCM -
Change Manager
Management
OCM -
Change Manager
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Project
Over
Manager
Management
CutOver - Cut
Project
Over
Manager
Management
ISM - Test
Management





DM - Data
Migration
Migration Architect
ISM - Test
Management




ISM - Test Project

Management Manager
DA - Data
Archiving
DA - Data Technology
Archiving Architect
DA - Data Application
Archiving Consultant
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Application
Solution
Consultant
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Architect
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
ISM - Test
Management



Test
ISM - Test Managemen
Management t Consultant


TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Solution
Management
TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management
BPM - Business
Technology
Process
Consultant
Management
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
_Milestone
_Phase
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
OCM -
Organizational
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management
ALM -
Application Technology
Management
ALM -
Management
TSM - Technical
Technology
Solution
Consultant
Management
ALM -
Management
Training -
Training
Education
Training -
Consultant
Training
OCM -
Education
Organizational
Consultant
Change
Management
ISM - Test
Management



CutOver - Cut
Over
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Project
Over
Manager
Management
CutOver - Cut
Technology
Over
Consultant
Management
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
_Milestone
_Phase
PM - Project
Management
Management Manager
Management Manager
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Training -
Training
Education
Training -
Consultant
Training
Education
Training -
Consultant
Training
OCM -
Education
Organizational
Consultant
Change
Management
TSM - Technical
Solution
Management
CutOver - Cut
Technology
Over
Consultant
Management
CutOver - Cut
Over
Management
CutOver - Cut
Technology
Over
Consultant
Management
CutOver - Cut
Project
Over
Manager
Management
CutOver - Cut
Application
Over
Consultant
Management
CutOver - Cut
Technology
Over
Consultant
Management
ALM -
Management
ALM -
Management
Management Manager
_Milestone
PM - Project
Management
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
Management Manager
_Milestone
_Phase
PM - Project
Management
Business
PM - Project
Consultant
Management
Management Manager
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM - Test
Application Managemen
Lifecycle t Consultant
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
ALM -
Application
Lifecycle
Management
ALM -
Management
WBS # WBS item title
1 Project Preparation
1 1 Project Initiation
Allocate Resources - hard booking with resource

1 1 1
management
1 1 2 Prepare Team Onboarding Document
Communicate the delivery model and made mobility

1 1 3
arrangements
1 2 Project Governance
1 2 1 Define Project Organization
1 2 2 Assign Roles and Responsibilities
1 2 3 Complete communication management plan
1 3 Project Charter
1 3 1 Prepare Project Charter Document
1 3 2 Identify Stakeholders
1 3 3 Obtain Project Charter Sign-off
1 4 Kick-Off Workshop
1 4 1 Prepare for Kickoff Meeting

1 5 Scope Statement
1 5 1 Review Scope Statement with Customer
1 5 2 Refine Acceptance Criteria
1 6 Project Schedule and Budget
1 6 1 Develop delivery schedule and assign resources
Define Initial Release and Sprint schedule, Assign

1 6 2
Resources
1 6 3 Include key workshops into the project schedule

1 6 4 Obtain Customer sign-off for project schedule
1 6 5 Establish Cost and Schedule baseline
1 7 Project Management Plan

1 7 1 Prepare Project Management Plan
1 8 Project and Operational Standards
1 8 1 Determine Solution Documentation Procedure
1 8 2 Determine Solution Implementation Procedure
1 8 3 Determine Test Management Procedure
1 8 4 Determine Change Control Management Procedure
1 9 Execution, Monitoring, and Controlling of Results

1 9 4
stakeholders
1 10 Organizational Change Management Roadmap

Prepare Organizational Change Management
1 10 1
Roadmap
1 11 Project Training Strategy and Plan (team + key-users)
1 11 1 Prepare training strategy and plan document
1 12 1 Conduct Solution Training and knowledge transfer
1 13 Business Process Map
1 13 1 Prepare Business Process Map
1 13 2 Validate and Complete business process map
1 14 Data Migration Approach and Strategy
Prepare Data Migration Scope and Requirements

1 14 1
Document
Complete the Data Migration approach and strategy

1 14 2
document
Technical Requirements and Design and Solution

1 15
Landscape Deployment Plan
1 15 1 Define Solution Landscape Concept
1 15 2 Define Solution Deployment Concept
1 16 Interface Inventory
1 16 1 Prepare Interface Inventory document
1 17 Initial Hardware Sizing Proposal
1 17 1 Complete HW sizing estimation for solution landscape
1 18 Project Support Tools and System Setup
Verify Technical System Requirements (frontend /

1 18 1
backend)
1 18 2 Validate connectivity to Cloud provider
1 18 3 Install or Upgrade SAP Solution Manager
Check connectivity of SAP Solution Manager to Cloud

1 18 4
environment
Set up Business Process Hierarchy in SAP Solution

1 18 5
Manager
1 18 6 Confirm availability of Solution Builder

Install SAP Best Practices solution builder content
1 18 7
add-on, installation data and solution file
Setup of project logistics and infrastructure, including

1 18 8
team collaboration environment
Prepare authorization roles in the systems for the

1 18 9
project team (DEV)
1 19 Demo Environment
Pre-Assembled Rapid Deployment Solution installed

1 19 1
in customer landscape
Perform unit test of the Pre-Assembled Rapid
1 19 2
Deployment Solution
Perform post activation tasks related to the Pre-

1 19 3
Assembled Rapid Deployment Solution
1 21 MILESTONE: Project Start to Design
2 Scope Validation

2 2 3 Conduct SCRUM Meetings

2 2 6
stakeholders
2 3 Stakeholder Analysis
2 3 1 Conduct classification of project Stakeholders
2 3 2 Identify Key Users
2 4 Change Impact Analysis

2 4 1 Validate organizational alignment approach
2 4 2 Establish Baseline of Current State
2 5 End User Training Strategy and Plan
2 5 1 Conduct Learning Needs Analysis
2 5 2 Develop Detailed End-User Training Plan
2 6 1 Conduct Blueprint Ramp-up Training
2 7 Scope Validation
For <General Settings #1 - n> - Conduct Validation

2 7 1
and Fit-gap Analysis
For <Scenario #1 - n> - Conduct Validation and Fit-

2 7 2
gap Analysis
For <Process #1 - n> - Conduct Validation and Fit-gap
2 7 3
Analysis
Validate pre-defined RICEFW Objects (reports, forms

2 7 4
etc.)
2 7 5 Determine Gap list and effort estimation
2 8 Legacy Data Migration (Cycle #1 - n)
2 8 1 Define Automated Data Migration Approach
2 8 2 Define Manual Data Migration Approach
2 9 User Access and Security
2 9 1 Authorization Requirements and Design
Pre-Assembled Rapid Deployment Solution Transfer

2 10
into Development Environment (DEV)
Perform transfer of Image from demo environment to

2 10 1
On-premise
2 10 2 Install Solution Documentation in Solution Manager
Validate Role assignment / Authorizations / Test Users

2 10 3
in DEV
2 11 Testing Strategy
Define Test data approach and validated pre-defined

2 11 1
master data
2 11 2 Review and Validate Testing Strategy with customer

2 13 MILESTONE: Design to Build
3 Realization
3 2 Sprint Initiation (Iterative)
3 2 1 Conduct Sprint Planning Meeting (Iterative)

3 3 1 Perform Sprint Execution Activities (Iterative)

3 3 5
stakeholders
3 3 6 Perform Scrum-Of-Scrums Meeting (Iterative)
3 4 Organizational Alignment
3 4 1 Execute Role Mapping and Transition Planning

3 5 Knowledge Transfer
For <SCOPE OPTION> - Prepare for Key User

3 5 1
Knowledge Transfer
For <SCOPE OPTION> - Perform Solution

3 5 2
Walkthrough and knowledge transfer to Key Users
3 5 3 Perform KT for delta scope
3 6 End User Training Delivery Enabled
Prepare End User Training Materials and

3 6 1
Documentation
Configured General Settings and Organizational

3 7
Structure (Cycle #1 - n)
3 7 1 Configure General Settings
3 7 2 Configure Organizational Structure
3 8 Configured Master Data Objects (Cycle #1 - n)
For <MASTER DATA OBJECT NAME> - Prepare and

3 8 1
Load Master Data
Core Configuration and Documentation - Process

3 9
(Cycle #1 - n)
Complete Core Configuration, including

3 9 1
documentation and test cases
3 10 Delta Configuration - Process (Cycle #1 - n)
3 10 1 Complete Delta Configuration
3 10 2 Complete Delta Process Documentation
3 10 3 Complete Delta Process Test Cases
3 10 4 Execute Business Process Unit and String Test Cases
3 10 5 Perform defect resolution for Unit and String Test

RDS or Predefined Service Solution Enhancements
3 11
and Extensions
3 11 1 Include RDS, PDS or Service specific task item here
Enhancement Development - RICEFW Object (Cycle

3 12
#1 - n)
3 12 1 Develop RICEFW Object #1 - n
3 12 2 Document RICEFW Object #1 - n
3 12 3 Execute Test Cases - RICEFW Object #1 - n
3 12 4 Perform defect resolution for RICEFW Object(s) Test
3 12 5 Conduct Final Code Review
3 13 Business Process Procedure
3 13 1 Develop Business Process Procedure Document

Validate and Complete Business Process Procedure
3 13 2
Document
3 14 Scenario Test (Cycle #1 - n)
3 14 1 Prepare Test Case - Scenario #1 - n

3 14 2 Execute Test Case - Scenario #1 - n
3 14 3 Resolve Issues for Scenario #1 - n
Obtain Customer Sign-off for Testing of Scenario #1 -

3 14 4
n
3 15 Quality Assurance Environment (QAS)
Execute Technical Installation of SAP Products for

3 15 1
QAS environment
Import Configuration and Development Objects to

3 15 2
QAS Environment
Set up Role Assignment / Authorizations / Test Users

3 15 3
in QAS
For <SCOPE OPTION> - Prepare and Load of Master
3 15 4
Data into QAS Environment
For <SCOPE OPTION> - Prepare and load
3 15 5
transactional data into QAS
3 15 6 Perform Manual Configuration Settings in QAS
3 16 MILESTONE: Build to Test
3 17 Preliminary Cutover plan
3 17 1 Prepare Preliminary Cutover plan
3 17 2 Refine Preliminary Cutover Plan
3 18 Approved Integration Test (Cycle #1 - n)
Prepare Integration Test Plan, including test of roles

3 18 1
and authorizations
3 18 2 Prepare and document Integration Test Case #1 - n
3 18 3 Execute Integration Test Case #1 - n
3 18 4 Perform defect resolution for Integration Test
3 18 5 Obtain Integration Test Results Sign-off
3 19 Legacy Data Migration (Cycle #1 - n)
3 19 1 Perform SAP Target Load Test

3 20 Approved User Acceptance Test (Cycle #1 - n)
3 20 1 For <SCOPE OPTION> - Prepare UA Test Plan
For <SCOPE OPTION> - Prepare and Document

3 20 2
User Acceptance Test Cases
3 20 3 For <SCOPE OPTION> - Execute UA Test Plan
For <SCOPE OPTION> - Perform UA Defect

3 20 4
Resolution
3 20 5 Obtain UA Test Results Sign-off
3 21 Production Environment (PRD)
Execute Technical Installation of SAP Products for

3 21 1
PRD Environment
Execute Technical Upgrade of SAP Products for PRD
3 21 2
Environment
Import Configuration and Development Objects to

3 21 3
PRD Environment
For <SCOPE OPTION> - Set up Role assignment /

3 21 4
Authorizations / Test Users in PRD
For <SCOPE OPTION> - Populate PRD with Test
3 21 5
Master Data
For <SCOPE OPTION> - Prepare and Load master
3 21 6
data into PRD environment
For <SCOPE OPTION> - Import of System Fast-track
3 21 7
Configuration into PRD
For <SCOPE OPTION> - Perform Manual
3 21 8
Configuration Settings in PRD
3 22 System and Performance Test (Cycle #1 - n)
3 22 1 Prepare Performance Test Plan
3 22 2 Prepare Performance Test Cases
3 22 3 Perform Performance Test Defect Resolution
3 23 SAP Going Live Check

Perform SAP Going Live Check - Analysis Session
3 23 1
and schedule the Verification Session
3 24 Technical Operations and Handover Plan
3 24 1 Validate Support Center/Help Desk Staffing Strategy
3 24 2 Set-up Business Process Monitoring
3 25 1 Conduct Project Quality Gate(s)

3 26 MILESTONE: Test to Deployment
4 Final Preparation


4 2 4
stakeholders
4 3 Pre Go-Live End-User Training Delivery
4 3 1 Deliver End User training
4 4 Approved Technical System Tests
4 4 1 Execute Technical System Tests
4 5 Production Cutover
4 5 1 Conduct Data Quality Readiness Check
4 5 2 Finalize Cutover Plan
4 5 3 Perform Pre-Cutover Weekend Closing Activities
Final Check of Production Readiness and Sign-Off for

4 5 4
Perform Cutover Weekend Activities including Final

4 5 5
Production Data Load
4 5 6 Obtain Production Data Load Sign-off

Initiate Solution Manager Update - Solution
4 5 7
Documentation
4 7 MILESTONE: Production System Live
5 Go Live Support
5 3 Post Go live End-User Training
5 3 1 For <SCOPE OPTION> - Prepare End-User Training
5 3 2 For <SCOPE OPTION> - Deliver End-User Training

5 4 SAP Going Live Check - Verification Session
Conduct SAP Going Live Check - Verification Session

5 4 1
Remote
5 5 Production Support After Go Live
5 5 1 Provide Post Go Live Support
5 6 MILESTONE: Deploy to Run
5 7 Improvement Roadmap
Perform Refinement & Improvement Planning

5 7 1
Workshops
5 7 2 Document Improvement Roadmap
5 8 Project Closure and Sign-Off Project Deliverables
5 8 3 Resolve and close open issues
5 8 4 Finalize Project Closeout Report
Obtain Sign-off for Project Closure and Results

5 8 5
Acceptance
6 Operate
6 1 Operations Maturity Assessment
Perform evaluation and assessment of operations

6 1 1
capabilities, including CoE operational set up
6 1 2 Prepare Maturity Assessment Report
6 2 Solution Documentation Optimized
Perform assessment of Solution Documentation set

6 2 1
up
6 3 Solution Implementation Optimized
Perform assessment of Solution Implementation set

6 3 1
up
6 4 Template Management Optimized
6 4 1 Perform assessment of Template Management set up
6 5 Test Management Optimized
6 5 1 Perform assessment of Test Management set up
6 6 Change Control Management Optimized
Perform assessment of Change Control Management

6 6 1
set up
6 7 Application Incident Management Optimized
6 7 1 Perform assessment of Incident Management set up
6 8 Technical Operations Optimized
6 8 1 Perform assessment of Technical Operations set up
6 9 Business Process Operations Optimized
6 9 1 Perform assessment of Process Operations set up
6 10 Maintenance Management Optimized
Perform assessment of Maintenance Management

6 10 1
set up
6 11 Upgrade Management Optimized
6 11 1 Perform assessment of Upgrade Management set up

Description Q-Gate Relevant
This phase provides initial planning and preparation for the project. Although
each project has its own unique objectives, scope, and priorities, the
deliverables outlined below assist in completing the initiation and planning
steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that a new
project exists. It supports the decision to accept the project, align stakeholders –
such as clients, customers, and SAP management – around a project and its
scope, provide updated information for planning, and obtain a commitment to
proceed. It ensures alignment between SAP, the customer’s strategic direction, and
the satisfaction of operational requirements.
The purpose of phase resources allocation is a confirmation of resource availability

for the particular phase.
The purpose of this activity is to prepare the onboarding package for external
Mandatory
consultants from SAP and partner companies.
The purpose of this task is to communicate the delivery model and ensure that the
appropriate mobility arrangements have been made for the consultants
The purpose of this deliverable is to ensure that an efficient management

framework is in place for successful project execution.
The purpose of this task is to define the organizational structure, roles and
Mandatory
responsibilities of the project team.
The purpose of this task is to identify and select global company and external
resources for the project in accordance with the required roles, skills and
responsibilities specified in the preceding task. The assignment of people to roles
should also take into account their qualifications and availability for the whole
project time frame.
The purpose of this task is to complete the communications management plan. This
document outlines the processes required to ensure timely generation, distribution,
storage, and retrieval of project information.
The purpose of this deliverable is to clearly and explicitly define the objectives of
the proposed project, analyze all possible benefits and quantify benefits in financial
Mandatory
terms. This information and supporting documents align key stakeholders around
the strategic intent of the project.
The purpose of this activity is to collect all input required for the project charter and
document it into a format suitable for both communication purpose as for formal
sign-off purpose, if possible utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the correct groupings of stakeholders
have been identified for the project.
The purpose of this activity is to achieve a formal sign-off of the project charter.
The purpose of this deliverable is to kick-off the project/phase and ensure that all
Mandatory
needed information is shared with the resources for a successful project execution.
The purpose of this task is to prepare the kickoff meeting which will helps ensure
the involvement of the team and other key resources and their commitment to the
project schedule.
The purpose of this activity is to gather the whole project team, including all
remotely involved resources, to kick-off the project or project phase. The meeting is
The purpose of this deliverable is to facilitate an initial understanding of the project

scope and associated project-related assumptions and constraints. The project
scope statement evolves through the initiation and planning of the project and
Mandatory
clearly and explicitly defines the deliverables of the proposed project. This
information and supporting documents align key stakeholders around what the
project is going to deliver.
The objective of this task is to review the scope statement document with the
customer project manager and key stakeholders in order to confirm the scope and
obtain approval.
The purpose of this activity is to clearly define the acceptance criteria against which
project deliverables and results are measured that have been listed in the Scope
Statement. These should also be updated in the Project Quality Gate Scorecard. In
the context of Agile projects this translates to the definition of Done for the backlog
items that are being delivered in the project.
The purpose of the Project Schedule deliverable is to define the work schedule to
be followed, the resources and associated time commitments required for the
project and the phases of the project. The work breakdown structure (WBS) serves
as the foundation for the schedule, the deliverables to be produced and tasks to be
performed, as part of the project. The project budget, including monitoring and
control, outlines all costs associated with the project, including labor, hardware,
software, contracting fees, and facilities.

Task dependencies (such as predecessors and successors)
Scheduled start and finish dates for each task, based on dependencies
Task constraints (such as must-start-on date and must-finish-on date)
Resources assigned to each task
High-level schedule for subsequent phases
The purpose of this activity is to create the project/phase schedule and assign
Mandatory
resources to the scheduled activities and tasks.
The purpose of this task is to define a high level release plan, determine the length
and number of sprints per release. During this activity the project team needs to
take into accounts business needs, project objectives & goals, available technical
environment, complexity of the solution, geographical and organizational scope of
the project and other aspects (like seasonality of customer's business). The
outcome of this task is high level release plan that includes key features targeted in
each release and number/duration of sprints (note that the sprint duration should be
fixed for all project teams and should not vary).
The purpose of this activity is to extract all planned workshops during the
project/phase into a schedule that facilitates workshop planning
The purpose of this activity is to create project schedule and cost baseline against
Mandatory
which tracking, change management and status reporting is done.
The purpose of the project management plan deliverable is to develop the project
management plan and the subsidiary plans on the basis of the project scope Mandatory
defined in the project charter.
The purpose of this activity is to collect input needed for the project management
plan and document it in a format suitable for both communication purpose as for
formal sign-off purpose, if possible utilizing the accelerator file(s) provided
The purpose of the Project and Operational Standards deliverable is to provide

consistent means of executing and governing project work in an efficient and
effective manner. The key objective of Project Standards is to identify, define,
approve, and communicate standards related to project execution.
Where and when applicable, the current customer processes and procedures,
related to the project standards should be taken into account when defining the
most suitable standards for the project.
The purpose of this task is to determine the customers framework to centrally

document and relate business processes and technical information of SAP and
Mandatory
non-SAP Solutions in Solution Manager, ensuring transparency, efficient
maintenance and collaboration
The purpose of this task, also known as Innovation Management, is to determine

the customers approach for the identification, adaptation and implementation of
new and enhanced business and technical scenarios. It is part of the application
Optional
lifecycle and designed to decouple technical installation from business innovation
using SAP Solution Manager to implement the innovation in the system landscape.
The purpose of this task is to determine the customers approach for managing
functional and performance testing of SAP-centric business processes to ensure
Optional
validated system behavior after software change events.
The purpose of this task is to determine the customers approach of handling

business and technology-driven changes, using a standardized process leading to
Optional
improved reliability of solution and minimized risk through segregation of duties and
transparency of changes.
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
execution, and control of project activities. The project manager is responsible for
ensuring that the management plans are applied at the appropriate level of control.
The purpose of this activity is to assure that the project is executed according to
what was agreed to in project charter, scope statement and project management
plan.
The purpose of this activity is to capture and manage project issues and risks and
Mandatory
changes related to those e.g. changes of project scope, timeline, costs etc.
The purpose of this activity to make sure that project stakeholders are aware of
status and progress of the project including potential disturbances due to existing Mandatory
risks and issues.
The purpose of this deliverable is to present an overview of all planned change

management activities. It guarantees that all activities are related to each other as Optional
well as to the overall project plan and ensures the “checkability” of OCM activities.
The purpose of this activity is to collect all required input for the OCM roadmap and
document it in a format suitable for communication and inclusion into the project
management plan
The purpose of this deliverable is to develop a comprehensive training strategy that

provides all team members with a phase-based learning path for acquiring the skills
and knowledge needed to complete the project successfully. This learning path
leads to project readiness as well as certification on the specific applications the
team members will be using.
The purpose of this task is to prepare the training strategy and plan. Optional
The purpose of this deliverable is to provide an overview of the SAP software to be

implemented so that all project team members have an understanding of the SAP
solution for their areas of responsibility.
The purpose of this task is to train the involved project team in the SAP solutions
expected to be used and/or chosen for the project scope
The purpose of the business process map is to derive and agree on the scope for
the start of the business blueprint phase. During blueprinting, the process map
builds the foundation for the process hierarchy – a decomposition of the process Mandatory
design – which is reflected as scenarios, processes, and process steps in SAP
Solution Manager.
The purpose of this task is to complete the Business Process Map with the content
reflecting the process scope of the project
Validate and Complete Business Process Map with pre-defined content depending
on delivery model (Industrialized and/or Assemble to Order process content).
The purpose of the data migration approach and Strategy deliverable is to capture
and communicate the approach and strategy for the legacy data migration. This
deliverable is intended to educate the SAP and customer project team members on
Optional
the SAP data migration framework and methodology used to support the data
migration project. In addition, the scope and requirement for data migration should
also be determined
The purpose of this task is to prepare the data migration scope and requirements
document that captures the overall scope and requirements of the data migration
effort.
The purpose of this activity to collect input needed for the Data Migration Approach
and Strategy document, in a format suitable for both communication purpose as
well as for formal sign-off purpose.
The purpose of the technical requirements and design deliverable is to provide the
project with a specification of the target solution from a software component
standpoint. This document is intended to serve as a reference for the rest of the
project team during the Business Blueprint phase.
Optional
Included in this deliverable is the solution landscape deployment plan, which is a
high level description of the overall system landscape approach to be used for the
implementation project.
The purpose of this task is to outline the software components and the design of
the future solution landscape.
The purpose of this task is to describe the concept of how the solution in scope will
be deployed.
The purpose of the interface inventory deliverable is to preliminarily identify the

external systems, applications, and business objects or transactions that must be
integrated with the SAP solution to realize the objectives of the project
The purpose of this task is to collect necessary information for the interface
inventory document.
The purpose of the initial hardware sizing proposal is to begin the process of
assessing the hardware infrastructure requirements.
The purpose of this task is to completed sizing estimates for the Solution Manager
system and Production and non-Production environments.
The purpose of the project support tools and system setup deliverable is to
establish the basic tools and processes necessary to support the project.
One of the most vital project tools is the SAP Solution Manager, the centerpiece of
SAP’s Application Lifecycle Management tools. The SAP Solution Manager
provides a central point of access for a variety of essential project support
functions, including:
· Solution Implementation – the identification, adaptation, and implementation Optional
of new and enhanced business scenarios.
· Solution Documentation – centralized documentation repository ensuring the
relationship of business process definitions with technical configuration decisions.
· Change Control Management – synchronized deployment of application
configuration with integrated project control and quality management.
In addition, customer-specific project management and documentation tools may
require installation and distribution to project team members.
The purpose of this task is to validate all technical system requirements for delivery
of the service or project. The objective is to ensure that all required technical
requirements have been satisfied and work can be performed by the team.
The purpose of this task is confirm that the access to the Cloud environment is
possible via the customer LAN
The purpose of this task is to validate and ensure a proper Solution Manager setup.
The purpose of this task is to confirm that the Solution Manager can connect to the
SAP application in the Cloud environement (Hybrid approach)
The purpose of this task is to ensure that the business process structure in SolMan
is supporting the solution documentation and all continued project activities in the
coming phases (business process management, value management, configuration
& development, test, training and cut over).
The purpose of this task is to validate that customer has SAP Solution Builder
installed and setup.
The purpose of this task is to install SAP Best Practices solution builder content
add-on, installation data and solution file
The objective of this task is to setup project logistics, systems and infrastructure
that will support delivery of the project. This may include setup of computers, setup
of project team room, telephony, etc.
The purpose of this task is to prepare authorization roles in the systems for the
project team
The purpose of the demo environment deliverable is to install a technical

development-like system to be used for demonstration and visualization purposes.
The purpose of this task is to installed the virtual Pre-Assembled Rapid Deployment
Solution and make it available in the system landscape of the customer.
The purpose of this task is to perform unit test of the activated pre-assembled RDS
solution and to confirm that relevant solution scope and business processes have
been activated without issues.
The purpose of this task is to check that the SAP system is running correctly and to
ensure that the remote service connection is enabled.
· Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
closure
The purpose of this task is to pass the Project Quality Gate by conducting a quality
check at critical stages of the project. Project Quality Gates are an integral part of
SAP’s Quality Built In approach for SAP primed, partner or client led projects. The
objectives of the Project Quality Gate are:
satisfaction
· To enable project management to continuously communicate the process
and build quality directly into the project
· To provide a tool to effectively manage project expectations and monitor
customer satisfaction
This milestone signifies transition for Project Startup activities to Design, Solution
Design Validation activities
The purpose of this phase is to create/update the business blueprint, which

is a detailed process-oriented and technical documentation of the results
gathered during requirements and design workshops or based on validation
of predefined solution or service description.
A blueprint consists of multiple documents illustrating how the company
intends to run its business using SAP solutions.
The purpose of the phase initiation deliverable is to formally recognize that a new
project phase starts.
The purpose of this task is to confirm resource availability for the particular phase. Mandatory
management process.
plan.
The purpose of this task is to plan, setup and conduct various SCRUM meetings in
order to keep the project teams aligned around common vision, share information
amongst the SCRUM teams and align individuals within each team. The purpose of
these standard meetings is to inform others about work that individual team
members do on given day and surface any blockers that team members need help
addressing .
In Agile implementation project the teams conduct following meetings:
1. Daily SCRUM meeting - short (about 15 minutes) session within each SCRUM
team facing the SCRUM board team members report to the team about what they
work on and whether they are encountering any issues that they need help with.
Objective of this session is to inform and align the team work.
2. Regular SCRUM of SCRUMs meeting - session in which SCRUM Masters from
individual SCRUM teams share information about what each SCRUM team works
on, surface any cross team alignment topics and resolve any issues that arise
between the teams. The session is very similar to integration team meetings
conducted in traditional projects. Note: Cadence of these sessions needs to be
calibrated, but they should be done on at least bi-weekly basis. The more often they
are done the shorter they can be.
3. Sprint Demo - the purpose of this meeting is to demonstrate the results of the
sprint to customer and obtain acceptance to release the features developed during
the sprint. The meeting is attended by Product Owner team, End users and
SCRUM team. It is conducted at the end of sprint.
4. Sprint Retrospective - or process improvement meeting is conducted right after
Sprint Demo meeting prior to closing the sprint. The objective of this meeting is for
the SCRUM team to conduct retrospective of the sprint, identify potential
improvements of the process, prioritize and select top improvements to implement
in the next sprint.
Mandatory
The purpose of this task is to ensure that each contract is closed by verifying that
all work specified in the contractual arrangement was completed, and that all Mandatory
defined deliverables were accepted.
The purpose of the stakeholder analysis deliverable is to detect the level of
acceptance or the general attitude regarding the project on the part of all key
stakeholders, as well as the ways they can influence the project. Execute an Optional
analysis of current state ‘as-is’ and future state ‘to-be’ business process maps to
quantify the delta ‘transition gap’
The purpose of this task is to re-visit the stakeholder identification results,
determine the detailed level of change impacts for the identified stakeholder
(groups) in order to create transparency about the organizational and system
changes.
The purpose of this task is to identify key users needed for the different areas
(depending on the scope of this project).
The purpose of the Change impact analysis deliverable is to ensure that the
organizational and technical changes in business processes have been identified Optional
and documented by comparing the as-is and the to-be business processes.
The purpose of this task is to validate the chosen approach with key stakeholders
for the continued project execution.
The purpose of this task is to define the baseline for where organizational change
management starts and against which progress and success of the OCM-activities Optional
are measured.
The purpose of the End User Training Strategy and Plan deliverable is to develop a
high level training plan that provides the recommended approach and Mandatory
corresponding activities to prepare the end users for using the new system.
The purpose of this task is to perform an analysis of the end-user population to be

trained and determine where the skills levels, knowledge gaps, and training
requirements are located. This analysis contains the key customer information for
definition of the end-user training and documentation of high-level project plan
recommendations, proposals, and preliminary strategies.
The purpose of this task is to develop a working document to track evolution of

Optional
documents and progress of processes for all education aspects of the project
The purpose of the Project Team Training deliverable is to ensure that the project
team is informed about the way of working during the Blueprint Phase including
usage of Solution Manager for Solution Documentation.
The purpose of this task is to clarify deliverables and expectations, methodology,

and tools. Typically two to three days should be reserved for this training. Once the
team members or at minimum the team leads are identified, they will be brought on
board with this ramp-up training before the phase kickoff meeting. The blueprint
ramp-up deliverable:
· Sets project team expectations and blueprint deliverables
· Provides guidance for blueprinting workshops and relevant enabling tools
· Introduces blueprint quality assurance and its acceptance criteria
· Prepares for essential blueprinting skills, such as workshop facilitation,
requirements gathering, and process modeling
The purpose of solution validation / fit-gap analysis deliverable is to validate the

predefined scenarios, processes and enhancements; identify potential gaps
between delivered product and customer requirements. The deliverable only
captures requirements for gaps. It follows an iterative approach. Existing
documentation and models can be altered, changes have to be marked and
documented in Solution Manager.
This task validates predefined general settings and that these are still relevant for
the scope of the implementation, such as organizational structures or customer or
material masters, and to identify potential gap between delivered product and
customer requirements.esign a solution for these business objects within the SAP
solution. These objects are associated to processes and reflected in applications so
understanding these relationships is essential for overall integration and cross-
process integrity.
This task validates predefined scenario solution documentation, identifies potential

gap between delivered product and customer requirements. Only requirements for
gap are being captured. It follows an iterative approach. Existing documentation
and models can be altered, changes have to be marked and documented in
Solution Manager
This task validates predefined process solution documentation, identifies potential
gap between delivered product and customer requirements. Only requirements for
gap are being captured. It follows an iterative approach. Existing documentation
and models can be altered, changes have to be marked and documented in
Solution Manager.
This task validates the pre-defined RICEFW Objects (reports, forms etc.). Additional
customization and enhancements should be kept to a minimum.
This purpose of this task is to analyze identified gaps and additional requirements
and determine effort (and duration) for the realization phase.
The purpose of the legacy data migration deliverables is to develop the designs,
plans, and procedures to support the migration of legacy data during the Mandatory
implementation of the SAP applications.
The purpose of this task is to design the specific architecture, programs, processes,
and tasks required to support the extraction, validation, harmonization, enrichment,
and cleansing of the legacy data.
The purpose of Manual Data Migration design is to develop the approach for
manually bringing legacy data into the SAP database when automated programs
are not available or the data volume does not justify the investment in developing
such programs.
The purpose of this deliverable is to ensure proper set up of a Roles and
Authorizations procedure and approach for the project.
The purpose of this task is to document the authorization requirements at the level
of business scenario and process, to evaluate chosen authorizations concepts Mandatory
against SAP standards and to determine a feasible implementation approach.
The purpose of the development environment deliverable is to install a viable,

correctly configured technical development environment that is available for use by Mandatory
the project team to begin the realization phase.
The purpose of this task is to ensure that the VA image is transfered to customers
development environment.
This task ensures that all solution documentation is made available for the project
team. Preferably the repository for this should be Solution Manager.
The objective of this task is to validate the assignment of user role profiles /
authorizations to the test users in the development landscape.
The purpose of this deliverable is to create project related test framework, which
gets content input from the existing Test Policy (1.16.), to build a central foundation
around the taken approach (e.g. Test Approach and Methodology, Test Standards
and Guidelines, Test Case Development, Defect Management, Reporting and
Mandatory
Analysis, Roles and Responsibilities)
on functional testing (unit-, string-, integration-, scenario-, user acceptance,
regression testing etc.) and performance testing. The actual test strategy
documentation for functional testing and performance testing have to be separated.
Determine overall test data approach by aligning with the overall data migration
approach. The test data approach will be documented as part of the testing
strategy.
The objective of this task is to communicate the testing strategy (functional and
performance) to the customer project team and validate it.
Mandatory
closure
satisfaction
This milestone signifies completion of Design activities and transition to Build

activities
The purpose of the realization phase is to implement the business scenario

and process requirements based on the business blueprint completed in the
previous phase.

· Establishment of the solution landscape
· Implementation of the final solution in the development environment
· Overall testing of the solution within the quality environment
· Release of the solution for production (live) operations
· Preparation for data migration and data archiving
· Identification of value delivery concepts
· Performance testing
The purpose of this deliverable is to initiate sprint in formal Sprint Planning Meeting.
The purpose of this task is to initiate sprint by selecting the set of user stories that
will be implemented in the sprint (scope of the sprint). During the sprint planning
meeting the SCRUM team estimates the stories and clarifies with product owner
team any questions that may still remain open. The team commits to deliver set of
highest priority stories from the backlog. This meeting formally sets the scope for
the sprint. This meeting is conducted in the beginning of each sprint.
The purpose of this task is to ensure consistent planning, execution and monitoring
of sprint activities. This includes:
Team Activities
■ The team performs their sprint tasks as to the sprint backlog, taking priority and
done criteria into account
■ The team attends the Daily Stand-up Meeting. The Daily Stand-up Meeting
serves for information exchange among the team members. It should not exceed
15 minutes and occurs same time same place each day. After the meeting, the
team updates the sprint backlog (what are remaining tasks and efforts). For more
information please refer to the Scrum Meeting Guidelines.
■ Scrum-of Scrum Meetings are conducted to coordinate the work between
different scrum teams. Scrum of Scrum meetings allow teams to discuss their work,
focusing especially on areas of overlap and integration. For more information
please refer to the Scrum Meeting Guidelines
Product Owner Activities
■ Prepares ready-state user stories for the next sprint(s).
■ Aligns expectations and requirements with his business stakeholders.
■ Is available for answering questions from the team.
Scrum Master Activities
■ Makes sure that the Scrum process is followed (organizing and facilitating Daily
Scrums, daily updates of remaining tasks and effort by team, organization of sprint
review and retrospective meetings)
■ Solves blocks and supports team, including escalation.
■ Ensures that management or others do not influence team.
plan.
Mandatory
risks and issues.
SCRUM of SCRUMs Meeting is conducted to coordinate the work between different

project SCRUM teams. SCRUM of SCRUMs meetings allow teams to discuss their
work, focusing especially on areas of overlap and integration. The meeting cadence
is defined for the entire project and follows the same structure. Some teams
conduct daily SCRUM of SCRUMs meeting while others consider weekly meeting
sufficient. The main driver for the meeting cadence is the level of collaboration
between the individual SCRUM teams and level of dependencies between the
features built in each SCRUM team.
The purpose of Organizational Alignment is to ensure a smooth transition process

towards the new way of working. This includes the alignment of roles and
responsibilities and activities to ensure that all employees are fully aligned to the
goals of the project and organization.
The purpose of this task is to use the results from previous change impact analysis
and the role mapping information (mapping of new business user roles to existing
Optional
roles and organizational structure) and determine an appropriate transition
approach for the business.
The purpose of the Knowledge Transfer deliverable is to ensure that key users get
a good understanding of the implemented solution.
In this task the SAP project team prepares for training and enablement of the
customer project team to understand the solution and how it is implemented in their
area, as well as trains the key users as defined in the statement of work.
The purpose of this task is to execute knowledge transfer by means of solution

walkthrough sessions, system demos on scenario and/or process level, functional
reviews etc., etc.
The purpose of this task is to execute knowledge transfer for the solution delta
scope by means of solution walkthrough sessions, system demos on scenario
and/or process level, functional reviews etc., etc.
The purpose of the deliverable End User Training Content Enabled is to ensure
availability of end user training material, training environment, logistics Optional
infrastructure and skilled instructors.
This task ensures a consistent appearance of the training materials and

documentation by providing the development team with standard templates.
The purpose of the Configured General Settings and Organizational Structure

deliverable is to complete and document the initial configuration of the system on Mandatory
the basis of the decisions made in the business blueprint phase.
The purpose of this task is to implement the configuration related to general

settings, and to document this in Solution Manager.
The purpose of this task is to implement the configuration related to organizational
structure, and to document this in Solution Manager.
The purpose of the Configured Master Data Objects 1-n deliverable is to configure
the master data in the SAP software system according to the business process Mandatory
requirements specified in the business blueprint phase.
processes' unit and string tests in DEV.
The purpose of the Core Configuration and Documentation deliverable is to ensure

that the configuration is implemented, tested and documented. Mandatory
The purpose of this task is to implement the Core Configuration, write valid test
cases and to document this in Solution Manager.
The purpose of the Delta Configuration deliverable is to ensure that the

configuration is implemented, tested and documented. Mandatory
The purpose of this task is to implement the Delta Configuration, write valid test
cases and to document this in Solution Manager.
The objective of this task is to develop process documentation for any changed
processes or for any new processes added to the standard.
The objective of this task is to develop process test cases for any changed
processes or for any new processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration Optional
The objective of this task is to resolve any issues identified during the Unit and
String Test. It is crucial that the issues are re-tested by users that reported them (or
designated re-testers) and that they are confirmed.
The purpose of this deliverable is to accommodate all RDS or Service Specific
enhancements, coded assets, etc. Each asset will have separate line item in this Mandatory
structure
The purpose of this service specific <Asset Name> is to <explain purpose of the
extension specific task>….
Note: This task is a place holder for any tasks that are specific to extensions like
reports, interfaces, etc. that are delivered in the service or RDS
The purpose of this deliverable is to develop and test the RICEFW objects.
Mandatory
Documentation to be stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the
functional specification,
The purpose of this task is to document the RICEFW object information in a
technical specification and define the appropriate test case(s). Documentation is
stored in Solution Manager.
The purpose of this task is to perform unit and string test of the developments. Optional
The objective of this task is to resolve any issues identified during the RICEFW
object(s) Test. It is crucial that the issues are re-tested by users that reported them
(or designated re-testers) and that they are confirmed.
The purpose of this task is to perform final code review of the development objects
and confirm readiness for transport into QAS.
The purpose of the Business Process Procedures deliverable is to provide the

basis for end-user training, end-user training documentation and test case creation.
The procedures may also be used by security to develop roles and authorizations.
The purpose of this task is to validate and complete Business Process Procedures
from the blueprint phase.
The purpose of this task is to validate and complete Business Process Procedures
from the blueprint phase.
The purpose of this deliverable is to provide evidence that the scenarios designed
can be supported by the solution implemented.
The purpose of this task is to identify and document applicable test case(s) for the
scenario.
The purpose of this task is to perform scenario test. Optional
The objective of this task is to resolve any issues identified during the scenario
testing. It is crucial that the issues are re-tested by users that reported them (or
The purpose of the quality assurance infrastructure and environment design and
setup deliverable is to install a viable, correctly configured technical QA Mandatory
environment that is available for use by the project team to perform QA testing.
The purpose of this task is to install SAP components needed for the realization of
project scope.
The purpose of this task is to build the quality assurance (QA) environment with
changes that have been unit-tested and released from the development
environment.
The purpose of this task is to set up users in the Quality Assurance environment.
processes in QAS.
The purpose of this task is to prepare transactional data for upload into QAS
The objective of this task is to perform any remaining manual configuration changes
in the Quality Assurance environment.
This milestone signifies completion of Build activities and transition to Integration

Testing, User Acceptance Testing and Non-Functional Testing
The purpose of the preliminary cutover plan deliverable is to document the strategy,
scope and timelines for moving from the as-is solution to the to-be solution and the Mandatory
hyper care period immediately following go-live.
The purpose of the preliminary cutover plan task is to document the strategy, scope
and timelines for moving from the as-is solution to the to-be solution and the hyper
care period immediately following go-live. This includes documenting activities such
as the transfer of data from the legacy systems to the SAP software production
system, setting up and initializing the production system, closing the legacy
systems, manually entering certain data in the new system, setting up and verifying
interface connections, importing transports and all manual configurations.
The purpose of this task is to refine the preliminary cutover plan based on
information the project team learned in the cutover plan review with customer.
The purpose of Approved Integration Test is to ensure functional correctness. It test

the integration of SAP solutions with non-SAP applications and interfaces and can
Mandatory
be executed in an iterative manner.
The purpose of this task is to define and document integration test cases, end-to-
end customer business process scenarios, according to the test plan. Test plans
and test case documentation is stored in Solution Manager.
The purpose of this task is to document the integration test case outlined in the
integration test plan
The objective of this task is to perform the Integration test according to previously
defined plan. During the test all issues must be logged and documented in the
system for traceability purpose.
The objective of this task is to resolve any issues identified during the Integration
Test. It is crucial that the issues are re-tested by users that reported them (or
The purpose of this task is to obtain customer approval (sign-off) of the integration
test.
The purpose of the legacy data migration deliverable is to develop, implement, and
test the data migration programs and processes defined in the business blueprint
phase. This activity consists of iterative development and testing cycles focused on
the analysis of data, refinement of business rules, and deployment of migration
programs and processes designed to move, cleanse, transform, and enrich legacy
Mandatory
data required to support the various test cycles and ultimately the production
cutover. The test cycles enable the migration team to improve data quality to an
acceptable production level, develop a detailed cutover sequencing plan, and
exercise data reconciliation and validation processes required to support the
production cutover.
The purpose of this task is to load the cleansed legacy data into the SAP software
target structures using a standard SAP load utility such as LSMW.
The purpose of this deliverable is to execute the User acceptance test (UAT). This
is the last test cycle of an SAP solution implementation and is an essential part of Mandatory
gaining end-user acceptance of the software system.
The purpose of this task is to define and document UAT test cases according to the
test plan. Test plans and test case documentation is stored in Solution Manager
The purpose of this task is to document the integration test case outlined in the
UAT test plan
The objective of this task is to perform the End User Acceptance test according to
previously defined plan. During the test all issues must be logged and documented
in the system for traceability purpose.
The objective of this task is to resolve any issues identified during the User
Acceptance Test. It is crucial that the issues are re-tested by users that reported Mandatory
them (or designated re-testers) and that they are confirmed.
The purpose of this task is to execute the testing, document the results and obtain
customer approval (sign-off)
The purpose of the production infrastructure and environment design and setup
deliverable is to install a viable, correctly configured technical production Mandatory
environment to support productive operations of the delivered solution.
The purpose of this task is to install and set up the production environment.
The purpose of this task is to upgrade the production environment.
The purpose of this task is to build the production (PRD) environment with changes
that have been tested and released from the quality assurance (QA) environment.
The purpose of this task is to set up users in the production environment.

The purpose of this task is to ensure that appropriate master data is available for
testing in the production environment (system test).
processes in PRD.
The purpose of this task it to perform import of Fast-Track configuration into the
Production environment.
The purpose of this task is to perform any remaining manual configuration changes
in the production environment.
The purpose of planned Performance and System Test is to checks the entire
system, consisting of databases, applications servers, front ends, printers etc. The Mandatory
performance test measures the throughput and response times of the system.
The task defines and documents the identified test cases related to system and
performance test. Outcome is documented in a test plan.
The objective of this task is to resolve issues identified during the performance or
load testing. Upon resolution the issues need to be re-tested and confirmed by
responsible testers.
The purpose of this service is to support the start of production of an SAP Solution.
During this service, SAP service engineers check the solution for potential risks and
Optional
give recommendations ensuring optimal performance and system availability for
core business processes.
The purpose of this task is to perform the first session of the SAP GoingLive Check.
The service consiste of two sessions - Analysis and Verification, and includes:
- Verification of the technical capabilities of the production environment (sizing
plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components and
Plug-Ins
The purpose of the technical operations and handover strategy deliverable is to

update refine two prior deliverables from the Business Blueprint phase, and prepare
Optional
a strategy to hand off operations of the solution landscape to the post-production
support organization.
The purpose of this task is to ensure that proper staffing(people and competence)
is in place for the support org/team
This task describes the considerations that are required to recognize and solve
critical situations during business process operation.
Mandatory
closure
satisfaction

This milestone concludes testing activities and start of deployment of the
functionality to Production Environment
The purpose of the final preparation phase is to finalize readiness of the

solution and its supporting tools and processes for production go live. This
includes, but is not limited to, system tests, end-user training, system
management, and cutover activities (including data migration). The phase
deliverables also serve to enable the resolution of all crucial open issues. On
successful completion of this phase, the business is ready to run the live
SAP software system.
plan.
Mandatory
risks and issues.
The purpose of the EU training delivery and readiness checklist is to provide a

checklist summarizing end-user training delivery to ensure readiness for adoption of
the solution. In the checklist, items governing training delivery, communications,
and future planning clarify the status of all aspects of the training initiative.
The objective of this task is to deliver end user training to identified end user groups
according to the previously developed training schedule.
The purpose of this deliverable is to present the findings and recommendations

from the results of technical tests such as disaster recovery tests, backup and
restore tests, and other required technical or basis-related tests to the customer or
project team for final signoff in order to exit system testing.
The purpose of this task is to prepare and execute the system tests. The
outcome/results should be approved by the customer.
The purpose of production cutover is to perform the cutover to the production

software and go live. At this point, the organizational, business, functional,
technical, and system aspects of the project are ready to be used in production.
This task verifies that master data support is set up and process is operational Mandatory
The purpose of this task is to complete the Cut Over plan with results obtained from
Mandatory
the Go Live simulations.
The objective of this task is to perform all the cutover preparation activities
remaining to be closed prior to cutover weekend. The detailed cutover plan
contains the complete listing of all pre-cutover activities, their dependencies,
owners, and timing.
This task will confirm that the productive system is ready for Go Live. Optional
The purpose of this task is the loading of production data from legacy systems into
the production environment. Once all preparations and configurations on both the
technical and application levels are completed, the final productive solution can be
set up and data loaded. The solution is live in a production environment
Purpose of this task is to obtain customer approval (sign-off) Mandatory

Purpose of this task is to hand over the finalized implementation project and it's
content, and set up as a productive solution in SAP Solution Manager. This Optional
provides the basis for the follow up activities in the Run Phase.

Mandatory
closure
satisfaction
This milestone signifies formal transition to production environment. Production is

up and running, cutover sustainment activities, end-user on-boarding and support
are under way.
The purpose of this phase is to provide support for the solution during the
period immediately following production cutover. Exceptional items such as
additional production support, exceptional business monitoring processes,
and extraordinary technical support are planned and executed in this phase.
At the end of the designated extra-care period, sustaining production support
processes planned in final preparation and executed as part of go-live
support become the core support for continuous improvement in the ongoing
solution.
The purpose of EU training during go-live support is to ensure that end users have
adopted the solution, knowledge resources are maintained, and responses to the Optional
end-user acceptance survey are positive.
This purpose of this task is to adapt available training material and make it suitable
for End User training.
This task executes the delivery of EU training as well as capturing feedback on both
the training session and the trainer.
The purpose of the production support and transfer to solution deliverable is to
confirm that the resources and processes are in place to support the ongoing
solution and to complete the steps required to close the project and finish
documentation.
The purpose of this task is to verify that the requirements identified in earlier
sessions are met.
The purpose of the production support and transfer to solution deliverable is to
confirm that the resources and processes are in place to support the ongoing
Optional
solution and to complete the steps required to close the project and finish
documentation.
The purpose of this task is to implement ongoing production support to the SAP
software system users and to monitor and optimize system performance.
This milestone signifies formal transition from post production sustainment support
to long term support and operation of the new environment
The purpose of the Improvement Roadmap is to outline a solution roadmap, which

takes into account the whole of the customer solution, incorporates captured
business requirement outside of the project scope and potential improvements.
The objective of the refinement & improvement planning workshop is to identify

future potential improvements of the customer solution.
The objective of this task is to capture the results of the refinement and
improvement planning workshop. The final document is shared with the virtual
account team and the customer team.
Mandatory
closure
The purpose of this task is to collect knowledge assets and lessons learned at the
end of each phase of the project that can be reused later by other projects.
Collecting documents, experiences, project highlights and lessons learned Optional
throughout the duration of the project can help to facilitate the project by providing
quick access and insights into key deliverables from earlier stages of the project.
satisfaction
The purpose of this activity is to achieve a closure of all open project issues which
is a prerequisite for the final project closure.
The purpose of this activity is to document the results of the project, both regarding
achieved objectives, deliverables as well as adherence to schedule, costs and
delivered value.
The purpose of this activity is to formally close the project by obtaining customer
signatures on dedicated deliverables/documents e.g. Project Quality Gate, Project
Closeout Report
Solution operations are initially set up during the implementation project. The
primary goal of this phase is to further optimize and automate the operability
of the solution. Operability is the ability to maintain IT systems in a
functioning and operating condition, guaranteeing systems availability and
required performance levels to support the execution of the enterprise’s
business operations.
The Operations Maturity Assessment evaluates the SAP customer's support

operations to determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements for
operations and to define what aspects of the operations need to be adjusted,
enhanced or implemented.
The report should detail assessment results and finding, including proposed actions
for how to bridge identified gaps.
Centrally document and relate business processes and technical information of
SAP and non-SAP Solutions ensuring transparency, efficient maintenance and
collaboration
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Solution Documentations area.
Represents the identification, adaptation and implementation of new and enhanced
future-proof business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical
installation from business innovation
Uses the SAP Solution Manager to implement the innovation in the system
landscape
exist for the Solution Implementation area.
The template management approach allows customers with multi-site SAP

installations to efficiently manage their business processes across geographical
distances – from initial template definition to template implementation and template
optimization, for example as part of a global rollout
exist for the Template Management area.
Functional and performance testing of SAP-centric business processes to ensure
validated system behavior after software change events
exist for the Test Management area.
Workflow-based management of business and technology-driven changes, with

integrated project management and synchronized deployment capabilities.
Standardized process leading to improved reliability of solution and minimized risk
through segregation of duties and transparency of changes
Efficient solution management – all project and system information is saved in SAP
Solution Manager
exist for the Change Control Management area.
Enables a centralized and common incident and issue message processing in
multiple organization levels
Offers a communication channel with all relevant stakeholders of an incident. The
process includes business user, SAP experts@customer, SAP Service&Support
and Partner Support employees.
Is integrated in all ALM processes of SAP Solution Manager, in any SAP Business
Suite solution and could be connected to an Non-SAP Help Desk application
Includes follow up activities as knowledge research, root cause analysis or Change
Management
exist for the Incident Management area.
Represents all capabilities for monitoring, alerting, analysis and administration of
SAP solutions
Allows customers to reduce TCO by predefined content and centralized tools for all
aspects of operations in SAP Solution Manager
Provides End-to-End reporting functionality either out-of-the-box or individually
created by customers
exist for the Technical Operations area.
SAP Business Process Integration & Automation Management (BPIAM) comprises
the most important application related operations topics necessary to ensure the
smooth and reliable flow of the core business processes to meet a company's
business requirements.
exist for the Process Operations area.
SAP Notes provide a solution for known issues. SAP Notes are usually applied
upon request (e.g. current incident in productive environment, information from SAP
about potential issue (Hot News, Security Notes)).
SAP Notes are collected and released as Support Packages. Support Packages
are applied to SAP solutions to comply with legal requirements or run on latest
technology.
exist for the Maintenance Management area.
Is the identification, adaptation and implementation of new and enhanced business
and technical scenarios
Uses the SAP Solution Manager to manage the upgrade project holistically and
effectively end-to-end
Allows SAP customers to better understand and manage the major technical risks
and challenges in an upgrade project, and to make the upgrade project a “non-
event for the business.”
exist for the Upgrade Management area.
Q-Gate Key Deliverable Work Stream Accountable Role
_Phase

Project Guideline (incl.
Travel Guideline)
Steering Committee
Definition, Org-Structure, PM - Project Management Project Manager
Roles
Project Charter PM - Project Management
OCM - Organizational Change

Project Manager
Management
Phase Kick Off Meeting PM - Project Management

Scope Statement
Document

milestones)

Project Budgetplan
(internal & external)
Project Management
Plan(s)

Management
Solution Manager Usage

guideline, ALM - Application Lifecycle Business Consultant
Business Process Management
Modeling Standards
Software System
Configuration Standards, ALM - Application Lifecycle Business Consultant
Enhancement and Management
Modification Standards
Test Management Test Management Consultant

Standards
Change Request and

Transport Management Application Consultant
Management
Standards (CTS)

external), Project Change PM - Project Management Project Manager
log, Project Issues log
external)

OCM Roadmap
Management
OCM - Organizational Change Business Consultant
Management
Training - Training
Project Team Training

Training - Training Education Consultant
Plan & Schedule
Training - Training
Business Process Map BPM - Business Process

Business Process List Management

Management

Management
Data Migration Approach,

DM - Data Migration
Start and Scope

Design Management

Solution Architect
Management
Management

Management
Management
Management

Solution Architect
Management
Proj Support Tools & Sys TSM - Technical Solution

Setup Management

Management

Management
Management

Management

Management

Management
Management

Management

Management

Management

Management

Management
_Milestone
_Phase
milestones)
Project Management
Plan(s)


Report (internal & external
Stakeholder Analysis OCM - Organizational Change

(Internal) Management

Management

Management
Organizational Change OCM - Organizational Change

Management Plan Management
Management
Business Readiness OCM - Organizational Change Business Consultant

Approach Management
Training Project Plan Training - Training

Documentation Training - Training Education Consultant
Developed
Training - Training
Business Consultant
Training - Training

Management

Management

Management
Management


Management

DM - Data Migration
Plan

Management
Authorization
Requirements and Design Technology Consultant
Management

Design Management

Management

Management

Management

Results

Results
Delivery Acceptance
Protocol
_Milestone
_Phase

milestones)
PM - Project Management Application Consultant


Management

User Role Document
Management
Training - Training

Developed
(incl. Process list, BPM - Business Process
Configuration, Interfaces, Management
Developments)
Management
Management
Developments)
Management
Developments)
Management
Developments)
Management
Management

Management

Management

Management
Developments)

Management
Development list(incl. BPM - Business Process

RICEFW, SOA, Migration) Management



Test cases & Results



Management

Management
Management

Test cases & Results ISM - Test Management Application Consultant

Design Management

Management

Management

Management

Management
_Milestone
Production Cutover Plan CutOver - Cut Over Management
CutOver - Cut Over Management Application Consultant
CutOver - Cut Over Management Project Manager

Results

DM - Data Migration
Plan

Testplans & Results - UAT ISM - Test Management

Regression

Design Management

Management
Management

Management

Management

Management
Management
Test Plans & Results ISM - Test Management

SAP Going Live Check
Management
Management
Technical Operations and TSM - Technical Solution

Handover Strategy Management

Management
Management
Results
Delivery Acceptance
Protocol

_Milestone
_Phase
milestones)

Training - Training
CutOver - Cut Over Management

Plan
Production Cutover Plan CutOver - Cut Over Management Application Consultant
Readiness for Cutover -

Signoff
Production Cutover Plan CutOver - Cut Over Management Project Manager

Solution Manager Update,
CutOver - Cut Over Management Technology Consultant
Results
Delivery Acceptance
Protocol
_Milestone
_Phase
milestones)
Go-Live Training Sessions Training - Training

Management
Support Process Enabled,

Governance Model for CutOver - Cut Over Management
Operations
_Milestone
Results
Delivery Acceptance
Protocol

Learned (internal)

_Phase
Business Consultant

Management

Management

Management

Management

Management

Management

Management
ALM - Application Lifecycle Test Management Consultant

Management

Management

Management
Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

W Bs Dictionary

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

W Bs Dictionary

Uploaded by

Copyright:

Available Formats

WBS # WBS item title

Allocate Resources - hard booking with resource

1 2 1 Define Project Organization

1 2 2 Assign Roles and Responsibilities

1 2 3 Complete communication management plan

1 3 1 Prepare Project Charter Document

1 3 3 Obtain Project Charter Sign-off

1 4 1 Prepare for Kickoff Meeting

1 5 1 Document Customer Requirements

1 5 2 Review Scope Statement with Customer

1 5 3 Create Work Breakdown Structure and WBS Dictionary

1 5 4 Refine Acceptance Criteria

1 5 5 Obtain customer sign off for project scope

1 6 Project Schedule and Budget

1 6 1 Develop delivery schedule and assign resources

1 6 2 Include key workshops into the project schedule

1 6 4 Establish Cost and Schedule baseline

1 7 Project Management Plan

1 7 1 Prepare Project Management Plan

1 7 2 Obtain Project Management Plan Sign-Off

1 8 Project and Operational Standards

1 8 1 Conduct ALM Roadmap

1 8 2 Determine Solution Documentation Procedure

1 8 3 Determine Solution Implementation Procedure

1 8 4 Determine Template Management Procedure

1 8 5 Determine Test Management Procedure

1 8 6 Determine Change Control Management Procedure

1 8 8 Determine Technical Operations

1 8 9 Determine Business Process Operations

1 8 10 Determine Maintenance Management

1 8 11 Determine Upgrade Management

1 9 Execution, Monitoring, and Controlling of Results

1 9 1 Direct and manage project execution

1 9 2 Monitor and control project activities

1 9 3 Manage Issues, Risks and Changes

1 10 Organizational Change Management Roadmap

1 10 1 Prepare Organizational Change Management Roadmap

1 11 Project Training Strategy and Plan (team + key-users)

1 11 1 Prepare training strategy and plan document

1 12 Project Team Training

1 12 1 Conduct Solution Training and knowledge transfer

1 13 Business Process Map

1 13 1 Prepare Business Process Map

Prepare Demo Environment for Scope Refinement

Complete Customer Blueprint and Configuration

1 13 6 Validate and Complete business process map

1 14 1 Prepare Value Map

1 15 Business Scenario Design

1 15 1 Capture Business Scenario Requirements

1 15 2 Validate and Complete Scenario Design

Store Scenario Level Solution Documentation in SAP

1 16 Prepare Testing Policy

1 16 1 Prepare Testing Policy document

1 16 2 Obtain Customer Sign-Off for Testing Policy document

1 17 Data Migration Approach and Strategy

1 17 1 Prepare Data Migration Workshop

1 17 2 Conduct Data Migration Workshop

1 17 3 Conduct Data Audit (Data Health Check)

Prepare Data Migration Scope and Requirements

1 17 5 Present DM scope and requirements document

1 17 6 Conduct Organizational Assessment for Data Migration

1 17 7 Conduct Infrastructure Assessment for Data Migration