W Bs Dictionary

WBS #
WBS item title
Project Preparation
Project Initiation
2 Prepare Team Onboarding Document
1 Define Project Organization
2 Assign Roles and Responsibilities
3 Complete communication management plan
1 Prepare Project Charter Document
2 Identify Stakeholders
3 Obtain Project Charter Sign-off
1 Prepare for Kickoff Meeting
2 Perform Kickoff Meeting
Allocate Resources - hard booking with resource

management
Project Governance
Project Charter
Kick-Off Workshop
Scope Statement
1 Document Customer Requirements
2 Review Scope Statement with Customer
3 Create Work Breakdown Structure and WBS Dictionary
4 Refine Acceptance Criteria
5 Obtain customer sign off for project scope
1 Develop delivery schedule and assign resources
2 Include key workshops into the project schedule
3 Obtain Customer sign-off for project schedule
4 Establish Cost and Schedule baseline
Project Schedule and Budget
Project Management Plan
1 Prepare Project Management Plan
2 Obtain Project Management Plan Sign-Off
1 Conduct ALM Roadmap
2 Determine Solution Documentation Procedure
3 Determine Solution Implementation Procedure
4 Determine Template Management Procedure
5 Determine Test Management Procedure
6 Determine Change Control Management Procedure
7 Determine Application Incident Management Procedure
Project and Operational Standards
8 Determine Technical Operations
9 Determine Business Process Operations
10 Determine Maintenance Management
11 Determine Upgrade Management
1 Direct and manage project execution
2 Monitor and control project activities
3 Manage Issues, Risks and Changes
4 Communicate Status and progress to project stakeholders
1 10
1 10
Execution, Monitoring, and Controlling of Results
Organizational Change Management Roadmap
1 Prepare Organizational Change Management Roadmap
1 11
1 11
Project Training Strategy and Plan (team + key-users)
1 Prepare training strategy and plan document
1 12
1 12
Project Team Training

1 Conduct Solution Training and knowledge transfer
1 13
Business Process Map
1 13
1 Prepare Business Process Map
1 13
1 13
3 Prepare Scope Document for Workshop
1 13
For <SCOPE OPTION> - Demonstrate the business

processes and predefined options list
1 13
Complete Customer Blueprint and Configuration

Requirements Template
1 13
6 Validate and Complete business process map
1 14
Prepare Demo Environment for Scope Refinement

Workshops
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
1 15
1 16
Store Scenario Level Solution Documentation in SAP

Solution Manager.
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)
1 17
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
1 17
Conduct Risk Assessment for Data Migration and Prepare

Mitigation Plan
1 17
Complete the Data Migration approach and strategy

document
Prepare Data Migration Scope and Requirements

Document
Technical Requirements and Design and Solution

Landscape Deployment Plan
1 18
1 18
1 Define Solution Landscape Concept
1 18
2 Define Solution Deployment Concept
1 19
1 19
Interface Inventory
1 Prepare Interface Inventory document
1 20
1 20
Initial Hardware Sizing Proposal

1 Complete HW sizing estimation for solution landscape
1 21
Project Support Tools and System Setup
Verify Technical System Requirements (frontend /

backend)
1 21
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
1 21
Set up Business Process Hierarchy in SAP Solution

Manager
1 21
Setup of project logistics and infrastructure, including

team collaboration environment
1 21
7 Install SAP GUI on project team computers
1 21
1 21
9 Prepare SAP Best Practice Activation
1 21 10
Test Remote Access and Establish OSS Connection (both

GUI and Web Access)
Execute Technical Installation of SAP Products (Predefined solution Components)
1 21 11 Perform Installation check

1 21 12 Review installation check and knowledge transfer
1 21 13
Prepare authorization roles in the systems for the project

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
Business Blueprint
Phase Initiation
1 Allocate Resources and Update Project Schedule
1 Update Project Management Plan
Execution, Monitoring and Controlling Results
Stakeholder Analysis
1 Conduct classification of project Stakeholders
2 Identify Key Users
1 Validate organizational alignment approach
2 Establish Baseline of Current State
1 Define Value Argumentation / Key Messages
2 Define Communication strategy
1 Conduct Learning Needs Analysis
2 Develop Detailed End-User Training Plan
Change Impact Analysis
Communication Plan
End User Training Strategy and Plan
1 Conduct Blueprint Ramp-up Training
2 Conduct Key User training
End User Training Content
1 Adaptation of Pre-delivered Training Content
For <General Settings #1 - n> - Conduct Validation and Fitgap Analysis
For <Scenario #1 - n> - Conduct Validation and Fit-gap

Analysis
For <Process #1 - n> - Conduct Validation and Fit-gap

Analysis
Validate pre-defined RICEFW Objects (reports, forms

etc.)
Prepare and Build Training Content in Project

Environment
Scope Validation / Fit-Gap Analysis
2 10
5 Determine Gap list and effort estimation
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
2 13
Value Realization
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
2 14
2 15
Define Functional Design - SOA & 3rd party applications

#1 - n
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
2 16
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
2 17
2 18
2 18
2 19
Conduct Data Mapping workshops (master data for predefined solutions)
Legacy Data Archive
Prepare baseline framework for the legacy data archiving

solution
Technical Solution Design
1 Prepare technical infrastructure specification
User Access and Security
2 19
1 Authorization Requirements and Design
2 20
2 20
2 20
Development Environment (DEV)

Execute Technical Installation of SAP Products for DEV
environment
Execute Technical Upgrade of SAP Products for DEV
2
environment
1
2 20
3 Install Solution Documentation in Solution Manager
2 20
4 Execute Technical Installation of 3rd party products
2 20
2 20
6 Perform Manual Configuration in DEV
2 20
2 20
Set up Role assignment / Authorizations / Test Users in

DEV
Validate Role assignment / Authorizations / Test Users in

DEV
Create master data in DEV environment - Master Data #1 8
n
2 21
Testing Strategy
2 21
1 Prepare Test Strategy document
2 21
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
Define Test data approach and validated pre-defined

master data
2 22
2 22
2 22
2 22
4 Conduct Design Review Service
2 22
5 Manage Fulfilled Contracts
2 22
2 23
MILESTONE: Design to Build
Realization
Phase Initiation
1 Execute Role Mapping and Transition Planning
2 Conduct Sounding Board/Pulse Checks
3 Refine and Execute Communication Plan
Organizational Alignment
Educational Readiness Review
1 Prepare Educational Readiness Report

Knowledge Transfer
Prepare for Key User Knowledge Transfer for <SCOPE

OPTION>
Perform Solution Walkthrough and knowledge transfer to

Key Users for <SCOPE OPTION>
1 Prepare End User Training Materials and Documentation
2 Set up Training Environment
3 Perform Training of the Trainers
4 Develop End User Training Schedule and Logistics plan
1 Configure General Settings
2 Configure Organizational Structure
2 Configure Master Data Objects #1 - n
2 Prepare Unit Test Cases
3 Prepare String Test Cases
4 Execute Business Process Unit Test
5 Perform defect resolution for Business Process Unit Test
End User Training Delivery Enabled
Configured General Settings and Organizational Structure
Configured Master Data Objects #1 - n
Prepare and Load master data - Master Data Object

<MASTER DATA OBJECT NAME>
Core Configuration and Documentation - Process #1 - n
Complete Core Configuration, including documentation

and test cases
6 Execute Business Process String Test
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
3 12
Develop, document and test Composite and/or Mobile

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

Application
3 13
Business Process Procedure
3 13
1 Develop Business Process Procedure Document
3 13
3 14
Validate and Complete Business Process Procedure

Document
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
3 16
3 16
Quality Assurance Environment (QAS)

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

Environment
Set up Role Assignment / Authorizations / Test Users in

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

Check
3 18
2 Conduct Production Support Readiness Check
3 18
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
Conduct Master Data Process Governance Readiness

Check
Approved Integration Test
Prepare Integration Test Plan, including test of roles and

authorizations
3 19
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
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
3 21
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
Prepare and Document User Acceptance Test Cases for

<SCOPE OPTION>
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
3 23
3 23
Production Environment (PRD)

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

Environment
Set up Role assignment / Authorizations / Test Users in

PRD for <SCOPE OPTION>
Populate PRD with Test Master Data for <SCOPE
5
OPTION>
Prepare and Load master data into PRD environment for
6
<SCOPE OPTION>
Perform Manual Configuration Settings in PRD for
7
<SCOPE OPTION>
3 24
Failover Environment
3 24
1 Prepare Failover Environment Design and Plan
3 24
3 24
3 Obtain Failover Environment Test Results
3 25
Set-up Failover Environment and Execute Identified

Scenarios
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
3 26
3 27
3 27
3 28
Perform SAP Going Live Check - Analysis Session and

schedule the Verification Session
System User Roles and Authorization Administration
Set up administrative procedures for Roles and

Authorizations
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
3 29
3 30
3 30
Technical Integration Check
1 Conduct TIC Service
3 30
2 Conduct Project Quality Gate(s)
3 30
3 30
4 Conduct Design Review Service
3 30
3 30
3 31
MILESTONE: Test to Deployment
Final Preparation
Phase Initiation
1 Perform Business validation and Transition Planning
3 Establish Business Process Operations
4 Establish System Administration and Control
5 Establish Security / Role and Authorization Management
6 Execute Transition to Production Support
1 Validate and adapt end user training material developed
2 Deliver End User training
Organizational and Production Support Readiness Check
Validate that Master Data Support Processes is

established
Pre Go-Live End-User Training Delivery
3 Collect Training Evaluations feedback
4 Perform People Readiness assessment
1 Execute Technical System Tests
2 Perform System Test Defect Resolution
3 Obtain System Test Results Sign-off
1 Execute Go Live Simulations 1 thru N
2 Conduct Data Quality Readiness Check
3 Finalize Cutover Plan
4 Perform Pre-Cutover Weekend Closing Activities
Final Check of Production Readiness and Sign-Off for

transition to Production
Perform Cutover Weekend Activities including Final

Production Data Load
7 Obtain Production Data Load Sign-off
Approved Technical System Tests
Production Cutover
Initiate Solution Manager Update - Solution

Documentation
MILESTONE: Production System Live
Go Live Support
Phase Initiation
1 Prepare End-User Training for <SCOPE OPTION>
2 Deliver End-User Training for <SCOPE OPTION>
3 Collect Training Evaluations feedback
4 Perform People Readiness assessment
1 Provide Post Go Live Support
2 Monitoring Open Issues to Resolution
3 Resolve Functional Issues
Knowledge Support Strategy
Define Mid-Term and Long-Term Knowledge Support

Strategy for Customer
Post Go live End-User Training
SAP Going Live Check - Verification Session
Conduct SAP Going Live Check - Verification Session

Remote
Production Support After Go Live
4 Resolve Technical Issues
Complete Transition to Customers Production Support

organization
Finalize Solution Manager Update - Solution

Documentation
Obtain Solution Transition to Production Acceptance

Protocol Sign-off
MILESTONE: Deploy to Run
End User Acceptance Survey
1 Prepare and distribute Survey to EU
Project Closure and Sign-Off Project Deliverables
5 Resolve and close open issues
6 Finalize Project Closeout Report
Obtain Sign-off for Project Closure and Results

Acceptance
5 10
MILESTONE: Project Complete
Operate
Operations Maturity Assessment
2 Prepare Maturity Assessment Report
Perform evaluation and assessment of operations

capabilities, including CoE operational set up
Solution Documentation Optimized
1 Perform assessment of Solution Documentation set up
Solution Implementation Optimized
1 Perform assessment of Solution Implementation set up
Template Management Optimized
1 Perform assessment of Template Management set up
Test Management Optimized
6 10
1 Perform assessment of Test Management set up
Change Control Management Optimized
Perform assessment of Change Control Management set

up
Application Incident Management Optimized
1 Perform assessment of Incident Management set up
Technical Operations Optimized
1 Perform assessment of Technical Operations set up
Business Process Operations Optimized
1 Perform assessment of Process Operations set up
Maintenance Management Optimized
6 10
6 11
6 11
1 Perform assessment of Maintenance Management set up
Upgrade Management Optimized
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 customers
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
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.
Mandatory
The purpose of this task is to define the organizational structure, roles and
responsibilities of the project team.
Mandatory
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 terms. This information and supporting documents align key
stakeholders around the strategic intent of the project.
Mandatory
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
Mandatory
all 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 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 the
Mandatory
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 basis
Mandatory
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 assign
Mandatory
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
against which tracking, change management and status reporting is done.
Mandatory
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 defined in the project charter.
Mandatory
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 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 lifecycle and designed to decouple technical installation Optional
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
Optional
ensure 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 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.
Optional
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
Optional
operations in SAP Solution Manager, including End-to-End 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 nonevent 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, costs
etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
Mandatory
status and progress of the project including potential disturbances due to
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 each other
Optional
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 decomposition of the Mandatory
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 establishing a Optional
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 necessary Optional
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 twoday scoping workshop to explain the SAP data migration approach and to
understand the customers 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 SAPs 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

Optional
implementation 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 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 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.
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 SAPs 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 customers
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
phase.
Mandatory
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.
control.
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
management process.
management plan.
etc.
Mandatory
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 Mandatory
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
Optional
stakeholders, as well as the ways they can influence the project. Execute an
analysis of current state asis and future state tobe 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
Optional
change management starts and against which progress and success of the
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
and corresponding activities to prepare the end users for using the new
system.
Mandatory
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
Fosters teamwork within project teams

The purpose of this task is to train the key users for the solution in scope (predefined 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
on the process scope.
It is best to store all organizational structure deliverables in the process
hierarchy in SAP Solution Manager.
Mandatory
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, Consistent
Mandatory
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 and Mandatory
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
35 are defined.
The purpose of this deliverable is to design, in detail, the to-be business

Mandatory
process down to activity level (PL 3-5) and to describe gaps where the
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
Optional
to monitor and controls the predefined KPI's and PPI's of the to-be process
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 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.
Mandatory
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 during Mandatory
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
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 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
Mandatory
Mandatory
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 functionaland 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
the project.
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 that
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
phase.
Mandatory
control.
management process.
management plan.
etc.
Mandatory
Mandatory
Mandatory
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 customers
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
Optional
availability of end user training material, training environment, 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 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
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 the system
on the basis of the decisions made in the business blueprint phase.
Optional
Optional
Mandatory
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 requirements specified in the business blueprint phase.
Mandatory
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 perform unit test for the configuration
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.
Optional
The purpose of this task is to perform string test for the configuration
Optional
The objective of this task is to resolve any issues identified during the 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 reported
The purpose of this deliverable is to develop and test the RICEFW objects.
Documentation to be stored in Solution Manager.
Mandatory
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
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
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
designated re-testers) and that they are confirmed.
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
solution and the hyper care period immediately following go-live.
Mandatory
The purpose of this task is to assess to what level the organization is prepared
Optional
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
interfaces and can be executed in an iterative manner.
Mandatory
The purpose of this task is to define and document integration test cases, endto-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
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,
Mandatory
transform, and enrich legacy 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 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
Mandatory
team can monitor the accuracy and efficiency of the data migration solution.
The purpose of this task is to provide one final assessment at the end of the
realization phase to report on the quality of the converted legacy data
Mandatory
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 Mandatory
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.
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 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 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.
Mandatory
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 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
Continuity Management (ACM)
Optional
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, 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.
Mandatory
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

deliverable is to establish an effective operation processes for security
Optional
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, and
Optional
prepare a strategy to hand off operations of the solution landscape to the postproduction 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
the project.
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
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.
phase.
Mandatory
control.
management process.
Mandatory
management plan.
etc.
Mandatory
Mandatory
The purpose of this survey is to take the pulse of the organization, prior to golive, 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 stakeholders Optional
in order to gain sponsors approval.
The purpose of this task is to ensure the customer establishes the means to
manage their data in an integrated environment.
This task provide a single defined support approach for monitoring and
measuring the customers daytoday support operations. The following four
topics needs to be covered:
- Exception Handling and Business Process and Interface Monitoring
- Data Volume Management
- 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
triggered and managed from a central administration system.
Optional
Optional
Optional
The task ensure that the customer establishes the means to manage security,
Optional
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 customers 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 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.
Optional
The purpose of this task is to capture feedback on both the training session
and the trainer delivering the material
Optional
This task checks how prepared the people in the organization are with regards
Optional
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,
sequence, and duration of items on the cutover plan.
Mandatory
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
Mandatory
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
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
Optional
the project.
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.
phase.
control.
Mandatory
management process.
management plan.
etc.
Mandatory
Mandatory
Mandatory
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
Optional
have adopted the solution, knowledge resources are maintained, and
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.
Optional
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.
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 customers production
environments to the long-term SAP support center team.
Optional
content, and set up as a productive solution in SAP Solution Manager. This
Optional
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 golive. 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
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
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 enterprises 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
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
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
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
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
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
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.
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.
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
nonevent for the business.
gaps exist for the Upgrade Management area.
Q-Gate Key Deliverable Work Stream
Accountable Role
_Phase
PM - Project Management
Project Guideline (incl.

Travel Guideline)
Project Manager
Project Manager
Steering Committee
Definition, Org-Structure, PM - Project Management
Roles
Project Manager
Project Manager
Project Manager
Project Charter
Phase Kick Off Meeting
Project Manager
OCM - Organizational
Change Management
Project Manager
Project Manager
Project Manager
Project Manager
Scope Statement
Document
Work Breakdown
Structure (WBS)
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Schedule (incl.

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

Management

Management
Technology Architect
Solution Manager Usage

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

Management
Application Consultant
Test Management
Standards
ISM - Test Management
Test Management
Consultant
Change Request and

Transport Management
Standards (CTS)
TSM - Technical Solution

Management

Management
Post Implementation
Service and Support

Management
Technology Consultant

Management

Management

Management
Project Manager
Project Manager
Risk List (internal &

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

Plan & Schedule
Training - Training
Education Consultant
Training - Training
Training - Training

Business Process List
BPM - Business Process

Management
Management
Management
Management
Management
Value Map
Value Audit of Scope

Management

Management
VM - Value Management
Business Consultant
Business Consultant

Management
Management
Business Consultant

Management

Management
Project Manager
Data Migration Approach,

DM - Data Migration
Start and Scope
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
Solution Landscape
Design

Management

Management
Management
Solution Architect

Management
Management
Management
Management
Solution Architect
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)
Project Manager
Business Manager
Project Manager
Project Manager
_Milestone
_Phase
milestones)
Project Manager
Project Manager
Project Management
Plan(s)
Project Manager
Project Manager
Project Manager

Project Manager
Report (internal &
external
Project Manager
(Internal)
Change Management
Organizational Change
Management Plan
Business Readiness
Approach
Change Management
Business Consultant
Change Management
Change Management
Change Management
Business Consultant
Change Management
Business Consultant
Change Management
Training Project Plan
End User Training and

Documentation
Developed
Change Management
Business Consultant
Change Management
Business Consultant
Training - Training
Training - Training
Training - Training
Training - Training
Training - Training
Business Consultant
Training - Training
Instructor
Training - Training
Training - Training
Training - Training

Management

Management

Management

Management

Management
Integration Development
Consultant

Management

Management
Business Blueprint
Documents(Org
Structure)
User Role Document
Solution Documentation

Management

Management

Management

Management

Management

Management

Management

Management
Management

Management

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

Management

Management

Management

Management
Consultant

Management
Consultant

Management
Data Migration Design /

Plan
Test Cases & Results

Management

Management
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DA - Data Archiving
DA - Data Archiving

Management

Management
Management
Authorization
Requirements and
Design

Management
Solution Landscape
Design

Management
Management
Management
Management
Management
Management
Management
Management
Management
Test Strategy Plans &

Results
Delivery of projects
Results
Delivery Acceptance
Protocol
DM - Data Migration

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

Project Manager
Report (internal &
external
Project Manager
Change Management
User Role Document
Change Management
Business Consultant
Change Management
Business Consultant
Change Management
Business Consultant
Training - Training
Training - Training
Training - Training
Training - Training
Training - Training
Documentation
Developed
Training Environment
Population and Testing
End User Training

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

Management
Management
Management
Management
Management

Management

Management
Developments)
Management
Management
RICEFW, SOA,
Migration)

Management

Management

Management

Management
Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management

Management
Consultant

Management
Consultant

Management
Consultant

Management
Management
Management
Business Consultant
Solution Landscape
Design

Management
Management
Management

Management

Management
DM - Data Migration

Management
_Milestone
Production Cutover Plan
CutOver - Cut Over

Management
Business Readiness
Approach
Change Management
Project Manager

Results

Plan
Change Management
Project Manager
DM - Data Migration
CutOver - Cut Over

Management
CutOver - Cut Over

Management
Project Manager
CutOver - Cut Over

Management
Project Manager
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
Testplans & Results UAT
Testplans & Results Regression
Project Manager
DA - Data Archiving
DA - Data Archiving
DA - Data Archiving
DA - Data Archiving
DA - Data Archiving
Solution Landscape
Design

Management
Management
Management
Design, Setup and Test
Results

Management
DM - Data Migration
DM - Data Migration

Management

Management

Management

Management

Management
Management
Test Plans & Results
Test Management
Consultant

Management

Management
System User Roles and

Authorization
Administration
and
System Authentication
Management

Management

Management
Technical Operations and TSM - Technical Solution

Handover Strategy
Management
Management
Management
Management
Technical Integration
Check
CutOver - Cut Over

Management
CutOver - Cut Over

Management
Results
Delivery Acceptance
Protocol

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

Project Manager
Report (internal &
external
Project Manager
Change Management
Functional/Technical
Requirements and
Production Support
Processes Defined
Master Data Support
Processes Established
Change Management
Business Consultant
DM - Data Migration
Business Process
Operation

Management
System Administration
and Control

Management
Security / Role and

Authorization
Management

Management
Transition to Support

Management
Training - Training
Training - Training
Training - Training
Training Evaluations
Training - Training
End User Training

Delivery and Readiness
Checklist
Change Management
CutOver - Cut Over

Management
Testplans & Results
CutOver - Cut Over

Management

Plan
DM - Data Migration
CutOver - Cut Over

Management
CutOver - Cut Over

Management
CutOver - Cut Over

Management
CutOver - Cut Over

Management
CutOver - Cut Over

Management
Project Manager
Solution Manager
Update,
CutOver - Cut Over

Management
Results
Delivery Acceptance
Protocol
Readiness for Cutover Signoff

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

Project Manager
Report (internal &
external
Project Manager
Training - Training
Training - Training
Go-Live Training
Sessions
Training - Training
Training - Training
Training - Training
Training - Training
Change Management

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

Management
CutOver - Cut Over
Management
CutOver - Cut Over

Management
Project Manager
CutOver - Cut Over

Management
CutOver - Cut Over

Management
Transition to Standard
Support Processes,
System Administration
and Control

Management
Solution Manager
Update,

Management
Project Manager
_Milestone
Change Management
Change Management
Business Consultant
Results
Delivery Acceptance
Protocol

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
_Milestone
_Phase
Business Consultant
Project Manager

Management
Management

Management

Management

Management

Management
Management

Management
Test Management
Consultant

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management
WBS #
WBS item title
Project Preparation
Project Initiation

management

1
Project Governance
1 Define Agile Project Organization and Roles
Complete communication management plan

1
Project Charter
Prepare Project Charter Document

1
1
Identify Stakeholders
Set Stakeholder Expectations for Agile Project
Obtain Project Charter Sign-off
Kick-Off Workshop
1
Prepare for Kickoff Meeting

1
Perform Kickoff Meeting

1
Scope Statement
Document Customer Requirements
5
1
5
1
3 Determine Gap List and Effort Estimation

1
Communicate result of fit gap analysis including

effort estimates
Create Work Breakdown Structure and WBS

Dictionary
7 Obtain customer sign off for project scope
Define Initial Release and Sprint schedule, Assign

Resources
1
1

1
Prepare Project Management Plan

1
Obtain Project Management Plan Sign-Off
8
1
Define and Set Up Agile Project Standards and

ALM Tools
4 Determine Template Management Procedure
Determine Change Control Management

Procedure
Determine Application Incident Management

Procedure
8 Determine Technical Operations
9 Determine Business Process Operations
10 Determine Maintenance Management
11 Determine Upgrade Management
9
Direct and manage project execution
Monitor and control project activities

1
Manage Issues, Risks and Changes
3
Communicate Status and progress to project
stakeholders

1
10
Prepare Organizational Change Management
Roadmap
10 1
Project Training Strategy and Plan (team + keyusers)
11
11 1
Prepare training strategy and plan document

1
12
12
1 Conduct Agile Training for the Project Team
13
Prepare Business Process Map
13 1
Prepare Demo Environment for Scope
Refinement Workshops
13 2
Prepare Scope Document for Workshop

1
13 3
For <SCOPE OPTION> - Demonstrate the

business processes and predefined options list
1
13 4
Complete Customer Blueprint and Configuration

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

1
14 1
Define and Prioritize Epics
14 2
Validate and Complete Value Map

1
14 3
Business Scenario Design

1
15
Capture Business Scenario Requirements

1
15 1
Validate and Complete Scenario Design

1
15 2
Store Scenario Level Solution Documentation in
SAP Solution Manager.
15 3
Prepare Testing Policy
16
Prepare Testing Policy document
16 1
16 2
Obtain Customer Sign-Off for Testing Policy

document
17
17 1
Prepare Data Migration Workshop
Conduct Data Migration Workshop

1
17 2
Conduct Data Audit (Data Health Check)
17 3
Document
17 4
17 5
Present DM scope and requirements document
Conduct Organizational Assessment for Data

Migration
1
17 6
Conduct Infrastructure Assessment for Data

Migration
1
17 7
Conduct Risk Assessment for Data Migration and

Prepare Mitigation Plan
17 8
Complete the Data Migration approach and
strategy document
17 9

18
Define Solution Landscape Concept
18 1
Define Solution Deployment Concept
18 2
Interface Inventory
1
19
Prepare Interface Inventory document
19 1

1
20
Complete HW sizing estimation for solution
landscape
20 1
21

backend)
1
21 1
Verify Functional System Requirements

1
21 2
Check availability of SAP Solution Manager
21 3
Install or Upgrade SAP Solution Manager
21 4
Set up Business Process Hierarchy in SAP

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

including team collaboration environment
1
21 6
Install SAP GUI on project team computers
21 7
Test Remote Access and Establish OSS
Connection (both GUI and Web Access)
21 8
Prepare authorization roles in the systems for the
project team (DEV)
21 9
Set up of testing tools
21 10
22
22
Conduct Knowledge Management Gate
Conduct Project Quality Gate
22
Conduct Project Management Review Service
22
3
22
Obtain Customer Sign-Off for Phase Completion

4
23
Lean Blueprint
2
Phase Initiation
2
1
Allocate Resources and Update Project Schedule

2
2
Update Project Management Plan
1
Conduct SCRUM Meetings

2
5
stakeholders
Conduct classification of project Stakeholders

2
1
Identify Key Users

2
4
Validate organizational alignment approach
Establish Baseline of Current State

2
Communication Plan
Define Value Argumentation / Key Messages
1
Define Communication strategy

2
Conduct Learning Needs Analysis
1
Develop Detailed End-User Training Plan

2
Conduct Blueprint Ramp-up Training
Conduct Key User training
End User Training Content

2
8
Adaptation of Pre-delivered Training Content
Prepare and Build Training Content in Project

Environment
Scope Validation
For <General Settings #1 - n> - Conduct

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

Fit-gap Analysis
For <Process #1 - n> - Conduct Validation and Fitgap Analysis
3
Validate pre-defined RICEFW Objects (reports,
forms etc.)
5 Determine Gap list and Update Product Backlog
Business Solution Design for Business Objects
10
Define Business Organization Structure
10 1
Define General Settings and Master Data
10 2
Define User Role Concept
10 3
Define Logical Data Model
10 4
Detailed Design - Business Scenario #1 -n
11
1 Complete Business Scenario Design Document
11
2 Refine Epics and Update Product Backlog
11
Detailed Design - Business Process #1 - n

2
12
1 Complete Business Process Design Document
12
2 Demo or Visualize Standard Functionality
12
3 Define User Stories and Update Product Backlog
12
Value Realization
2
13
Prepare Value Dashboard

2
13 1
Detailed Design - Configuration and

Enhancements
14
Finalize Core Configuration Design
14 1
Finalize Delta Configuration Design
14 2
Define functional Design - RICEFW Object #1 - n
14 3
Define Functional Design - SOA & 3rd party
applications #1 - n
14 4
Baseline Build Plan

2
15
Define Baseline Build Feature Set
15 1
Conduct Baseline Sprint Planning Meeting
15 2
Baseline Build
16
Build Baseline User Stories (Iterative)
16 1
Demo Baseline Feature Set and Solicit Feedback

(Iterative)
16 2
Visualization
2
17
1 Capture Initial Visualization Requirements
17
2 Build Visualization (Iterative)
17
Demo Visualizations and Solicit Feedback

(Iterative)
17
Baseline Build Sign-Off
18
Conduct Baseline Build and Visualizations Demo
18 1
Conduct Acceptance Testing of Baseline Build

2
18 2
Finalize Documentation of Baseline Build
18 3
Signoff Baseline Build and Visualizations

2
18 4

2
19
Ensure Master Data Management Processes
Ownership
19 1
Conduct Data Mapping workshops (master data
for pre-defined solutions)
19 2
Conduct Data Quality Assessment
19 3
Define Automated Data Migration Approach

2
19 4
Define Manual Data Migration Approach

2
19 5
Prepare Data Quality Plan
19 6
Prepare Data Security Design and plans
19 7
Legacy Data Archive

2
20
Prepare baseline framework for the legacy data

archiving solution
2
20 1
Technical Solution Design
21
Prepare technical infrastructure specification
21 1
Identify System Environment for Baseline Build

and Baseline Acceptance
21 2

2
22
Authorization Requirements and Design

2
22 1
Development Environment (DEV)

2
23
Execute Technical Installation of SAP Products
for DEV environment
23 1
Execute Technical Upgrade of SAP Products for
DEV environment
23 2
Install Solution Documentation in Solution
Manager
23 3
Execute Technical Installation of 3rd party
products
23 4
Set up Role assignment / Authorizations / Test
Users in DEV
23 5
Perform Manual Configuration in DEV
23 6
Validate Role assignment / Authorizations / Test
Users in DEV
23 7
Create master data in DEV environment - Master
Data #1 - n
23 8
Testing Strategy
24
Prepare Test Strategy document

2
24 1
Review and Validate Testing Strategy with
customer
24 2
24 3
Obtain customer sign-off on Testing Strategy.
Release and Sprint Plan

2
25
Update Product Backlog
25 1
Conduct Release Planning Meeting
25 2
Validate Release and Sprint Plan Against SOW
25 3
26
26 1
26 2
Execute Baseline Retrospective
26 3
26 4
Conduct Design Review Service
26 5
Manage Fulfilled Contracts

2
26 6
26 7
27

Realization
3
Phase Initiation
3
1

3
2
Sprint Initiation (Iterative)
Conduct Sprint Planning Meeting (Iterative)
3
Perform Sprint Execution Activities (Iterative)
2

3
5
stakeholders
Perform Scrum-Of-Scrums Meeting (Iterative)
Execute Role Mapping and Transition Planning
1
Conduct Sounding Board/Pulse Checks
Communicate Sprint Scope and Plan (Iterative)
Communicate Sprint Result (Iterative)
Refine and Execute Communication Plan

3
Educational Readiness Review

3
5
Prepare Educational Readiness Report
Prepare End User Training Materials and

Documentation
1
Set up Training Environment
6
3
6
3
Perform Training of the Trainers

3
Develop End User Training Schedule and
Logistics plan
6
3
Configured General Settings and Organizational

Structure
Configure General Settings
1
Configure Organizational Structure
7
3
Configured Master Data Objects #1 - n
Prepare and Load master data - Master Data

Object <MASTER DATA OBJECT NAME>
1
Configure Master Data Objects #1 - n
8
3
Core Configuration and Documentation - Process

#1 - n
Complete Core Configuration, including

documentation and test cases
1
Prepare Unit Test Cases
9
3
2
Prepare String Test Cases
9
3
3
Execute Business Process Unit Test
9
3
Perform defect resolution for Business Process

Unit Test
9
3
5
Execute Business Process String Test
9
3
Perform defect resolution for Process String Test
9
3
10
Delta Configuration - Process #1 - n
10
Complete Delta Configuration
1
Complete Delta Process Documentation
10
3
2
Complete Delta Process Test Cases
10
3
3
Execute Business Process Unit and String Test
Cases
10
3
Perform defect resolution for Unit and String Test
10
3
11
Enhancement Development - RICEFW Object #1 n
11
Develop RICEFW Object #1 - n
11
3
Document RICEFW Object #1 - n

2
Execute Test Cases - RICEFW Object #1 - n
11
3
Perform defect resolution for RICEFW Object(s)

Test
11
3
4
Conduct Final Code Review
11
3
12
12
Develop Business Process Procedure Document
1
Validate and Complete Business Process
Procedure Document
12
3
13
Value Audits
13
Perform Value Audit
1
14
Scenario Test #1 - n
3
14
3
3
Prepare Test Case - Scenario #1 - n

1
14
14
3
Execute Test Case - Scenario #1 - n
Resolve Issues for Scenario #1 - n

3
14
3
Obtain Customer Sign-off for Testing of Scenario

#1 - n
15
15

for QAS environment
1
QAS environment
15
3
Import Configuration and Development Objects to

QAS Environment
15
3
3
Set up Role Assignment / Authorizations / Test
Users in QAS
15
3
4
Prepare and Load Master Data into QAS
Environment for <SCOPE OPTION>
15
3
5
15
6 Perform Manual Configuration Settings in QAS
3
16
17
Sprint Closing
17
Conduct Sprint Review Meeting
17
Signoff Sprint Results
Conduct Sprint Retrospective
17
18
18
Conduct Organizational Change Management

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

Readiness Check
19
Approved Integration Test
19
Prepare Integration Test Plan, including test of

roles and authorizations
1
19
19
3
Prepare and document Integration Test Case #1 n
Execute Integration Test Case #1 - n

3
19
3
Perform defect resolution for Integration Test

4
19
3
Obtain Integration Test Results Sign-off

5
20
20
Develop Data Migration Program Units
1
20
Execute and validate Manual Data Migration

2
20
3
Obtain Data Quality Reports

3
Perform SAP Target Load Test
20
3
4
Obtain Data Migration Test Results
20
3
5
Conduct Final Data Quality Assessment
20
3
21
Approved User Acceptance Test
21
Prepare UA Test Plan for <SCOPE OPTION>
1
Prepare and Document User Acceptance Test
Cases for <SCOPE OPTION>
21
3
21
3
Execute UA Test Plan for <SCOPE OPTION>

3
Perform UA Defect Resolution for <SCOPE

OPTION>
21
3
4
21
Obtain UA Test Results Sign-off

5
22
SAP Data Archiving
22
Capture Legal and Business Retention

Requirements
Prepare Data Archive Plan
22
3
Prepare Data Archive Storage Plan
22
3
3
3
22
Conduct Data Archive Implementation Test
23
23

for PRD Environment
1
PRD Environment
23
3
2
PRD Environment
23
3
3
Set up Role assignment / Authorizations / Test
Users in PRD for <SCOPE OPTION>
23
3
4
Populate PRD with Test Master Data for <SCOPE
OPTION>
23
3
5
Prepare and Load master data into PRD
environment for <SCOPE OPTION>
23
3
6
23
Perform Manual Configuration Settings in PRD for

<SCOPE OPTION>
24
24
Prepare Failover Environment Design and Plan
Set-up Failover Environment and Execute

Identified Scenarios
24
3
2
Obtain Failover Environment Test Results
24
3
25
System and Performance Test
25
Prepare System Test Plan
1
Prepare Performance Test Plan
25
3
3
3
2
25
25
3
4
25
3
3
Prepare Performance Test Cases
Execute Performance Tests
25
3
Prepare System Test Cases
Perform Performance Test Defect Resolution

6
25
Obtain Test Results Sign-off
26
26
Perform SAP Going Live Check - Analysis

Session and schedule the Verification Session
27
System User Roles and Authorization

Administration
27
Set up administrative procedures for Roles and

Authorizations
28
28
Validate Support Center/Help Desk Staffing

Strategy
1
Establish Support Processes
28
3
2
Set-up Business Process Monitoring
28
3
29
29
Conduct Project Quality Gate(s)
29
29
Conduct Design Review Service
29
29
3

5
29
3

6
30
Final Preparation
Phase Initiation
4
1

4
2
1

4
4
stakeholders
Organizational and Production Support

Readiness Check
Perform Business validation and Transition

Planning
1
Validate that Master Data Support Processes is
established
Establish Business Process Operations
Establish System Administration and Control

4
4
Establish Security / Role and Authorization
Management
Execute Transition to Production Support

4
Validate and adapt end user training material

developed
Deliver End User training

4
Collect Training Evaluations feedback
Perform People Readiness assessment

4
5
Execute Technical System Tests
1
Perform System Test Defect Resolution
Obtain System Test Results Sign-off
Production Cutover
4
Execute Go Live Simulations 1 thru N

4
1
Conduct Data Quality Readiness Check
Finalize Cutover Plan
Perform Pre-Cutover Weekend Closing Activities

4
4
Final Check of Production Readiness and SignOff for transition to Production
Perform Cutover Weekend Activities including

Final Production Data Load
Obtain Production Data Load Sign-off

Documentation
4
8
Release Closing
Prepare Product Backlog for Next Release/Sprint
Conduct Release Retrospective
Update the Release and Sprint plan

4

4

4
Go Live Support
5
Phase Initiation
5
1

5
2
1

5
4
stakeholders
Prepare End-User Training for <SCOPE

OPTION>
1
3
2
3
Deliver End-User Training for <SCOPE

OPTION>
Collect Training Evaluations feedback
3
Perform People Readiness assessment
3
5
Conduct SAP Going Live Check - Verification

Session Remote
Provide Post Go Live Support
1
5
Monitoring Open Issues to Resolution

2
5
5
Resolve Functional Issues

3
5
5
Resolve Technical Issues

4
Complete Transition to Customers Production

Support organization
Finalize Solution Manager Update - Solution

Documentation
5
5
6
Obtain Solution Transition to Production
Acceptance Protocol Sign-off
5
5
7
6
7
5

4
7
5
Resolve and close open issues

5
7
5
Finalize Project Closeout Report

6

Acceptance
5
8
MILESTONE: Project Complete
Operate
6
6

6
Prepare Maturity Assessment Report

6
2
Perform assessment of Solution Documentation
set up
3
Perform assessment of Solution Implementation
set up
4
Perform assessment of Template Management
set up

6
Perform assessment of Test Management set up

6
6
Perform assessment of Change Control
Management set up
7
Perform assessment of Incident Management set
up
8
Perform assessment of Technical Operations set
up
9
Perform assessment of Process Operations set
up
10
Perform assessment of Maintenance
Management set up
10 1
11
Perform assessment of Upgrade Management set
up
11 1
Description
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 customers 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 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 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 that consist of SCRUM master, Product Owner 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 fully
implement feature in iteration.
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 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 task is to build agile awareness of key stakeholders, secure commitment to
adopt standard SAP functionality where possible. It is recommended to conduct informal and
formal meetings to set the expectations and confirm the project approach with key project
stakeholders.
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 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 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-/nonprocess-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 determine all gaps for customer solution, document them formally
and estimate effort to cover the identified gaps.
The objective of this task is to present the results of fit gap analysis to customer including the
effort estimates to cover the identified gaps as part of the project/service delivery.
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 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.
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.
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 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 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 define and set up SCRUM standards and tools, such as SCRUM board, burn-down chart, product ba
The purpose of this task is to determine the customers framework to centrally document and relate
business processes and technical information of SAP 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
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 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 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
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 nonevent 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, 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 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 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 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 educate project team on Agile implementation approach, principles
and techniques.
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 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 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 for the Product 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?
HighLevel Business Process scope: What 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 user stories.
The purpose of this task is to validate that identified key process changes, key performance
indicators, and value enablers are accurate and make 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 predefined 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 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 customers 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.
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 SAPs
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.
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 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)
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
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 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 SAPs 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 customers 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 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 management process.
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
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 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 analysis of current state asis and future state tobe
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 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 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 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 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:
Provides guidance for blueprinting workshops and relevant enabling tools
Prepares for essential blueprinting skills, such as workshop facilitation, requirements

gathering, and process modeling
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 predelivered 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 crossprocess 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.
The purpose of this task is to capture all identified delta requirements from the validation sessions
in the product backlog.
The requirements are captured in form of user stories that define the requirement from end-user
perspective, provide details on how to test the feature when it is completed, priority of the backlog
item and business value.
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 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, 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 and processes. This information is populated in
the business process hierarchy in SAP 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 35 are defined.
The purpose of this task is for the Product Owner team to decompose the 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 the business scenarios and processes (down to
level 3) 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 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 to test the backlog item upon completion (e.g. definition of done for the feature)
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 standard solution does not cover all required
functionalities.
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 35) 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 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-user perspective, provide details on how to test the feature when it is
completed, priority of the 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
SCRUM team.
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 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 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 Baseline Build Plan is to define plan to setup fully functional environment to
demonstrate the standard functionality of the SAP solution to the customer product owner team,
key users and stakeholders.
The purpose of this task 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, understanding
of the solution, complexity of the 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 depending on the size and complexity of the 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
team.
The purpose of Baseline Build is to setup fully functional environment to demonstrate the standard
functionality of the SAP solution to the customer product owner team, key users and stakeholders.
The results of the demo is either acceptance of standard feature or new delta requirement that is
captured in the form of user story in the product backlog.
The purpose of this task is to build the baseline functionality defined in the baseline user story.
This is conducted in iterative fashion through out the baseline build. The outcome of this task is
fully functional baseline build of user story that is unit tested and ready for demo to the product
owner and key users.
The purpose of this task is to demo the baseline build feature (user story) to the key users and
product owner team to obtain acceptance or solicit input for delta requirement.
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 Build
Planning session.
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 initiate the work to document the visualization requirements as part
of the business process 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 in iterative fashion through out the baseline build. The outcome
of this task is visualization of the baseline build user story that is ready for demo to the product
owner and key users.
The purpose of this task is to demo the baseline build visualization to the key users and product
owner team to obtain acceptance or solicit input for delta requirement.
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 Build
Planning session.
The purpose of this deliverable is to obtain final sign-off for the baseline build (and 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.
The results of the demo is either acceptance of standard feature or in exceptional cases new 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 baseline
build.
The purpose of this task is for the key users and product owner team to conduct acceptance test
of the features built in the baseline build. This may also include walk-throughs of the visualizations
for features that have not been fully built in the system.
The purpose of this task is to complete documentation of the baseline build and capture it in SAP
Solution Manager. In particular this pertains to configuration documents, test cases, test scripts,
visualizations, etc. as defined in the project documentation standards defined in previous phase.
The purpose of this task is to formally signoff the baseline build, visualizations and product
backlog. This signals to the project team that 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, and
procedures to support the migration of legacy data 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 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 task is to define system environment that will be used for the baseline build. At
minimum the environment needs to have two systems Development and Quality Assurance. It is
recommended to also provide team with Sandbox environment where they can experiment with
the functionality during the baseline build.
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 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 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 realization of project
scope.
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)
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.
The objective of this task is to communicate the testing strategy (functional and performance) to
the customer project team and validate it.
The purpose of this deliverable is to refine the Initial Release Plan that was defined earlier. At this
time the team also defined sprint plan for the first few iterations.
The 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 the user
stories so they are clearly understood by the SCRUM teams. Each user story needs to have clear
definition of the requirement in the language of the customer, defined test criteria and assigned
business value.
The purpose of this task is to conduct release planning meeting to define scope of product
releases based on the prioritized product backlog. The meeting is lead by Product Owner 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 surfaced
during the baseline build that may not be part of the original scope and may require amendment of
SOW or Change Request. This task is the responsibility of SAP Project Manager and Chief
Product Owner/Sponsor from the customer side.

satisfaction
The purpose of this task is to conduct 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 team to adjust to changing project environment 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 backlog, prioritized and tracked along
with other user stories.
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
accepted.

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.
Implementation of the final solution in the development environment
Performance testing
starts.
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 Standup Meeting. The Daily Standup 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.
Scrumof 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 readystate 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.
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 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 customers view.
The purpose of this task is to communicate the scope and plan for the sprint to the users outside
of the core project team. This may include end users, key stakeholders, people external to the
project that have interest in information about the project plans and progress.
The purpose of this task is to communicate the sprint results to the users outside of the core
project team. This may include end users, key stakeholders, people external to the project that
have interest in information about the progress of the project and accomplishments of the project
team.
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 deliverable End User Training Content Enabled is to ensure availability of end
user training material, training environment, 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 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 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 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 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.
The purpose of this task is to implement the Core Configuration, write valid test cases and to
The purpose of this task is to perform unit test for the configuration
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
The objective of this task is to resolve any issues identified during the 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.
The purpose of this task is to implement the Delta Configuration, write valid test cases and to
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 objective of this task is to resolve any issues identified during the Unit and String Test. It is
they are confirmed.
The purpose of this deliverable is to develop and test the RICEFW objects. 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.
The objective of this task is to resolve any issues identified during the RICEFW object(s) Test. It is
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 the value audit deliverable during the realization phase is to monitor and control
the implementation of key process changes and value 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 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 designated re-testers) and that they
are confirmed.
The purpose of the quality assurance infrastructure and environment design and setup deliverable
is to install a viable, correctly configured technical QA 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 upgrade 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.
The purpose of this task is to prepare master data required for all business 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 this deliverable is to formally close the sprint by conducting the Sprint 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 item
or in cases the feature is not accepted the 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.
The purpose of this task is to obtain formal acceptance and signoff of the sprint results following
the sprint review meeting. The product owner team is the party that provides the sign-off to the
project team. In case some features are not accepted they are brought back into the product
backlog as requirement, properly prioritized and included in planning for next sprint.
The purpose of this task is to conduct retrospective meeting with the SCRUM team to identify
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 hyper care period
immediately following go-live.
The purpose of this task is to assess to what level the organization is 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 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
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 designated re-testers) and that they
are confirmed.
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 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 solution.
The purpose of this task is to provide one final assessment at the end of the 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 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 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
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 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 production environment to support productive
operations of the delivered solution.
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 ensure that appropriate master data is available for testing in the
production environment (system test).
The purpose of this task is to prepare master data required for all business 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 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, 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 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 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 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.
- Verification of the technical capabilities of the production environment (sizing plausibility)
- Check of version and release compatibility of all involved SAP components and Plug-Ins
The purpose of the System User Roles and Authorization Administration 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, 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.

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
accepted.

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.
starts.
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 stakeholders in order to gain sponsors approval.
The purpose of this task is to ensure the customer establishes the means to manage their data in
an integrated environment.
This task provide a single defined support approach for monitoring and measuring the customers
day-to-day support operations. The following four topics needs to be covered:
- Exception Handling and Business Process and Interface Monitoring
- Data Volume Management
- 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 triggered and managed from a central
administration system.
The task ensure that the customer establishes the means to manage 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 customers 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 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 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 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, sequence, and duration of items on the
cutover plan.
This task verifies that master data support is set up and process is operational
The purpose of this task is to complete the Cut Over plan with results 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.
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 hand over the finalized implementation project and it's content, and set
up as a productive solution in SAP Solution Manager. This provides the basis for the follow up
activities in the Run Phase.
The purpose of this deliverable is to formally close the release and prepare for next release and/or
sprint planning meeting.
The purpose of this task is to 'groom' the product backlog. Product Owner Team needs to detail
the user stories to ready them for next release/sprint planning meeting. The stories need to meet
definition of Ready for Build so they are understood by the SCRUM team and can be estimated
during the sprint planning meeting.
The purpose of this task is to conduct retrospective meeting with the project team to identify
The purpose of this task is to update the Release and Sprint Plan according to changed priorities
and focus of the team. It is accountability of Product Owner to maintain the Release and Sprint
plan and keep it current during the project.

satisfaction
accepted.
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.
starts.
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 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 ongoing 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.
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 customers production environments to the longterm 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. 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

satisfaction
accepted.
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
enterprises 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
from the implementation project and 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 across geographical distances from initial template
definition to template implementation and template optimization, for example as part of a global
rollout
from the implementation project and determine if 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
from the implementation project and 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 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
from the implementation project and determine if 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
from the implementation project and determine if 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
from the implementation project and determine if 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.
from the implementation project and 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 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.
from the implementation project and determine if 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-toend
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 nonevent for the business.
from the implementation project and determine if potential gaps exist for the Upgrade
Management area.
Q-Gate
Relevant
Q-Gate Key Deliverable
Work Stream
Accountable Role
_Phase
Mandatory
Project Manager
Project Guideline (incl. Travel

Guideline)
Project Manager
Mandatory
Project Charter
Project Manager
Project Manager
Mandatory
Mandatory
Project Manager
OCM - Organizational Change

Management
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Scope Statement Document PM - Project Management
Project Manager
Project Manager
Mandatory
Work Breakdown Structure

(WBS)
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Mandatory
Project Budgetplan (internal

& external)
Mandatory
Project Management Plan(s) PM - Project Management
Project Manager
Project Manager

Management
Project Manager
Mandatory

guideline,
Business Process Modeling
Standards

Management
Business Consultant
Optional
Software System
Configuration Standards,
Enhancement and

Management
Business Consultant

Management
Optional
Test Management Standards ISM - Test Management
Test Management
Consultant
Optional
Change Request and

Standards (CTS)

Management

Management
Optional
Post Implementation Service TSM - Technical Solution

and Support
Management

Management

Management

Management
Project Manager
Project Manager
Mandatory
Risk List (internal & external),

Project Change log, Project PM - Project Management
Issues log
Project Manager
Mandatory
Project (Performance) Report

Project Manager
Optional
OCM Roadmap

Management

Management
Business Consultant
Training - Training
Optional
Project Team Training Plan &

Training - Training
Schedule
Training - Training
Mandatory

Project Manager

Management

Management

Management
Optional
Optional
Value Map

Management

Management

Management

Management
Business Consultant
Business Consultant

Management

Management
Business Consultant

Management

Management
Optional

Start and Scope
Project Manager
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
Optional
Solution Landscape Design
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration

Management

Management
Solution Architect

Management

Management

Management

Management

Management
Optional
Proj Support Tools & Sys

Setup
Solution Architect

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management
Optional

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
_Milestone
_Phase
Mandatory

milestones)
Project Manager
Project Manager
Mandatory
Project Manager
Project Manager
Project Manager
Project Manager
Mandatory

Issues log
Project Manager
Mandatory

(internal & external
Project Manager
Optional
Optional
Optional
(Internal)
Management Plan
Business Readiness
Approach

Management

Management
Business Consultant

Management

Management

Management
Business Consultant

Management
Business Consultant

Management

Management
Business Consultant

Management
Business Consultant
Mandatory
Optional

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

Management

Management

Management

Management

Management
Consultant

Management

Management
Mandatory
Mandatory
Business Blueprint
Documents(Org Structure)
User Role Document

Management

Management

Management

Management
Mandatory
Mandatory

Management

Management

Management

Management
Optional

Management
Mandatory
RICEFW, SOA, Migration)
Business Consultant

Management

Management

Management

Management
Consultant

Management
Consultant
Project Manager
Project Manager

Management

Management

Management

Management

Management
Mandatory
Mandatory

Management

Management
Project Manager

Management

Management
Project Manager
Data Migration Design / Plan DM - Data Migration
Test Cases & Results
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
DA - Data Archiving
DA - Data Archiving

Management

Management

Management

Management
Mandatory
Authorization Requirements
and Design

Management
Mandatory

Management

Management

Management

Management

Management

Management

Management

Management

Management
Mandatory

Results
Project Manager
Mandatory
Delivery of projects Results

Delivery Acceptance Protocol
Optional

Learned (internal)
Project Manager
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
_Milestone
_Phase
Mandatory

milestones)
Project Manager
Project Manager
Project Manager
Mandatory
Project Manager
Project Manager
Project Manager
Mandatory

Issues log
Project Manager
Mandatory

Project Manager
Project Manager

Management
Optional
User Role Document

Management
Business Consultant

Management
Business Consultant
Project Manager
Project Manager

Management
Business Consultant
Training - Training
Training - Training
Optional
Optional

Training Environment
Population and Testing
Training - Training
Training - Training
Training - Training
Training - Training
Optional
End User Training Schedule

Training - Training
and Logistics
Mandatory
Solution Documentation (incl.

Process list, Configuration,
Management
Interfaces, Developments)

Management

Management
Mandatory
Mandatory
Optional
Optional

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management
Mandatory
Optional
Mandatory
Optional

Management
RICEFW, SOA, Migration)

Management

Management

Management

Management

Management

Management

Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management
Optional

Management

Management
Business Consultant
Optional
Mandatory

Management

Management

Management

Management

Management
DM - Data Migration

Management
_Milestone
Project Manager
Project Manager
Project Manager
Mandatory
CutOver - Cut Over Management
Optional
Business Readiness
Approach

Management
Project Manager

Management
Project Manager
DM - Data Migration
CutOver - Cut Over Management Application Consultant
CutOver - Cut Over Management Project Manager
Mandatory
Mandatory

Results
DM - Data Migration
DM - Data Migration
DM - Data Migration
DM - Data Migration
Mandatory
DM - Data Migration
Mandatory
DM - Data Migration
Mandatory
Testplans & Results - UAT
Mandatory
Project Manager
DA - Data Archiving
DA - Data Archiving
Mandatory
Optional
Design, Setup and Test
Results
DA - Data Archiving
DA - Data Archiving
DA - Data Archiving

Management

Management

Management

Management

Management
DM - Data Migration
DM - Data Migration

Management

Management

Management
Mandatory
Optional

Management

Management
Test Management
Consultant

Management

Management
Optional
System User Roles and

Authorization Administration
and
System Authentication
Management

Management

Management
Optional
Technical Operations and

Handover Strategy

Management

Management

Management

Management
Mandatory

Optional

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
Project Manager
_Milestone
_Phase
Mandatory

milestones)
Project Manager
Project Manager
Mandatory
Project Manager
Project Manager
Project Manager
Mandatory

Issues log
Project Manager
Mandatory

Project Manager

Management
Optional
Functional/Technical
Requirements and
Production Support
Processes Defined

Management
Business Consultant
Optional
Master Data Support

Processes Established
DM - Data Migration
Optional
Business Process Operation

Management
Optional
System Administration and

Control

Management
Optional
Security / Role and

Authorization Management

Management
Optional
Transition to Support

Management
Training - Training
Training - Training
Training - Training
Optional
Training Evaluations
Training - Training
Optional
End User Training Delivery

and Readiness Checklist

Management
Mandatory
Testplans & Results
Mandatory
Mandatory
Optional
Mandatory
Optional
Solution Manager Update,

CutOver - Cut Over Management Technology Consultant
Project Manager
Project Manager
Mandatory

Optional

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
_Milestone
_Phase
Mandatory

milestones)
Project Manager
Project Manager
Mandatory
Project Manager
Project Manager
Project Manager
Mandatory

Issues log
Project Manager
Mandatory

Project Manager
Optional
Go-Live Training Sessions
Training - Training
Training - Training
Training - Training
Training - Training

Management

Management
Optional
Support Process Enabled,

Governance Model for
Operations
Optional
Transition to Standard
Support Processes, System
Administration and Control

Management
Optional


Management
Project Manager
_Milestone
Mandatory

Optional

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
_Milestone
_Phase
Business Consultant
Project Manager

Management

Management

Management

Management

Management

Management

Management

Management
Test Management
Consultant

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management
WBS # WBS item title
Project Preparation
1 1
Project Initiation

management
1 1
1 1
1 1
1 2
Communicate the delivery model and made mobility

arrangements
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
1 5
Scope Statement
1 5
1 5
1 6
1 6
1 Develop delivery schedule and assign resources
1 6
1 6
1 6
1 6
1 7
Define Initial Release and Sprint schedule, Assign

Resources
1 7
1 Prepare Project Management Plan
1 8
1 8
1 8
1 8
1 8
4 Determine Change Control Management Procedure
1 9
1 9
1 9
1 9
1 9

stakeholders
1 10
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
1 12 1 Conduct Solution Training and knowledge transfer
1 13
1 13 1 Prepare Business Process Map

1 13 2 Validate and Complete business process map
1 14
1 14 1

Document
1 14 2
Complete the Data Migration approach and strategy

document
1 15

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
1 17 1 Complete HW sizing estimation for solution landscape
1 18
1 18 1

backend)
1 18 2 Validate connectivity to Cloud provider

1 18 3 Install or Upgrade SAP Solution Manager
1 18 4
Check connectivity of SAP Solution Manager to Cloud

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

Manager
1 18 6 Confirm availability of Solution Builder

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

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

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

customer landscape
1 19 2
Perform unit test of the Pre-Assembled Rapid

Deployment Solution
1 19 3
Perform post activation tasks related to the PreAssembled Rapid Deployment Solution
1 20
1 20 1 Conduct Project Quality Gate
1 21
Scope Validation
2 1
Phase Initiation
2 1
2 2
2 2
2 2
2 2
3 Conduct SCRUM Meetings
2 2
2 2
2 2
2 3

stakeholders
2 3
1 Conduct classification of project Stakeholders
2 3
2 Identify Key Users
2 4
2 4
1 Validate organizational alignment approach
2 4
2 Establish Baseline of Current State
2 5
2 5
1 Conduct Learning Needs Analysis
2 5
2 Develop Detailed End-User Training Plan
2 6
2 6
1 Conduct Blueprint Ramp-up Training
2 7
2 7
Scope Validation
For <General Settings #1 - n> - Conduct Validation

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

Analysis
2 7
Validate pre-defined RICEFW Objects (reports, forms

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
2 9
1 Authorization Requirements and Design
2 10
Pre-Assembled Rapid Deployment Solution Transfer

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

On-premise
2 10 2 Install Solution Documentation in Solution Manager

2 10 3
Validate Role assignment / Authorizations / Test Users

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

master data
2 11 2 Review and Validate Testing Strategy with customer
2 12
2 12 1 Conduct Project Quality Gate
2 13
Realization
3 1
Phase Initiation
3 1
3 2
3 2
3 3

Sprint Initiation (Iterative)
1 Conduct Sprint Planning Meeting (Iterative)
3 3
1 Perform Sprint Execution Activities (Iterative)
3 3
3 3
3 3
3 3
3 3
6 Perform Scrum-Of-Scrums Meeting (Iterative)
3 4
3 4
1 Execute Role Mapping and Transition Planning
3 5
3 5

stakeholders
Knowledge Transfer
1
For <SCOPE OPTION> - Prepare for Key User

Knowledge Transfer
For <SCOPE OPTION> - Perform Solution

Walkthrough and knowledge transfer to Key Users
3 5
3 5
3 Perform KT for delta scope
3 6
3 6

1
Prepare End User Training Materials and

Documentation
Configured General Settings and Organizational
Structure (Cycle #1 - n)
3 7
3 7
1 Configure General Settings
3 7
2 Configure Organizational Structure
3 8
3 8
Configured Master Data Objects (Cycle #1 - n)
Core Configuration and Documentation - Process

(Cycle #1 - n)
3 9
3 9
3 10
For <MASTER DATA OBJECT NAME> - Prepare and

Load Master Data
Complete Core Configuration, including

documentation and test cases
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
3 11
RDS or Predefined Service Solution Enhancements

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

#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
3 13 1 Develop Business Process Procedure Document

3 13 2
Validate and Complete Business Process Procedure

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
3 14 4
Obtain Customer Sign-off for Testing of Scenario #1 n
3 15
3 15 1
Execute Technical Installation of SAP Products for

QAS environment
3 15 2

QAS Environment
Set up Role Assignment / Authorizations / Test Users

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 3
3 15 6 Perform Manual Configuration Settings in QAS

3 16
3 17
3 17 1 Prepare Preliminary Cutover plan
3 17 2 Refine Preliminary Cutover Plan
3 18
Approved Integration Test (Cycle #1 - n)
3 18 1
Prepare Integration Test Plan, including test of roles

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

3 20 2
For <SCOPE OPTION> - Prepare and Document User

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

Resolution
3 20 5 Obtain UA Test Results Sign-off

3 21
Execute Technical Installation of SAP Products for

PRD Environment
Execute Technical Upgrade of SAP Products for PRD
3 21 2
Environment
3 21 1
3 21 3

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

Authorizations / Test Users in PRD
For <SCOPE OPTION> - Populate PRD with Test

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 21 5
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
3 23 1
Perform SAP Going Live Check - Analysis Session

and schedule the Verification Session
3 24
3 24 1 Validate Support Center/Help Desk Staffing Strategy

3 24 2 Set-up Business Process Monitoring
3 25
3 25 1 Conduct Project Quality Gate(s)
3 25 2 Obtain Customer Sign-Off for Phase Completion

3 26
Final Preparation
4 1
Phase Initiation
4 1
4 2
4 2
4 2
4 2
4 2
4 3
4 3
1 Deliver End User training
4 4
4 4

stakeholders
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
4 5
Final Check of Production Readiness and Sign-Off for

transition to Production
Perform Cutover Weekend Activities including Final

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

Documentation
4 7
Go Live Support
5 1
Phase Initiation
5 1
5 2
5 2
5 3
5 3
1 For <SCOPE OPTION> - Prepare End-User Training
5 3
2 For <SCOPE OPTION> - Deliver End-User Training
5 4
5 4
5 5
5 5
Conduct SAP Going Live Check - Verification Session

Remote
1 Provide Post Go Live Support
5 6
5 7
Improvement Roadmap
Perform Refinement & Improvement Planning
Workshops
5 7
5 7
2 Document Improvement Roadmap
5 8
5 8
5 8
5 8
3 Resolve and close open issues
5 8
4 Finalize Project Closeout Report
5 8

Acceptance
Operate
6 1

6 1
6 1
2 Prepare Maturity Assessment Report
6 2
6 2
1 Perform assessment of Solution Documentation set up
6 3
6 3
6 4
6 4
1 Perform assessment of Template Management set up
6 5
6 5
1 Perform assessment of Test Management set up
6 6
6 6
Perform assessment of Solution Implementation set

up
Perform assessment of Change Control Management

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

up
6 11
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 customers 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
responsibilities of the project team.
Mandatory
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 signoff 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 deliverable is to kick-off the project/phase and ensure that all
needed information is shared with the resources for a successful project execution.
Mandatory
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 the project and clearly
Mandatory
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.
The purpose of this activity is to create the project/phase schedule and assign
resources to the scheduled activities and tasks.
Mandatory
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 defined Mandatory
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 nonMandatory
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
Optional
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
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
improved reliability of solution and minimized risk through segregation of duties and
transparency of changes.
Optional
Optional
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, costs etc.
Mandatory
status and progress of the project including potential disturbances due to existing
risks and issues.
Mandatory
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
well as to the overall project plan and ensures the checkability of OCM activities.
Optional
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.
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 design Mandatory
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
SAPs 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

Optional
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 addon, 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.

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
SAPs 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

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.
Mandatory
management process.
Mandatory
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 defined
Mandatory
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 analysis Optional
of current state asis and future state tobe 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
and documented by comparing the as-is and the to-be business processes.
Optional
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 corresponding Mandatory
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 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:
Provides guidance for blueprinting workshops and relevant enabling tools
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 crossprocess integrity.
Optional
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
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
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 against Mandatory
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
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.
Mandatory
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
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.
Implementation of the final solution in the development environment
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.
Mandatory
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 Standup Meeting. The Daily Standup 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.
Scrumof 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 readystate 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.
Mandatory
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 infrastructure Optional
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 the Mandatory
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
requirements specified in the business blueprint phase.
Mandatory
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
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
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.
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
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
structure
Mandatory
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.
Documentation to be stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the functional
specification,
Mandatory
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
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 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
Optional

The purpose of the quality assurance infrastructure and environment design and
setup deliverable is to install a viable, correctly configured technical QA environment Mandatory
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 be
Mandatory
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.
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
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 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 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
performance test measures the throughput and response times of the system.
Mandatory
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.
- Verification of the technical capabilities of the production environment (sizing
plausibility)
- 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

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.
Mandatory
Mandatory
risks and issues.
Mandatory
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
the Go Live simulations.
Mandatory
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.
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
Mandatory
content, and set up as a productive solution in SAP Solution Manager. This provides Optional
the basis for the follow up activities in the Run Phase.
Mandatory

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.
Mandatory
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.

documentation.
The purpose of this task is to verify that the requirements identified in earlier
sessions are met.
Optional
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

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.
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
Optional
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 enterprises 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
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 nonevent
for the business.
exist for the Upgrade Management area.
Q-Gate Key Deliverable
Work Stream
Accountable Role
_Phase
Project Guideline (incl.

Travel Guideline)
Project Manager
Project Manager
Project Manager
Steering Committee
Definition, Org-Structure,
Roles
Project Charter
Project Manager
Project Manager
Project Manager
Management
Scope Statement
Document
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager

milestones)
Project Manager
Project Manager
Project Manager
Project Manager
Project Budgetplan
Project Manager
Project Management
Plan(s)
Project Manager

Management

guideline,
Business Process
Modeling Standards

Management
Business Consultant
Software System
Configuration Standards,
Enhancement and

Management
Business Consultant
Test Management
Standards
Test Management Consultant
Change Request and

Standards (CTS)

Management
Project Manager
Project Manager

external), Project Change
Project Manager
Report (internal &
external)
Project Manager
OCM Roadmap

Management
Management
Business Consultant
Training - Training

Plan & Schedule
Training - Training
Training - Training
Training - Training


Management

Start and Scope
Solution Landscape
Design

Management

Management
DM - Data Migration
DM - Data Migration
DM - Data Migration

Management

Management
Management
Solution Architect

Management
Management
Management
Management
Proj Support Tools & Sys

Setup
Solution Architect

Management

Management

Management
Management
Management
Management
Management
Management

Management

Management

Management
Management

Management
Business Manager
_Milestone
_Phase
milestones)
Project Manager
Project Management
Plan(s)
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Report (internal & external
Project Manager

(Internal)

Management
Management Plan

Management
Business Consultant

Management

Management
Management
Business Consultant
Business Readiness
Approach

Management
Business Consultant
Training - Training
Training - Training

Training - Training
Training - Training
Training - Training
Business Consultant

Management

Management

Management

Management

Management
Management
Plan
Consultant
DM - Data Migration
DM - Data Migration
DM - Data Migration

Management
Authorization
Requirements and Design Management
Solution Landscape
Design

Management
Management
Management
Management

Results
Results
Delivery Acceptance
Protocol
DM - Data Migration
Business Manager
_Milestone
_Phase
milestones)
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager


Management
User Role Document

Management
Business Consultant
Training - Training
Training - Training
Training - Training
Training - Training

Training - Training
Training - Training
Configuration, Interfaces,
Developments)

Management
Management
Management
Developments)

Management
Management
Management
Management
Management
Management
Developments)

Management
Management
Developments)

Management
Management
Developments)

Management

Management
RICEFW, SOA, Migration) Management
Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management
Consultant

Management
Management
Management
Solution Landscape
Design

Management
Management

Management

Management
DM - Data Migration
DM - Data Migration

Management
_Milestone

Results

Plan
Project Manager
DM - Data Migration
DM - Data Migration
Testplans & Results - UAT ISM - Test Management
Solution Landscape
Design
Project Manager

Management
Management
Management

Management

Management
DM - Data Migration
DM - Data Migration

Management
Management

Management

Management
Technical Operations and TSM - Technical Solution

Handover Strategy
Management
Management
Management
Results
Delivery Acceptance
Protocol
Business Manager
Project Manager
_Milestone
_Phase
milestones)
Project Manager
Project Manager
Project Manager
Project Manager
Project Manager

Training - Training
Training - Training

Plan
DM - Data Migration
Project Manager

Results
Delivery Acceptance
Protocol
Business Manager
_Milestone
_Phase
milestones)
Project Manager
Project Manager
Go-Live Training Sessions Training - Training

Training - Training
Training - Training

Management
Support Process Enabled,

Governance Model for
Operations
_Milestone
Project Manager
Project Manager
Results
Delivery Acceptance
Protocol

Learned (internal)
Project Manager
Business Manager
Project Manager
Project Manager
Project Manager
_Phase
Business Consultant
Project Manager

Management
Management

Management

Management

Management

Management

Management
Management
Test Management Consultant

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

Management

W Bs Dictionary

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

W Bs Dictionary

Загружено:

Авторское право:

Доступные форматы

WBS #

WBS item title

2 Prepare Team Onboarding Document

1 Define Project Organization

2 Assign Roles and Responsibilities

3 Complete communication management plan

1 Prepare Project Charter Document

3 Obtain Project Charter Sign-off

1 Prepare for Kickoff Meeting

2 Perform Kickoff Meeting

Allocate Resources - hard booking with resource

1 Document Customer Requirements

2 Review Scope Statement with Customer

3 Create Work Breakdown Structure and WBS Dictionary

4 Refine Acceptance Criteria

5 Obtain customer sign off for project scope

1 Develop delivery schedule and assign resources

2 Include key workshops into the project schedule

3 Obtain Customer sign-off for project schedule

4 Establish Cost and Schedule baseline

Project Schedule and Budget

Project Management Plan

1 Prepare Project Management Plan

2 Obtain Project Management Plan Sign-Off

1 Conduct ALM Roadmap

2 Determine Solution Documentation Procedure

3 Determine Solution Implementation Procedure

4 Determine Template Management Procedure

5 Determine Test Management Procedure

6 Determine Change Control Management Procedure

7 Determine Application Incident Management Procedure

Project and Operational Standards

8 Determine Technical Operations

9 Determine Business Process Operations

10 Determine Maintenance Management

11 Determine Upgrade Management

1 Direct and manage project execution

2 Monitor and control project activities

3 Manage Issues, Risks and Changes

4 Communicate Status and progress to project stakeholders

Execution, Monitoring, and Controlling of Results

Organizational Change Management Roadmap

1 Prepare Organizational Change Management Roadmap

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

1 Prepare training strategy and plan document

Project Team Training

Business Process Map

1 Prepare Business Process Map

3 Prepare Scope Document for Workshop

For <SCOPE OPTION> - Demonstrate the business

Complete Customer Blueprint and Configuration

6 Validate and Complete business process map

Prepare Demo Environment for Scope Refinement

1 Prepare Value Map

2 Validate and Complete Value Map

Business Scenario Design

1 Capture Business Scenario Requirements

2 Validate and Complete Scenario Design

Store Scenario Level Solution Documentation in SAP

Prepare Testing Policy

1 Prepare Testing Policy document

2 Obtain Customer Sign-Off for Testing Policy document

Data Migration Approach and Strategy