You are on page 1of 310

WBS # WBS item title

1 Project Preparation

1 1 Project Initiation

1 1 1 Allocate Resources - hard booking with resource management

1 1 2 Prepare Team Onboarding Document

1 2 Project Governance

1 2 1 Define Project Organization

1 2 2 Assign Roles and Responsibilities

1 2 3 Complete communication management plan

1 3 Project Charter

1 3 1 Prepare Project Charter Document

1 3 2 Identify Stakeholders

1 3 3 Obtain Project Charter Sign-off

1 4 Kick-Off Workshop

1 4 1 Prepare for Kickoff Meeting


1 4 2 Perform Kickoff Meeting

1 5 Scope Statement

1 5 1 Document Customer Requirements

1 5 2 Review Scope Statement with Customer

1 5 3 Create Work Breakdown Structure and WBS Dictionary

1 5 4 Refine Acceptance Criteria

1 5 5 Obtain customer sign off for project scope

1 6 Project Schedule and Budget

1 6 1 Develop delivery schedule and assign resources

1 6 2 Include key workshops into the project schedule


1 6 3 Obtain Customer sign-off for project schedule

1 6 4 Establish Cost and Schedule baseline

1 7 Project Management Plan

1 7 1 Prepare Project Management Plan

1 7 2 Obtain Project Management Plan Sign-Off

1 8 Project and Operational Standards

1 8 1 Conduct ALM Roadmap

1 8 2 Determine Solution Documentation Procedure

1 8 3 Determine Solution Implementation Procedure

1 8 4 Determine Template Management Procedure

1 8 5 Determine Test Management Procedure

1 8 6 Determine Change Control Management Procedure


1 8 7 Determine Application Incident Management Procedure

1 8 8 Determine Technical Operations

1 8 9 Determine Business Process Operations

1 8 10 Determine Maintenance Management

1 8 11 Determine Upgrade Management

1 9 Execution, Monitoring, and Controlling of Results

1 9 1 Direct and manage project execution

1 9 2 Monitor and control project activities

1 9 3 Manage Issues, Risks and Changes


1 9 4 Communicate Status and progress to project stakeholders

1 10 Organizational Change Management Roadmap

1 10 1 Prepare Organizational Change Management Roadmap

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

1 11 1 Prepare training strategy and plan document

1 12 Project Team Training

1 12 1 Conduct Solution Training and knowledge transfer

1 13 Business Process Map

1 13 1 Prepare Business Process Map

1 13 2 Prepare Demo Environment for Scope Refinement Workshops

1 13 3 Prepare Scope Document for Workshop


For <SCOPE OPTION> - Demonstrate the business processes and
1 13 4
predefined options list

Complete Customer Blueprint and Configuration Requirements


1 13 5
Template

1 13 6 Validate and Complete business process map

1 14 Value Determination

1 14 1 Prepare Value Map


1 14 2 Validate and Complete Value Map

1 15 Business Scenario Design

1 15 1 Capture Business Scenario Requirements

1 15 2 Validate and Complete Scenario Design

1 15 3 Store Scenario Level Solution Documentation in SAP Solution Manager.

1 16 Prepare Testing Policy

1 16 1 Prepare Testing Policy document

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

1 17 Data Migration Approach and Strategy

1 17 1 Prepare Data Migration Workshop

1 17 2 Conduct Data Migration Workshop

1 17 3 Conduct Data Audit (Data Health Check)

1 17 4 Prepare Data Migration Scope and Requirements Document

1 17 5 Present DM scope and requirements document

1 17 6 Conduct Organizational Assessment for Data Migration

1 17 7 Conduct Infrastructure Assessment for Data Migration


Conduct Risk Assessment for Data Migration and Prepare Mitigation
1 17 8
Plan

1 17 9 Complete the Data Migration approach and strategy document

Technical Requirements and Design and Solution Landscape


1 18
Deployment Plan

1 18 1 Define Solution Landscape Concept

1 18 2 Define Solution Deployment Concept

1 19 Interface Inventory

1 19 1 Prepare Interface Inventory document

1 20 Initial Hardware Sizing Proposal

1 20 1 Complete HW sizing estimation for solution landscape

1 21 Project Support Tools and System Setup


1 21 1 Verify Technical System Requirements (frontend / backend)

1 21 2 Verify Functional System Requirements

1 21 3 Check availability of SAP Solution Manager

1 21 4 Install or Upgrade SAP Solution Manager

1 21 5 Set up Business Process Hierarchy in SAP Solution Manager

Setup of project logistics and infrastructure, including team collaboration


1 21 6
environment

1 21 7 Install SAP GUI on project team computers

Test Remote Access and Establish OSS Connection (both GUI and
1 21 8
Web Access)

1 21 9 Prepare SAP Best Practice Activation

Execute Technical Installation of SAP Products (Pre-defined solution


1 21 10
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

2 Business Blueprint

2 1 Phase Initiation

2 1 1 Allocate Resources and Update Project Schedule

2 1 2 Perform Kickoff Meeting

2 2 Execution, Monitoring and Controlling Results

2 2 1 Update Project Management Plan

2 2 2 Direct and manage project execution

2 2 3 Monitor and control project activities


2 2 4 Manage Issues, Risks and Changes

2 2 5 Communicate Status and progress to project stakeholders

2 3 Stakeholder Analysis

2 3 1 Conduct classification of project Stakeholders

2 3 2 Identify Key Users

2 4 Change Impact Analysis

2 4 1 Validate organizational alignment approach

2 4 2 Establish Baseline of Current State

2 5 Communication Plan

2 5 1 Define Value Argumentation / Key Messages

2 5 2 Define Communication strategy

2 6 End User Training Strategy and Plan

2 6 1 Conduct Learning Needs Analysis

2 6 2 Develop Detailed End-User Training Plan


2 7 Project Team Training

2 7 1 Conduct Blueprint Ramp-up Training

2 7 2 Conduct Key User training

2 8 End User Training Content

2 8 1 Adaptation of Pre-delivered Training Content

2 8 2 Prepare and Build Training Content in Project Environment

2 9 Scope Validation / Fit-Gap Analysis

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

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


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

2 9 4 Validate pre-defined RICEFW Objects (reports, forms etc.)

2 9 5 Determine Gap list and effort estimation

2 10 Business Solution Design for Business Objects

2 10 1 Define Business Organization Structure

2 10 2 Define General Settings and Master Data

2 10 3 Define User Role Concept

2 10 4 Define Logical Data Model


2 11 Detailed Design - Business Scenario #1 -n

2 11 1 Capture Business Scenario Requirements

2 11 2 Complete Business Scenario Design Document

2 12 Detailed Design - Business Process #1 - n

2 12 1 Capture Business Process Requirements

2 12 2 Complete Business Process Design Document

2 12 3 Demo or Visualize Standard Functionality

2 13 Value Realization

2 13 1 Prepare Value Dashboard

2 14 Detailed Design - Configuration and Enhancements

2 14 1 Finalize Core Configuration Design

2 14 2 Finalize Delta Configuration Design


2 14 3 Define functional Design - RICEFW Object #1 - n

2 14 4 Define Functional Design - SOA & 3rd party applications #1 - n

2 15 Visualization

2 15 1 Conduct Visualizations

2 15 2 Prepare Initial Business Process Procedure document

2 16 Legacy Data Migration

2 16 1 Ensure Master Data Management Processes Ownership

Conduct Data Mapping workshops (master data for pre-defined


2 16 2
solutions)

2 16 3 Conduct Data Quality Assessment

2 16 4 Define Automated Data Migration Approach

2 16 5 Define Manual Data Migration Approach

2 16 6 Prepare Data Quality Plan

2 16 7 Prepare Data Security Design and plans

2 17 Legacy Data Archive


2 17 1 Prepare baseline framework for the legacy data archiving solution

2 18 Technical Solution Design

2 18 1 Prepare technical infrastructure specification

2 19 User Access and Security

2 19 1 Authorization Requirements and Design

2 20 Development Environment (DEV)

2 20 1 Execute Technical Installation of SAP Products for DEV environment

2 20 2 Execute Technical Upgrade of SAP Products for DEV environment

2 20 3 Install Solution Documentation in Solution Manager

2 20 4 Execute Technical Installation of 3rd party products

2 20 5 Set up Role assignment / Authorizations / Test Users in DEV

2 20 6 Perform Manual Configuration in DEV

2 20 7 Validate Role assignment / Authorizations / Test Users in DEV

2 20 8 Create master data in DEV environment - Master Data #1 - n

2 21 Testing Strategy
2 21 1 Prepare Test Strategy document

2 21 2 Define Test data approach and validated pre-defined master data

2 21 3 Review and Validate Testing Strategy with customer

2 21 4 Obtain customer sign-off on Testing Strategy.

2 21 5 Initiate Performance Testing preparation activities

2 22 Phase Closure and Sign-Off phase Deliverables

2 22 1 Conduct Knowledge Management Gate

2 22 2 Conduct Project Quality Gate

2 22 3 Conduct Project Management Review Service

2 22 4 Conduct Design Review Service

2 22 5 Manage Fulfilled Contracts


2 22 6 Obtain Customer Sign-Off for Phase Completion
2 23 MILESTONE: Design to Build

3 Realization

3 1 Phase Initiation

3 1 1 Allocate Resources and Update Project Schedule

3 1 2 Perform Kickoff Meeting

3 2 Execution, Monitoring and Controlling Results

3 2 1 Update Project Management Plan

3 2 2 Direct and manage project execution

3 2 3 Monitor and control project activities

3 2 4 Manage Issues, Risks and Changes

3 2 5 Communicate Status and progress to project stakeholders


3 3 Organizational Alignment

3 3 1 Execute Role Mapping and Transition Planning

3 3 2 Conduct Sounding Board/Pulse Checks

3 3 3 Refine and Execute Communication Plan

3 4 Educational Readiness Review

3 4 1 Prepare Educational Readiness Report

3 5 Knowledge Transfer

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

Perform Solution Walkthrough and knowledge transfer to Key Users for


3 5 2
<SCOPE OPTION>

3 6 End User Training Delivery Enabled

3 6 1 Prepare End User Training Materials and Documentation

3 6 2 Set up Training Environment

3 6 3 Perform Training of the Trainers

3 6 4 Develop End User Training Schedule and Logistics plan

3 7 Configured General Settings and Organizational Structure

3 7 1 Configure General Settings

3 7 2 Configure Organizational Structure


3 8 Configured Master Data Objects #1 - n

Prepare and Load master data - Master Data Object <MASTER DATA
3 8 1
OBJECT NAME>
3 8 2 Configure Master Data Objects #1 - n

3 9 Core Configuration and Documentation - Process #1 - n

3 9 1 Complete Core Configuration, including documentation and test cases

3 9 2 Prepare Unit Test Cases

3 9 3 Prepare String Test Cases

3 9 4 Execute Business Process Unit Test

3 9 5 Perform defect resolution for Business Process Unit Test

3 9 6 Execute Business Process String Test

3 9 7 Perform defect resolution for Process String Test

3 10 Delta Configuration - Process #1 - n

3 10 1 Complete Delta Configuration

3 10 2 Complete Delta Process Documentation

3 10 3 Complete Delta Process Test Cases

3 10 4 Execute Business Process Unit and String Test Cases

3 10 5 Perform defect resolution for Unit and String Test


3 11 Enhancement Development - RICEFW Object #1 - n

3 11 1 Develop RICEFW Object #1 - n

3 11 2 Document RICEFW Object #1 - n

3 11 3 Execute Test Cases - RICEFW Object #1 - n

3 11 4 Perform defect resolution for RICEFW Object(s) Test

3 11 5 Conduct Final Code Review

3 12 SOA / Composite Application Development #1 - n

3 12 1 Develop, document and test Enterprise Service #1 - n

3 12 2 Develop, document and test Composite and/or Mobile Application #1 - n

3 12 3 Conduct Final Code Review for SOA / Composite Application

3 13 Business Process Procedure

3 13 1 Develop Business Process Procedure Document

3 13 2 Validate and Complete Business Process Procedure Document

3 14 Value Audits

3 14 1 Perform Value Audit

3 15 Scenario Test #1 - n

3 15 1 Prepare Test Case - Scenario #1 - n


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

3 15 4 Obtain Customer Sign-off for Testing of Scenario #1 - n

3 16 Quality Assurance Environment (QAS)

3 16 1 Execute Technical Installation of SAP Products for QAS environment

3 16 2 Execute Technical Upgrade of SAP Products for QAS environment

3 16 3 Import Configuration and Development Objects to QAS Environment

3 16 4 Set up Role Assignment / Authorizations / Test Users in QAS


Prepare and Load Master Data into QAS Environment for <SCOPE
3 16 5
OPTION>
3 16 6 Perform Manual Configuration Settings in QAS

3 17 MILESTONE: Build to Test

3 18 Preliminary Cutover plan

3 18 1 Conduct Organizational Change Management Readiness Check

3 18 2 Conduct Production Support Readiness Check

3 18 3 Conduct Master Data Process Governance Readiness Check

3 18 4 Prepare Preliminary Cutover plan

3 18 5 Review Preliminary Cutover Plan with customer

3 18 6 Refine Preliminary Cutover Plan


3 19 Approved Integration Test

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

3 19 2 Prepare and document Integration Test Case #1 - n

3 19 3 Execute Integration Test Case #1 - n

3 19 4 Perform defect resolution for Integration Test

3 19 5 Obtain Integration Test Results Sign-off

3 20 Legacy Data Migration

3 20 1 Develop Data Migration Program Units

3 20 2 Execute and validate Manual Data Migration

3 20 3 Obtain Data Quality Reports

3 20 4 Perform SAP Target Load Test

3 20 5 Obtain Data Migration Test Results

3 20 6 Conduct Final Data Quality Assessment

3 21 Approved User Acceptance Test

3 21 1 Prepare UA Test Plan for <SCOPE OPTION>


3 21 2 Tool adaption and delta UAT training

Prepare and Document User Acceptance Test Cases for <SCOPE


3 21 3
OPTION>

3 21 4 Execute UA Test Plan for <SCOPE OPTION>

3 21 5 Perform UA Defect Resolution for <SCOPE OPTION>

3 21 6 Obtain UA Test Results Sign-off

3 22 SAP Data Archiving

3 22 1 Capture Legal and Business Retention Requirements

3 22 2 Prepare Data Archive Plan

3 22 3 Prepare Data Archive Storage Plan

3 22 4 Conduct Data Archive Implementation Test

3 23 Production Environment (PRD)

3 23 1 Execute Technical Installation of SAP Products for PRD Environment

3 23 2 Execute Technical Upgrade of SAP Products for PRD Environment

3 23 3 Import Configuration and Development Objects to PRD Environment

Set up Role assignment / Authorizations / Test Users in PRD for


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

3 24 Failover Environment

3 24 1 Prepare Failover Environment Design and Plan

3 24 2 Set-up Failover Environment and Execute Identified Scenarios

3 24 3 Obtain Failover Environment Test Results

3 25 System and Performance Test

3 25 1 Prepare System Test Plan

3 25 2 Prepare Performance Test Plan

3 25 3 Prepare System Test Cases

3 25 4 Prepare Performance Test Cases

3 25 5 Execute Performance Tests

3 25 6 Perform Performance Test Defect Resolution

3 25 7 Obtain Test Results Sign-off

3 26 SAP Going Live Check

Perform SAP Going Live Check - Analysis Session and schedule the
3 26 1
Verification Session

3 27 System User Roles and Authorization Administration

3 27 1 Set up administrative procedures for Roles and Authorizations


3 28 Technical Operations and Handover Plan

3 28 1 Validate Support Center/Help Desk Staffing Strategy

3 28 2 Establish Support Processes

3 28 3 Set-up Business Process Monitoring

3 29 Technical Integration Check

3 29 1 Conduct TIC Service

3 30 Phase Closure and Sign-Off phase Deliverables

3 30 1 Conduct Knowledge Management Gate

3 30 2 Conduct Project Quality Gate(s)

3 30 3 Conduct Project Management Review Service


3 30 4 Conduct Design Review Service

3 30 5 Manage Fulfilled Contracts

3 30 6 Obtain Customer Sign-Off for Phase Completion


3 31 MILESTONE: Test to Deployment

4 Final Preparation

4 1 Phase Initiation

4 1 1 Allocate Resources and Update Project Schedule

4 1 2 Perform Kickoff Meeting

4 2 Execution, Monitoring and Controlling Results

4 2 1 Update Project Management Plan

4 2 2 Direct and manage project execution

4 2 3 Monitor and control project activities

4 2 4 Manage Issues, Risks and Changes

4 2 5 Communicate Status and progress to project stakeholders


4 3 Organizational and Production Support Readiness Check

4 3 1 Perform Business validation and Transition Planning

4 3 2 Validate that Master Data Support Processes is established

4 3 3 Establish Business Process Operations

4 3 4 Establish System Administration and Control

4 3 5 Establish Security / Role and Authorization Management

4 3 6 Execute Transition to Production Support

4 4 Pre Go-Live End-User Training Delivery

4 4 1 Validate and adapt end user training material developed

4 4 2 Deliver End User training

4 4 3 Collect Training Evaluations feedback

4 4 4 Perform People Readiness assessment

4 5 Approved Technical System Tests


4 5 1 Execute Technical System Tests

4 5 2 Perform System Test Defect Resolution

4 5 3 Obtain System Test Results Sign-off

4 6 Production Cutover

4 6 1 Execute Go Live Simulations 1 thru N

4 6 2 Conduct Data Quality Readiness Check

4 6 3 Finalize Cutover Plan

4 6 4 Perform Pre-Cutover Weekend Closing Activities

Final Check of Production Readiness and Sign-Off for transition to


4 6 5
Production

Perform Cutover Weekend Activities including Final Production Data


4 6 6
Load

4 6 7 Obtain Production Data Load Sign-off

4 6 8 Initiate Solution Manager Update - Solution Documentation

4 7 Phase Closure and Sign-Off phase Deliverables

4 7 1 Conduct Knowledge Management Gate


4 7 2 Conduct Project Quality Gate

4 7 3 Conduct Project Management Review Service

4 7 4 Manage Fulfilled Contracts

4 7 5 Obtain Customer Sign-Off for Phase Completion

4 8 MILESTONE: Production System Live

5 Go Live Support

5 1 Phase Initiation

5 1 1 Allocate Resources and Update Project Schedule

5 1 2 Perform Kickoff Meeting

5 2 Execution, Monitoring and Controlling Results

5 2 1 Update Project Management Plan


5 2 2 Direct and manage project execution

5 2 3 Monitor and control project activities

5 2 4 Manage Issues, Risks and Changes

5 2 5 Communicate Status and progress to project stakeholders

5 3 Knowledge Support Strategy

Define Mid-Term and Long-Term Knowledge Support Strategy for


5 3 1
Customer

5 4 Post Go live End-User Training

5 4 1 Prepare End-User Training for <SCOPE OPTION>

5 4 2 Deliver End-User Training for <SCOPE OPTION>

5 4 3 Collect Training Evaluations feedback

5 4 4 Perform People Readiness assessment

5 5 SAP Going Live Check - Verification Session

5 5 1 Conduct SAP Going Live Check - Verification Session Remote

5 6 Production Support After Go Live

5 6 1 Provide Post Go Live Support

5 6 2 Monitoring Open Issues to Resolution

5 6 3 Resolve Functional Issues


5 6 4 Resolve Technical Issues

5 6 5 Complete Transition to Customers Production Support organization

5 6 6 Finalize Solution Manager Update - Solution Documentation

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

5 7 MILESTONE: Deploy to Run

5 8 End User Acceptance Survey

5 8 1 Prepare and distribute Survey to EU

5 9 Project Closure and Sign-Off Project Deliverables

5 9 1 Conduct Knowledge Management Gate

5 9 2 Conduct Project Quality Gate

5 9 3 Conduct Project Management Review Service


5 9 4 Manage Fulfilled Contracts

5 9 5 Resolve and close open issues

5 9 6 Finalize Project Closeout Report

5 9 7 Obtain Sign-off for Project Closure and Results Acceptance

5 10 MILESTONE: Project Complete

6 Operate

6 1 Operations Maturity Assessment

Perform evaluation and assessment of operations capabilities, including


6 1 1
CoE operational set up

6 1 2 Prepare Maturity Assessment Report

6 2 Solution Documentation Optimized

6 2 1 Perform assessment of Solution Documentation set up

6 3 Solution Implementation Optimized

6 3 1 Perform assessment of Solution Implementation set up

6 4 Template Management Optimized

6 4 1 Perform assessment of Template Management set up

6 5 Test Management Optimized


6 5 1 Perform assessment of Test Management set up

6 6 Change Control Management Optimized

6 6 1 Perform assessment of Change Control Management set up

6 7 Application Incident Management Optimized

6 7 1 Perform assessment of Incident Management set up

6 8 Technical Operations Optimized

6 8 1 Perform assessment of Technical Operations set up

6 9 Business Process Operations Optimized

6 9 1 Perform assessment of Process Operations set up


6 10 Maintenance Management Optimized

6 10 1 Perform assessment of Maintenance Management set up

6 11 Upgrade Management Optimized

6 11 1 Perform assessment of Upgrade Management set up


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 define the organizational structure, roles and responsibilities of the
project team.

The purpose of this task is to identify and select global company and external resources for the
project in accordance with the required roles, skills and responsibilities specified in the preceding
task. The assignment of people to roles should also take into account their qualifications and
availability for the whole project time frame.

The purpose of this task is to complete the communications management plan. This document
outlines the processes required to ensure timely generation, distribution, storage, and retrieval of
project information.

The purpose of this deliverable is to clearly and explicitly define the objectives of the proposed
project, analyze all possible benefits and quantify benefits in financial terms. This information and
supporting documents align key stakeholders around the strategic intent of the project.

The purpose of this activity is to collect all input required for the project charter and document it
into a format suitable for both communication purpose as for formal sign-off purpose, if possible
utilizing the accelerator file(s) provided

The purpose of this activity is to ensure that the correct groupings of stakeholders have been
identified for the project.
The purpose of this activity is to achieve a formal sign-off of the project charter.

The purpose of this deliverable is to kick-off the project/phase and ensure that all needed
information is shared with the resources for a successful 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-/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 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 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
Purpose of this task is to obtain customer approval (sign-off)
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 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 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 non-event for the business.

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

The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.

The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.

The purpose of this activity is to capture and manage project issues and risks and changes
related to those e.g. changes of project scope, timeline, 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 task is to prepare the training strategy and plan.

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

Purpose of this task is to obtain customer approval (sign-off)

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

Purpose of this task is to obtain customer approval (sign-off)


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 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 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 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 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 as-is and future state to-be
business process maps to quantify the delta transition gap

The purpose of this task is to re-visit the stakeholder identification results, determine the detailed
level of change impacts for the identified stakeholder (groups) in order to create transparency
about the organizational and system changes.

The purpose of this task is to identify key users needed for the different areas (depending on the
scope of this project).

The purpose of the Change impact analysis deliverable is to ensure that the organizational and
technical changes in business processes have been identified 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:
Sets project team expectations and blueprint deliverables
Provides guidance for blueprinting workshops and relevant enabling tools
Introduces blueprint quality assurance and its acceptance criteria
Prepares for essential blueprinting skills, such as workshop facilitation, requirements
gathering, and process modeling
Fosters teamwork within project teams

The purpose of this task is to train the key users for the solution in scope (pre-defined content)

The purpose of the end user training content deliverable is to create a curriculum plan that covers
the skills that end users will need to possess to use the system. This document will be refined
throughout the project.

The purpose of this task is to validate and adapt the standard end user training material being
pre-delivered within the solution. (delivery model 3&4).

The purpose of this task is to prepare training content in the system environment being set up for
the project.

The purpose of solution validation / fit-gap analysis deliverable is to validate the predefined
scenarios, processes and enhancements; identify potential gaps between delivered product and
customer requirements. The deliverable only captures requirements for gaps. It follows an
iterative approach. Existing documentation and models can be altered, changes have to be
marked and documented in Solution Manager.

This task validates predefined general settings and that these are still relevant for the scope of
the implementation, such as organizational structures or customer or material masters, and to
identify potential gap between delivered product and customer requirements.esign a solution for
these business objects within the SAP solution. These objects are associated to processes and
reflected in applications so understanding these relationships is essential for overall integration
and cross-process integrity.

This task validates predefined scenario solution documentation, identifies potential gap between
delivered product and customer requirements. Only requirements for gap are being captured. It
follows an iterative approach. Existing documentation and models can be altered, changes have
to be marked and documented in Solution Manager
This task validates predefined process solution documentation, identifies potential gap between
delivered product and customer requirements. Only requirements for gap are being captured. It
follows an iterative approach. Existing documentation and models can be altered, changes have
to be marked and documented in Solution Manager.

This task validates the pre-defined RICEFW Objects (reports, forms etc.). Additional
customization and enhancements should be kept to a minimum.

This purpose of this task is to analyze identified gaps and additional requirements and determine
effort (and duration) for the realization phase.

The purpose of business objects modeling (cross-process view) is to identify business objects
that are relevant for the scope of the implementation, such as organizational structures or
customer or material masters, and to design a solution for these business objects within the SAP
solution. Business objects are associated to processes and reflected in applications.
Understanding these relationships is essential for overall integration and cross-process integrity.

Business object modeling may also build the foundation for service modeling, if the project is
implementing a service-oriented architecture (SOA).

The purpose of this task is to capture the design and requirements of the organizational structure.
This should reflect multiple views of a company i.e. Legal, Fiscal, Functional, Product-oriented,
Regional and geographical, Customer-group, Distribution-channels, Purchasing-channels etc.
depending 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.

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

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

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 obtain customer approval (sign-off)

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

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

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.

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.
Purpose of this task is to obtain customer approval (sign-off)
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

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 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 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 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 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 update communication plan and execute accordingly

The purpose of this deliverable is to determine the potential issues with the SAP education
strategy and solution before they impact the quality of the SAP software deployment.

The purpose of this task is to capture feedback on both the training strategy and approach,
determine issues and propose resolutions for identified issues.

The purpose of the Knowledge Transfer deliverable is to ensure that key users get a good
understanding of the implemented solution.

In this task the SAP project team prepares for training and enablement of the customer project
team to understand the solution and how it is implemented in their area, as well as trains the key
users as defined in the statement of work.

The purpose of this task is to execute knowledge transfer by means of solution walkthrough
sessions, system demos on scenario and/or process level, functional reviews etc., etc.

The purpose of the deliverable End User Training Content Enabled is to ensure availability of end
user training material, training environment, 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
document this in Solution Manager.
The purpose of this task is to prepare the test cases

The purpose of this task is to prepare the test cases

The purpose of this task is to perform unit test for the configuration

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

The objective of this task is to resolve any issues identified during the Unit and String Test. It is
crucial that the issues are re-tested by users that reported them (or designated re-testers) and
that they are confirmed.
The purpose of this deliverable is to 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 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 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 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.
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.

Purpose of this task is to obtain customer approval (sign-off)

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 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 stored in Solution Manager.

The purpose of this task is to document the integration test case outlined in the integration test
plan

The objective of this task is to perform the Integration test according to previously defined plan.
During the test all issues must be logged and documented in the system for traceability purpose.

The objective of this task is to resolve any issues identified during the Integration Test. It is crucial
that the issues are re-tested by users that reported them (or 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 oft his task is to adapt testing tools if needed (e.g. add of field values and additional
security roles) and train project team members, as usually the test team gets extended before
and during the UAT test cycle.

The purpose of this task is to document the integration test case outlined in the UAT test plan

The objective of this task is to perform the End User Acceptance test according to previously
defined plan. During the test all issues must be logged and documented in the system for
traceability purpose.

The objective of this task is to resolve any issues identified during the User Acceptance Test. It is
crucial that the issues are re-tested by users that 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.

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 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).
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 document the test case outlined in the test plan

The purpose of this task is to document the test case outlined in the test plan

The purpose of this task is to execute the performance tests and present the findings for these
tests. The outcome should be formally approved by the customer.

The objective of this task is to resolve issues identified during the performance or load testing.
Upon resolution the issues need to be re-tested and confirmed by responsible testers.
The purpose of this task is to obtain customer approval (sign-off)

The purpose of this service is to support the start of production of an SAP Solution. During this
service, SAP service engineers check the solution for 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

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.

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

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 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 Project Management Review is to provide a proactive quality assurance review,
with an impartial analysis of all aspects of the project across all project management
disciplines, enabling early detection of project issues with actionable recommendations.
The purpose of this task is to execute a Design Review of SAP Solution service that provides a
proactive quality assurance review of the design of the SAP solution which is being implemented.
It delivers an impartial analysis of all aspects of the solution design across all relevant design
perspectives and leads to an early detection of potential solution risks and offers actionable risk
mitigation recommendations.

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.
Purpose of this task is to obtain customer approval (sign-off)
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.

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 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 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 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 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.
Purpose of this task is to obtain customer approval (sign-off)

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.

This task will confirm that the productive system is ready for Go Live.

The purpose of this task is the loading of production data from legacy systems into the production
environment. Once all preparations and configurations on both the technical and application
levels are completed, the final productive solution can be set up and data loaded. The solution is
live in a production environment

Purpose of this task is to obtain customer approval (sign-off)

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 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 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 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 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 this task is to obtain customer approval (sign-off)
This milestone signifies formal transition to production environment. Production is up and
running, cutover sustainment activities, end-user on-boarding and support are under way.

The purpose of this phase is to provide support for the solution during the period
immediately following production cutover. Exceptional items such as additional
production support, exceptional business monitoring processes, and extraordinary
technical support are planned and executed in this phase. At the end of the designated
extra-care period, sustaining production support processes planned in final preparation
and executed as part of go-live support become the core support for continuous
improvement in the ongoing solution.

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 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 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 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 knowledge support strategy is to provide an approach for identifying and
addressing ongoing learning needs, required knowledge support, and processes for managing
training for all solution users.

The purpose of this task is to define knowledge support strategy is to provide a strategy for
identifying and addressing ongoing learning needs, required knowledge support, and processes
for managing training for all solution users. Since each user demographic has specific needs, the
project needs to put in place a set of ongoing learning plans and techniques.

The purpose of EU training during go-live support is to ensure that end users have adopted the
solution, knowledge resources are maintained, and 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 long-term SAP support
center team.

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

Purpose of this task is to obtain customer approval (sign-off)

This milestone signifies formal transition from post production sustainment support to long term
support and operation of the new environment

The purpose of the End User Acceptance Survey deliverable is to ensure the end-user
acceptance, which is a key indicator of success for any SAP implementation. The success of a
project depends on how usable and beneficial end users perceive the new processes and
systems to be after go-live. One of the key issues is to identify levels of acceptance and analyze
what cause them to vary.

The result of this task will determine the level of acceptance of the organization and provides
information needed for the analysis of what causes the acceptance levels to vary.

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

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

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 Template
Management area.
Functional and performance testing of SAP-centric business processes to ensure validated
system behavior after software change events
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 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

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

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

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

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

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 Maintenance
Management area.

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

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 Upgrade
Management area.
Q-Gate Relevant Q-Gate Key Deliverable Work Stream

_Phase

PM - Project Management

PM - Project Management
Project Guideline (incl. Travel
Mandatory PM - Project Management
Guideline)
PM - Project Management

Steering Committee Definition,


Mandatory PM - Project Management
Org-Structure, Roles

PM - Project Management

PM - Project Management

Mandatory Project Charter PM - Project Management

PM - Project Management

OCM - Organizational Change


Management
PM - Project Management

Mandatory Phase Kick Off Meeting PM - Project Management

PM - Project Management
PM - Project Management

Mandatory Scope Statement Document PM - Project Management

PM - Project Management

PM - Project Management

Work Breakdown Structure


Mandatory PM - Project Management
(WBS)

PM - Project Management

PM - Project Management

PM - Project Management

Project Schedule (incl.


Mandatory PM - Project Management
milestones)
PM - Project Management
PM - Project Management
Project Budgetplan (internal &
Mandatory PM - Project Management
external)

Mandatory Project Management Plan(s) PM - Project Management

PM - Project Management

PM - Project Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

Solution Manager Usage


guideline, ALM - Application Lifecycle
Mandatory
Business Process Modeling Management
Standards

Software System Configuration


ALM - Application Lifecycle
Optional Standards, Enhancement and
Management
Modification Standards

ALM - Application Lifecycle


Management

Optional Test Management Standards ISM - Test Management

Change Request and Transport TSM - Technical Solution


Optional
Management Standards (CTS) Management
TSM - Technical Solution
Management

Post Implementation Service TSM - Technical Solution


Optional
and Support Management

ALM - Application Lifecycle


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log
Project (Performance) Report
Mandatory PM - Project Management
(internal & external)

OCM - Organizational Change


Optional OCM Roadmap
Management

OCM - Organizational Change


Management

Training - Training

Project Team Training Plan &


Optional Training - Training
Schedule

Training - Training

Training - Training

Business Process Map BPM - Business Process


Mandatory
Business Process List Management

BPM - Business Process


Management
BPM - Business Process
Management
BPM - Business Process
Management
BPM - Business Process
Management

BPM - Business Process


Management

BPM - Business Process


Management

Optional Value Map VM - Value Management

VM - Value Management
Optional Value Audit of Scope VM - Value Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

Data Migration Approach, Start


Optional DM - Data Migration
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

TSM - Technical Solution


Optional Solution Landscape Design
Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Optional Proj Support Tools & Sys Setup
Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management

PM - Project Management

Project (phase) Lessons


Optional PM - Project Management
Learned (internal)
PM - Project Management

PM - Project Management

PM - Project Management
_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management

Mandatory Project Management Plan(s) PM - Project Management

PM - Project Management

PM - Project Management
Risk List (internal & external),
Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external

OCM - Organizational Change


Optional Stakeholder Analysis (Internal)
Management

OCM - Organizational Change


Management

OCM - Organizational Change


Management

Organizational Change OCM - Organizational Change


Optional
Management Plan Management

OCM - Organizational Change


Management

OCM - Organizational Change


Optional Business Readiness Approach
Management

OCM - Organizational Change


Management

OCM - Organizational Change


Management

OCM - Organizational Change


Management

Mandatory Training Project Plan Training - Training

Training - Training

End User Training and


Optional Training - Training
Documentation Developed
Training - Training

Training - Training

Training - Training

Training - Training

Training - Training

Training - Training

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management
BPM - Business Process
Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

Business Blueprint BPM - Business Process


Mandatory
Documents(Org Structure) Management

BPM - Business Process


Management

BPM - Business Process


Mandatory User Role Document
Management

BPM - Business Process


Management
BPM - Business Process
Mandatory Solution Documentation
Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Mandatory Solution Documentation
Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

Optional Value Audit of Scope VM - Value Management

VM - Value Management

Development list(incl. RICEFW, BPM - Business Process


Mandatory
SOA, Migration) Management

BPM - Business Process


Management

BPM - Business Process


Management
BPM - Business Process
Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

Mandatory Data Migration Design / Plan DM - Data Migration

DM - Data Migration

DM - Data Migration

Mandatory Test Cases & Results DM - Data Migration

DM - Data Migration

DM - Data Migration

DM - Data Migration

DM - Data Migration

DA - Data Archiving
DA - Data Archiving

TSM - Technical Solution


Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management

Authorization Requirements TSM - Technical Solution


Mandatory
and Design Management

TSM - Technical Solution


Mandatory Solution Landscape Design
Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management
TSM - Technical Solution
Management

Mandatory Test Strategy Plans & Results ISM - Test Management


ISM - Test Management

DM - Data Migration

ISM - Test Management

ISM - Test Management

ISM - Test Management

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

Project (phase) Lessons


Optional PM - Project Management
Learned (internal)

PM - Project Management

PM - Project Management

PM - Project Management

PM - Project Management
PM - Project Management
_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management

Mandatory Project Management Plan(s) PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external
OCM - Organizational Change
Management

OCM - Organizational Change


Optional User Role Document
Management

OCM - Organizational Change


Management

OCM - Organizational Change


Management

Training - Training

Training - Training

Training - Training

Training - Training

Training - Training

End User Training and


Optional Training - Training
Documentation Developed

Training - Training

Training Environment
Optional Training - Training
Population and Testing

Training - Training

End User Training Schedule


Optional Training - Training
and Logistics

Solution Documentation (incl.


BPM - Business Process
Mandatory Process list, Configuration,
Management
Interfaces, Developments)

BPM - Business Process


Management
BPM - Business Process
Management
Solution Documentation (incl.
BPM - Business Process
Mandatory Process list, Configuration,
Management
Interfaces, Developments)

BPM - Business Process


Management
BPM - Business Process
Management

Solution Documentation (incl.


BPM - Business Process
Mandatory Process list, Configuration,
Management
Interfaces, Developments)

BPM - Business Process


Management
BPM - Business Process
Management
BPM - Business Process
Management
BPM - Business Process
Optional Test cases & Results
Management

BPM - Business Process


Management

BPM - Business Process


Optional Test cases & Results
Management

BPM - Business Process


Management

Solution Documentation (incl.


BPM - Business Process
Mandatory Process list, Configuration,
Management
Interfaces, Developments)

BPM - Business Process


Management
BPM - Business Process
Management

BPM - Business Process


Management

BPM - Business Process


Optional Test cases & Results
Management

BPM - Business Process


Management
Development list(incl. RICEFW, BPM - Business Process
Mandatory
SOA, Migration) Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Optional Test cases & Results
Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management

BPM - Business Process


Management
BPM - Business Process
Management

Optional Value Audit of Scope VM - Value Management

VM - Value Management

ISM - Test Management

ISM - Test Management


Optional Test cases & Results ISM - Test Management
ISM - Test Management

ISM - Test Management

TSM - Technical Solution


Mandatory Solution Landscape Design
Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
DM - Data Migration
TSM - Technical Solution
Management

_Milestone

Mandatory Production Cutover Plan CutOver - Cut Over Management

OCM - Organizational Change


Optional Business Readiness Approach
Management
OCM - Organizational Change
Management
DM - Data Migration

CutOver - Cut Over Management

CutOver - Cut Over Management

CutOver - Cut Over Management


Mandatory Test Strategy Plans & Results ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

Mandatory Data Migration Design / Plan DM - Data Migration

DM - Data Migration

DM - Data Migration

DM - Data Migration

DM - Data Migration

Mandatory Test cases & Results DM - Data Migration

Mandatory Test cases & Results DM - Data Migration

Mandatory Testplans & Results - UAT ISM - Test Management

ISM - Test Management


ISM - Test Management

ISM - Test Management

ISM - Test Management

Testplans & Results -


Mandatory ISM - Test Management
Regression

ISM - Test Management

DA - Data Archiving

DA - Data Archiving

DA - Data Archiving

DA - Data Archiving

DA - Data Archiving

TSM - Technical Solution


Mandatory Solution Landscape Design
Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

TSM - Technical Solution


Management
DM - Data Migration

DM - Data Migration
TSM - Technical Solution
Management

Failover Environment Design, TSM - Technical Solution


Optional
Setup and Test Results Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management

TSM - Technical Solution


Management

Mandatory Test Plans & Results ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

TSM - Technical Solution


Optional SAP Going Live Check
Management

TSM - Technical Solution


Management

System User Roles and


Authorization Administration
TSM - Technical Solution
Optional and
Management
System Authentication
Management

TSM - Technical Solution


Management
Technical Operations and TSM - Technical Solution
Optional
Handover Strategy Management

TSM - Technical Solution


Management
TSM - Technical Solution
Management
BPM - Business Process
Management

Optional Technical Integration Check CutOver - Cut Over Management

CutOver - Cut Over Management

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

Project (phase) Lessons


Optional PM - Project Management
Learned (internal)

PM - Project Management

PM - Project Management
PM - Project Management

PM - Project Management

PM - Project Management
_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management

Mandatory Project Management Plan(s) PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external
OCM - Organizational Change
Management

Functional/Technical
OCM - Organizational Change
Optional Requirements and Production
Management
Support Processes Defined

Master Data Support


Optional DM - Data Migration
Processes Established

ALM - Application Lifecycle


Optional Business Process Operation
Management

System Administration and ALM - Application Lifecycle


Optional
Control Management

Security / Role and TSM - Technical Solution


Optional
Authorization Management Management

ALM - Application Lifecycle


Optional Transition to Support
Management

Training - Training

Training - Training

Training - Training

Optional Training Evaluations Training - Training

End User Training Delivery and OCM - Organizational Change


Optional
Readiness Checklist Management

ISM - Test Management


ISM - Test Management

ISM - Test Management

ISM - Test Management

CutOver - Cut Over Management

Mandatory Testplans & Results CutOver - Cut Over Management

Mandatory Data Migration Design / Plan DM - Data Migration

Mandatory Production Cutover Plan CutOver - Cut Over Management

CutOver - Cut Over Management

Optional Readiness for Cutover - Signoff CutOver - Cut Over Management

CutOver - Cut Over Management

Mandatory Production Cutover Plan CutOver - Cut Over Management

Solution Manager Update,


Optional CutOver - Cut Over Management
Solution Documentation

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

Project (phase) Lessons


Optional PM - Project Management
Learned (internal)
PM - Project Management

PM - Project Management

PM - Project Management

PM - Project Management

_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management

Mandatory Project Management Plan(s) PM - Project Management


PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external

Training - Training

Training - Training

Optional Go-Live Training Sessions Training - Training

Training - Training

Training - Training

Training - Training
OCM - Organizational Change
Management

TSM - Technical Solution


Management

CutOver - Cut Over Management

Support Process Enabled,


Optional Governance Model for CutOver - Cut Over Management
Operations

CutOver - Cut Over Management

CutOver - Cut Over Management

CutOver - Cut Over Management


CutOver - Cut Over Management

Transition to Standard Support


ALM - Application Lifecycle
Optional Processes, System
Management
Administration and Control

Solution Manager Update, ALM - Application Lifecycle


Optional
Solution Documentation Management

PM - Project Management

_Milestone

OCM - Organizational Change


Management

OCM - Organizational Change


Management

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

Project (phase) Lessons


Optional PM - Project Management
Learned (internal)

PM - Project Management

PM - Project Management
PM - Project Management

PM - Project Management

PM - Project Management

PM - Project Management

_Milestone

_Phase

PM - Project Management

PM - Project Management

PM - Project Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management
ALM - Application Lifecycle
Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management
ALM - Application Lifecycle
Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management

ALM - Application Lifecycle


Management
Accountable Role

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Technology Architect

Business Consultant

Business Consultant

Application Consultant

Test Management Consultant

Application Consultant
Application Consultant

Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Project Manager

Project Manager

Project Manager
Project Manager

Business Consultant

Education Consultant

Education Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Business Consultant
Business Consultant

Business Consultant

Application Consultant

Application Consultant

Technology Consultant

Project Manager

Application Consultant

Technology Architect

Application Consultant

Application Consultant

Technology Architect

Application Consultant

Application Consultant
Application Consultant

Application Consultant

Solution Architect

Technology Architect

Technology Architect

Solution Architect
Technology Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Project Manager
Business Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Business Consultant

Education Consultant

Business Consultant

Business Consultant

Business Consultant

Business Consultant

Education Consultant

Education Consultant
Business Consultant

Instructor

Education Consultant

Education Consultant

Application Consultant

Application Consultant
Application Consultant

Integration Development
Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant
Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Business Consultant

Application Consultant

Application Consultant
Integration Development
Consultant

Integration Development
Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant
Technology Architect

Technology Architect

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant

Application Consultant
Technology Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Project Manager

Business Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Business Consultant

Business Consultant

Business Consultant

Education Consultant

Application Consultant

Application Consultant

Education Consultant

Education Consultant

Education Consultant

Education Coordinator

Application Consultant

Application Consultant
Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant
Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Integration Development
Consultant

Application Consultant

Application Consultant

Business Consultant

Application Consultant
Application Consultant
Application Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant

Project Manager

Project Manager

Application Consultant

Application Consultant

Project Manager

Project Manager
Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Technology Architect

Technology Consultant
Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Project Manager

Technology Architect

Application Consultant

Application Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant
Application Consultant

Technology Architect

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant

Test Management Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant
Technology Consultant

Technology Consultant

Technology Consultant

Technology Architect

Project Manager

Business Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Business Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Education Coordinator

Education Consultant

Education Coordinator

Education Consultant
Technology Consultant

Application Consultant

Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Project Manager

Technology Consultant

Project Manager
Business Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Education Consultant

Education Consultant

Education Consultant

Education Coordinator

Education Consultant

Technology Consultant

Technology Consultant

Project Manager

Application Consultant
Technology Consultant

Technology Consultant

Technology Consultant

Project Manager

Business Consultant

Project Manager

Business Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Business Consultant

Project Manager

Application Consultant

Technology Consultant

Technology Consultant
Test Management Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant
Technology Consultant

Technology Consultant
Q-Gate
WBS
WBS item title Description Releva
#
nt

This phase provides initial planning and preparation for


the project. Although each project has its own unique
1 Project Preparation 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
1 1 Project Initiation
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.
Allocate Resources - hard
The purpose of phase resources allocation is a confirmation
1 1 1 booking with resource
of resource availability for the particular phase.
management

The purpose of this activity is to prepare the onboarding


Prepare Team Onboarding Mandat
1 1 2 package for external consultants from SAP and partner
Document ory
companies.

The purpose of this deliverable is to ensure that an efficient


1 2 Project Governance 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
Define Agile Project
1 2 1 of SCRUM master, Product Owner and team members.
Organization and Roles
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


Complete communication management plan. This document outlines the processes
1 2 2
management plan 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
Mandat
1 3 Project Charter possible benefits and quantify benefits in financial terms.
ory
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
Prepare Project Charter the project charter and document it into a format suitable for
1 3 1
Document 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


1 3 2 Identify Stakeholders 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
Set Stakeholder Expectations
1 3 3 functionality where possible. It is recommended to conduct
for Agile Project
informal and formal meetings to set the expectations and
confirm the project approach with key project stakeholders.
Obtain Project Charter Sign- The purpose of this activity is to achieve a formal sign-off of
1 3 4
off the project charter.
The purpose of this deliverable is to kick-off the
Mandat
1 4 Kick-Off Workshop project/phase and ensure that all needed information is
ory
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
1 4 1 Prepare for Kickoff Meeting
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
1 4 2 Perform Kickoff Meeting
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 Mandat
1 5 Scope Statement
project and clearly and explicitly defines the deliverables of ory
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
Document Customer process-related as well as project-/non-process-related
1 5 1
Requirements 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
Review Scope Statement with document with the customer project manager and key
1 5 2
Customer stakeholders in order to confirm the scope and obtain
approval.
The purpose of this task is to determine all gaps for
Determine Gap List and Effort
1 5 3 customer solution, document them formally and estimate
Estimation
effort to cover the identified gaps.

Communicate result of fit gap The objective of this task is to present the results of fit gap
1 5 4 analysis including effort analysis to customer including the effort estimates to cover
estimates 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
Create Work Breakdown Mandat
1 5 5 executed by the project team to complete the project. It is
Structure and WBS Dictionary ory
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
1 5 6 Refine Acceptance Criteria 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.
Obtain customer sign off for
1 5 7 Purpose of this task is to obtain customer approval (sign-off)
project scope
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.
1 6 Project Schedule and Budget
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 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,
Define Initial Release and available technical environment, complexity of the solution,
1 6 1 Sprint schedule, Assign geographical and organizational scope of the project and
Resources 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


Include key workshops into
1 6 2 workshops during the project/phase into a schedule that
the project schedule
facilitates workshop planning
Obtain Customer sign-off for
1 6 3 Purpose of this task is to obtain customer approval (sign-off)
project schedule

The purpose of this activity is to create project schedule and


Establish Cost and Schedule Mandat
1 6 4 cost baseline against which tracking, change management
baseline ory
and status reporting is done.
The purpose of the project management plan deliverable is
to develop the project management plan and the subsidiary Mandat
1 7 Project Management Plan
plans on the basis of the project scope defined in the project ory
charter.
The purpose of this activity is to collect input needed for the
project management plan and document it in a format
Prepare Project Management
1 7 1 suitable for both communication purpose as for formal sign-
Plan
off purpose, if possible utilizing the accelerator file(s)
provided
Obtain Project Management The purpose of this activity is to achieve a formal sign-off of
1 7 2
Plan Sign-Off 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,
Project and Operational approve, and communicate standards related to project
1 8
Standards 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
* Ready for Build (e.g. backlog item has proper size, it is clearly defined and unders
Define and Set Up Agile
* Ready for Demo (e.g. backlog item is fully developed and unit tested)
1 8 1 Project Standards and ALM
* Ready for Integration Test (e.g. backlog item integration test is defined (automated
Tools
* Ready for Release (e.g. backlog item user level documentation is complete, ALM
Note that definition of Ready for one step in the implementation process == definitio

The purpose of this task is to determine the customers


framework to centrally document and relate business
Determine Solution Mandat
1 8 2 processes and technical information of SAP and non-SAP
Documentation Procedure ory
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
Determine Solution
1 8 3 application lifecycle and designed to decouple technical Optional
Implementation Procedure
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
Determine Template multi-site SAP installations to efficiently manage their
1 8 4
Management Procedure 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
Determine Test Management
1 8 5 of SAP-centric business processes to ensure validated Optional
Procedure
system behavior after software change events.

The purpose of this task is to determine the customers


approach of handling business and technology-driven
Determine Change Control
1 8 6 changes, using a standardized process leading to improved Optional
Management Procedure
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,
Determine Application Incident
1 8 7 customer-side SAP experts, SAP Service & Support and
Management Procedure
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
Determine Technical reduce TCO by predefined content and centralized tools for
1 8 8 Optional
Operations 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
Determine Business Process important application related operations topics necessary to
1 8 9
Operations 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
Determine Maintenance
1 8 10 handled and how they are applied (upon request e.g. current
Management
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
Determine Upgrade upgrade project holistically and effectively end-to-end and
1 8 11
Management allows SAP customers to better understand and manage the
major technical risks and challenges in an upgrade project,
and to make the upgrade project a non-event for the
business.

The purpose of this deliverable is to execute the project


management plan and control and monitor the work defined
in the project scope statement.
Management plans developed during the project preparation
Execution, Monitoring, and
1 9 phase (see deliverable Project Management Plan) guide
Controlling of Results
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


Direct and manage project
1 9 1 executed according to what was agreed to in project charter,
execution
scope statement and project management plan.
The purpose of this activity is to assure that resources are
Monitor and control project assigned to all scheduled project activities (and tasks) and
1 9 2
activities that work is progressing and deliverables are produced as
expected.
The purpose of this activity is to capture and manage project
Manage Issues, Risks and Mandat
1 9 3 issues and risks and changes related to those e.g. changes
Changes ory
of project scope, timeline, costs etc.

The purpose of this activity to make sure that project


Communicate Status and
stakeholders are aware of status and progress of the project Mandat
1 9 4 progress to project
including potential disturbances due to existing risks and ory
stakeholders
issues.
The purpose of this deliverable is to present an overview of
all planned change management activities. It guarantees
Organizational Change
1### that all activities are related to each other as well as to the Optional
Management Roadmap
overall project plan and ensures the checkability of OCM
activities.
The purpose of this activity is to collect all required input for
Prepare Organizational
the OCM roadmap and document it in a format suitable for
1###1 Change Management
communication and inclusion into the project management
Roadmap
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
Project Training Strategy and
1### skills and knowledge needed to complete the project
Plan (team + key-users)
successfully. This learning path leads to project readiness as
well as certification on the specific applications the team
members will be using.

Prepare training strategy and The purpose of this task is to prepare the training strategy
1###1 Optional
plan document and plan.

The purpose of this deliverable is to provide an overview of


the SAP software to be implemented so that all project team
1### Project Team Training
members have an understanding of the SAP solution for
their areas of responsibility.
Conduct Agile Training for the The purpose of this task is to educate project team on Agile
1###1
Project Team 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 Mandat
1### Business Process Map
foundation for the process hierarchy a decomposition of ory
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


Prepare Business Process
1###1 Process Map with the content reflecting the process scope
Map
of the project

Prepare Demo Environment


The purpose of this task is to ensure that a proper
1###2 for Scope Refinement
environment is available for the options selection workshops
Workshops

The purpose of this task is to prepare the scope document


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

The goal of this task is to complete customer blueprint


Complete Customer Blueprint document based on interviews and assessment sessions.
1###5 and Configuration The document details the options customer selected from
Requirements Template the pre-defined solution, all modifications and details the
configuration requirements of the solution.

Validate and Complete Business Process Map with pre-


Validate and Complete
1###6 defined content depending on delivery model (Industrialized
business process map
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
1### Value Determination Optional
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
1###1 Prepare Value Map 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?
1###2 Define and Prioritize Epics High-Level 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
Validate and Complete Value process changes, key performance indicators, and value
1###3 Optional
Map 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
1### Business Scenario Design 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
Capture Business Scenario
1###1 and relate them to business scenarios, business objectives
Requirements
and benefits

The purpose of this task is to complete the Business


Validate and Complete Scenario Design document with relevant pre-defined
1###2
Scenario Design business process content (Assemble to order and/or
Industrialized content)

Store Scenario Level Solution The purpose of this task is to store Business Scenario
1###3 Documentation in SAP content in Solution Manager, according to Business Process
Solution Manager. 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
1### Prepare Testing Policy 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
Prepare Testing Policy
1###1 needed for the Test Policy, and to document it in a format
document
suitable for communication.

Obtain Customer Sign-Off for


1###2 Purpose of this task is to obtain customer approval (sign-off)
Testing Policy document

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
Data Migration Approach and intended to educate the SAP and customer project team
1### Optional
Strategy 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
Prepare Data Migration The purpose of this task is to make the necessary
1###1
Workshop 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
Conduct Data Migration
1###2 data migration approach and to understand the customers
Workshop
legacy data systems, business priorities, and technical
infrastructure.
The purpose of the data audit is to identify the legacy
Conduct Data Audit (Data
1###3 systems that will supply data for the SAP applications and to
Health Check)
profile the quality of the legacy data.

The purpose of this task is to prepare the data migration


Prepare Data Migration Scope
1###4 scope and requirements document that captures the overall
and Requirements Document
scope and requirements of the data migration effort.

The purpose of this task is to present data migration scope


Present DM scope and
1###5 and requirements document to customer project team and
requirements document
obtain buy in.
The purpose of this task is to assess customer organization
Conduct Organizational
for the demands of data migration process. The outcome of
1###6 Assessment for Data
this task is documented current state of the organization and
Migration
required target state.
The purpose of this task is to assess customer infrastructure
Conduct Infrastructure for the needs of the data migration process. As a result the
1###7 Assessment for Data project team learns about available tools and identifies any
Migration gaps/requirements to acquire tools to support the migration
process.
The purpose of this task is to assess risk for the data
migration activities. The risk assessment focuses on
Conduct Risk Assessment for
organization, technical risk, data quality risk and other risks
1###8 Data Migration and Prepare
that may impact the data migration activities. During this task
Mitigation Plan
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
Complete the Data Migration
Data Migration Approach and Strategy document, in a
1###9 approach and strategy
format suitable for both communication purpose as well as
document
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
Technical Requirements and
rest of the project team during the Business Blueprint phase.
1### Design and Solution Optional
Landscape Deployment Plan
Included in this deliverable is the solution landscape
deployment plan, which is a high level description of the
overall system landscape approach to be used for the
implementation project.

Define Solution Landscape The purpose of this task is to outline the software
1###1
Concept components and the design of the future solution landscape.

Define Solution Deployment The purpose of this task is to describe the concept of how
1###2
Concept the solution in scope will be deployed.

The purpose of the interface inventory deliverable is to


preliminarily identify the external systems, applications, and
1### Interface Inventory
business objects or transactions that must be integrated with
the SAP solution to realize the objectives of the project

Prepare Interface Inventory The purpose of this task is to collect necessary information
1###1
document for the interface inventory document.

The purpose of the initial hardware sizing proposal is to


Initial Hardware Sizing
1### begin the process of assessing the hardware infrastructure
Proposal
requirements.

Complete HW sizing The purpose of this task is to completed sizing estimates for
1###1 estimation for solution the Solution Manager system and Production and non-
landscape 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,
Project Support Tools and
1### adaptation, and implementation of new and enhanced Optional
System Setup
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
Verify Technical System
requirements for delivery of the service or project. The
1###1 Requirements (frontend /
objective is to ensure that all required technical requirements
backend)
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
Verify Functional System
1###2 objective is to ensure that all required functional
Requirements
requirements have been satisfied and work can be
performed by the team.

Check availability of SAP The purpose of this task is to validate that customer has
1###3
Solution Manager SAP Solution Manager installed and setup.

Install or Upgrade SAP The purpose of this task is to validate and ensure a proper
1###4
Solution Manager Solution Manager setup.

The purpose of this task is to ensure that the business


process structure in SolMan is supporting the solution
Set up Business Process
documentation and all continued project activities in the
1###5 Hierarchy in SAP Solution
coming phases (business process management, value
Manager
management, configuration & development, test, training
and cut over).

The objective of this task is to setup project logistics,


Setup of project logistics and
systems and infrastructure that will support delivery of the
1###6 infrastructure, including team
project. This may include setup of computers, setup of
collaboration environment
project team room, telephony, etc.

Install SAP GUI on project The purpose of this task is to install SAP GUI on project
1###7
team computers team computers.

The objective of this task is to validate that the remote


Test Remote Access and
connection to SAP is working and connection can be
1###8 Establish OSS Connection
established. This is both for the SAPGUI as well as Web
(both GUI and Web Access)
Access.

Prepare authorization roles in


The purpose of this task is to prepare authorization roles in
1###9 the systems for the project
the systems for the project team
team (DEV)

The purpose of this task is the initial set up of all relevant


1######Set up of testing tools 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
Phase Closure and Sign-Off
1 22 outstanding issues
phase Deliverables
Identify lessons learned during the phase to prepare
for formal project closure
Capture customer feedback and potential Customer
References
The purpose of this task is to collect knowledge assets and
lessons learned at the end of each phase of the project that
can be reused later by other projects. Collecting documents,
Conduct Knowledge
1 22 1 experiences, project highlights and lessons learned Optional
Management Gate
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
1 22 2 Conduct Project Quality Gate 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
Conduct Project Management assurance review, with an impartial analysis of all aspects of
1 22 3
Review Service the project across all project management disciplines,
enabling early detection of project issues with actionable
recommendations.
Obtain Customer Sign-Off for
1 22 4 Purpose of this task is to obtain customer approval (sign-off)
Phase Completion

MILESTONE: Project Start to This milestone signifies transition for Project Startup
1 23
Design 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
2 Lean Blueprint
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
2 1 Phase Initiation
recognize that a new project phase starts.

Allocate Resources and The purpose of this task is to confirm resource availability for Mandat
2 1 1
Update Project Schedule the particular phase. ory

The purpose of this task is to ensure the involvement of the


team and other key resources and their commitment to the
2 1 2 Perform Kickoff Meeting
project schedule. The meeting is also used to examine the
approach for the specific project phase.

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
Execution, Monitoring and
2 2 phase (see deliverable Project Management Plan) guide
Controlling Results
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 task is to update the project
Update Project Management The purpose of
management thisand
plan taskthe
is to plan, setup
subsidiary andbased
plans conducton the Mandat
2 2 1
Plan various
changesSCRUM
agreed meetings
during theinprojects
order tochange
keep the project teams
management ory
aligned
process.around common vision, share information amongst
The purposeteams
the SCRUM of thisand
activity
alignis individuals
to assure that theeach
within project is
team.
Direct and manage project
2 2 2 executed
The according
purpose of these tostandard
what wasmeetings
agreed toisintoproject
inform charter,
others
execution
scope work
about statement and project
that individual teammanagement
members do plan.
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
2 2 3 Conduct SCRUM Meetings
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.
The purpose
4. Sprint of this activity
Retrospective is to assure
- or process that resources
improvement are is
meeting
Monitor and control project assigned to all scheduled project activities (and
conducted right after Sprint Demo meeting prior to closing tasks) and
2 2 4
activities that work isThe
the sprint. progressing
objective and deliverables
of this meeting isarefor produced
the SCRUM as
expected.
team to conduct retrospective of the sprint, identify potential
improvements of the process, prioritize and select top
improvements to implement in the next sprint.
The purpose of this activity is to capture and manage project
Manage Issues, Risks and Mandat
2 2 5 issues and risks and changes related to those e.g. changes
Changes ory
of project scope, timeline, costs etc.

The purpose of this task is to ensure that each contract is


Communicate Status and
closed by verifying that all work specified in the contractual Mandat
2 2 6 progress to project
arrangement was completed, and that all defined ory
stakeholders
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
2 3 Stakeholder Analysis Optional
well as the ways they can influence the project. Execute an
analysis of current state as-is and future state to-be
business process maps to quantify the delta transition gap
The purpose of this task is to re-visit the stakeholder
identification results, determine the detailed level of change
Conduct classification of
2 3 1 impacts for the identified stakeholder (groups) in order to
project Stakeholders
create transparency about the organizational and system
changes.

The purpose of this task is to identify key users needed for


2 3 2 Identify Key Users
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
2 4 Change Impact Analysis Optional
business processes have been identified and documented
by comparing the as-is and the to-be business processes.

Validate organizational The purpose of this task is to validate the chosen approach
2 4 1
alignment approach with key stakeholders for the continued project execution.

The purpose of this task is to define the baseline for where


Establish Baseline of Current
2 4 2 organizational change management starts and against which Optional
State
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
2 5 Communication Plan
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
Define Value Argumentation / impact for every stakeholder group. Due to the individual
2 5 1
Key Messages 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.

Define Communication The purpose of this task is to define the communication


2 5 2
strategy strategy for the change management activities.

The purpose of the End User Training Strategy and Plan


End User Training Strategy deliverable is to develop a high level training plan that Mandat
2 6
and Plan provides the recommended approach and corresponding ory
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
Conduct Learning Needs
2 6 1 located. This analysis contains the key customer information
Analysis
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


Develop Detailed End-User
2 6 2 to track evolution of documents and progress of processes Optional
Training Plan
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
2 7 Project Team Training
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
Conduct Blueprint Ramp-up deliverables
2 7 1
Training 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
2 7 2 Conduct Key User training
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
2 8 End User Training Content
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
Adaptation of Pre-delivered
2 8 1 standard end user training material being pre-delivered
Training Content
within the solution. (delivery model 3&4).
Prepare and Build Training
The purpose of this task is to prepare training content in the
2 8 2 Content in Project
system environment being set up for the project.
Environment
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
2 9 Scope Validation
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
For <General Settings #1 - n>
product and customer requirements.esign a solution for
2 9 1 - Conduct Validation and Fit-
these business objects within the SAP solution. These
gap Analysis
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
For <Scenario #1 - n> -
product and customer requirements. Only requirements for
2 9 2 Conduct Validation and Fit-
gap are being captured. It follows an iterative approach.
gap Analysis
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
For <Process #1 - n> -
product and customer requirements. Only requirements for
2 9 3 Conduct Validation and Fit-
gap are being captured. It follows an iterative approach.
gap Analysis
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
Validate pre-defined RICEFW
2 9 4 (reports, forms etc.). Additional customization and
Objects (reports, forms etc.)
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.
Determine Gap list and
2 9 5 The requirements are captured in form of user stories that
Update Product Backlog
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 Solution Design for Business objects are associated to processes and reflected
2###
Business Objects 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,
Define Business Organization Functional, Product-oriented, Regional and geographical, Mandat
2###1
Structure Customer-group, Distribution-channels, Purchasing- ory
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.
Define General Settings and
2###2
Master Data General Settings and Master Data Design also addresses
cross-application general settings and master data for e.g.
countries, languages, currencies, organizational units, units
of measure, number ranges, product hierarchies, material
types and shipment rules.
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
Mandat
2###3 Define User Role Concept concept overview, User role documents - one per role,
ory
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
2###4 Define Logical Data Model
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
Detailed Design - Business started in project preparation. This includes documentation Mandat
2###
Scenario #1 -n of requirements, solution design for the scenarios and ory
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-
Complete Business Scenario
2###1 off purpose. The documented business scenario provides an
Design Document
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
Refine Epics and Update
2###2 implemented?
Product Backlog
Who will work with the processes and what are their
primary business requirements? This will be used as input
for the definition of the user stories.
Priority of each backlog item
Estimated size and effort (the effort is estimated by the
SCRUM team not the PO team)
Business Value
How 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-


Detailed Design - Business be business process down to activity level (PL 3-5) and to Mandat
2###
Process #1 - n describe gaps where the standard solution does not cover all ory
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
Complete Business Process
2###1 formal sign-off purpose. The document provides details of
Design Document
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
Demo or Visualize Standard be enhanced product owner captures this requirement in
2###2
Functionality 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
Define User Stories and
2###3 perspective, provide details on how to test the feature when
Update Product Backlog
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
2### Value Realization Optional
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
2###1 Prepare Value Dashboard
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
Detailed Design - gaps and core enhancements needed to complement
Mandat
2### Configuration and standard functionality, in order to fulfill business
ory
Enhancements 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


Finalize Core Configuration
2###1 for identified core configuration objects related to business
Design
processes.

The purpose of this task is to complete the documentation


Finalize Delta Configuration
2###2 for additionally identified configuration objects related to
Design
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
Define functional Design -
2###3 Interfaces that need to be developed
RICEFW Object #1 - n
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

Define Functional Design - The purpose of this task is to prepare functional design
2###4 SOA & 3rd party applications document for all SOA and 3rd party applications / solution
#1 - n enhancements or extensions.

The purpose of Baseline Build Plan is to define plan to setup


fully functional environment to demonstrate the standard
2### Baseline Build Plan
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,
Define Baseline Build Feature
2###1 understanding of the solution, complexity of the setup and
Set
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
Conduct Baseline Sprint
2###2 the size and complexity of the baseline build. Teams may
Planning Meeting
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
2### Baseline Build 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
Build Baseline User Stories iterative fashion through out the baseline build. The outcome
2###1
(Iterative) 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.
Demo Baseline Feature Set The results of the demo is either acceptance of standard
2###2 and Solicit Feedback feature or new delta requirement that is captured in the form
(Iterative) 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
2### Visualization
understand and judge by the project team members, key
users and stakeholders.

The purpose of this task is to initiate the work to document


Capture Initial Visualization
2###1 the visualization requirements as part of the business
Requirements
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
2###2 Build Visualization (Iterative)
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.
The results of the demo is either acceptance of standard
Demo Visualizations and
2###3 feature or new delta requirement that is captured in the form
Solicit Feedback (Iterative)
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
2### Baseline Build Sign-Off 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.
Conduct Baseline Build and
2###1 The results of the demo is either acceptance of standard
Visualizations Demo
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
Conduct Acceptance Testing
2###2 in the baseline build. This may also include walk-throughs of
of Baseline Build
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
Finalize Documentation of
2###3 particular this pertains to configuration documents, test
Baseline Build
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
Signoff Baseline Build and build, visualizations and product backlog. This signals to the
2###4
Visualizations 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 Mandat
2### Legacy Data Migration
migration of legacy data during the implementation of the ory
SAP applications.
Ensure Master Data The purpose of this task is to ensure that defined processes
2###1 Management Processes and procedures needed to ensure correct quality and
Ownership handling of master data are operational in the organization.

Conduct Data Mapping This task ensures that provided master data for Assemble to
2###2 workshops (master data for order and/or Industrialized content, can be utilized by the
pre-defined solutions) project.

The purpose of this task is to conduct a detailed analysis of


legacy data in order to determine:
Conduct Data Quality The availability and quality of existing data to support Mandat
2###3
Assessment the SAP applications to be implemented ory
The complexities and risks associated with the data
and migration process
The purpose of this task is to design the specific
Define Automated Data architecture, programs, processes, and tasks required to
2###4
Migration Approach 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
Define Manual Data Migration
2###5 database when automated programs are not available or the
Approach
data volume does not justify the investment in developing
such programs.
The purpose of the data quality plan is to define the metrics
2###6 Prepare Data Quality Plan that track and monitor data quality during the data migration
process.
The purpose of data Security Design is to identify and
Prepare Data Security Design
2###7 develop the necessary architectural designs and plans to
and plans
support the security requirements.
The purpose of legacy data archive is to make legacy
master data not considered currently active available for
2### Legacy Data Archive
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
Prepare baseline framework legacy data archiving, meaning the planning for usage of
2###1 for the legacy data archiving legacy-data archive objects, the legacy archive
solution 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
2### Technical Solution Design
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
Prepare technical
2###1 physical standpoint, showing where each of the SAP and
infrastructure specification
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
Identify System Environment
environment needs to have two systems Development and
2###2 for Baseline Build and
Quality Assurance. It is recommended to also provide team
Baseline Acceptance
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


2### User Access and Security 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,
Authorization Requirements Mandat
2###1 to evaluate chosen authorizations concepts against SAP
and Design ory
standards and to determine a feasible implementation
approach.
The purpose of the development environment deliverable is
Development Environment to install a viable, correctly configured technical development Mandat
2###
(DEV) environment that is available for use by the project team to ory
begin the realization phase.

Execute Technical Installation


The purpose of this task is to install SAP components
2###1 of SAP Products for DEV
needed for the realization of project scope.
environment

Execute Technical Upgrade of


The purpose of this task is to upgrade SAP components
2###2 SAP Products for DEV
needed for the realization of project scope.
environment

This task ensures that all solution documentation is made


Install Solution Documentation
2###3 available for the project team. Preferably the repository for
in Solution Manager
this should be Solution Manager.

Execute Technical Installation This task deals with the installation of 3rd party products
2###4
of 3rd party products needed to realize scope of the project.
Set up Role assignment /
The purpose of this task is to set up users in the
2###5 Authorizations / Test Users in
development environment.
DEV

The objective of this task is to perform any remaining


Perform Manual Configuration
2###6 manual configuration changes in the Development
in DEV
environment.

Validate Role assignment / The objective of this task is to validate the assignment of
2###7 Authorizations / Test Users in user role profiles / authorizations to the test users in the
DEV development landscape.

Create master data in DEV


2###8 environment - Master Data #1 Prepare master data required for a business process
-n

The purpose of this deliverable is to create project related


test framework, which gets content input from the existing
Test Policy (1.16.), to build a central foundation around the
taken approach (e.g. Test Approach and Methodology, Test
Standards and Guidelines, Test Case Development, Defect
Management, Reporting and Analysis, Roles and Mandat
2### Testing Strategy
Responsibilities) ory
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
Prepare Test Strategy for functional- and performance testing, which incorporates
2###1
document standard and procedures which will be used for the detailed
test plan preparation / documentation.
The objective of this task is to communicate the testing
Review and Validate Testing
2###2 strategy (functional and performance) to the customer
Strategy with customer
project team and validate it.

Obtain customer sign-off on


2###3 Purpose of this task is to obtain customer approval (sign-off)
Testing Strategy.

The purpose of this deliverable is to refine the Initial Release


2### Release and Sprint Plan 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
2###1 Update Product Backlog 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
Conduct Release Planning
2###2 prioritized product backlog. The meeting is lead by Product
Meeting
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
Validate Release and Sprint been surfaced during the baseline build that may not be part
2###3
Plan Against SOW 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.
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
Phase Closure and Sign-Off Mandat
2### outstanding issues
phase Deliverables ory
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,
Conduct Knowledge
2###1 experiences, project highlights and lessons learned Optional
Management Gate
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
2###2 Conduct Project Quality Gate 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 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
Execute Baseline
2###3 to changing project environment and needs. The team will
Retrospective
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
Conduct Project Management assurance review, with an impartial analysis of all aspects of
2###4
Review Service 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
Conduct Design Review being implemented. It delivers an impartial analysis of all
2###5
Service 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.
The purpose of this task is to ensure that each contract is
closed by verifying that all work specified in the contractual
2###6 Manage Fulfilled Contracts
arrangement was completed, and that all defined
deliverables were accepted.

Obtain Customer Sign-Off for


2###7 Purpose of this task is to obtain customer approval (sign-off)
Phase Completion

This milestone signifies completion of Design activities and


2### MILESTONE: Design to Build
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
3 Realization
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

The purpose of the phase initiation deliverable is to formally


3 1 Phase Initiation
recognize that a new project phase starts.

Allocate Resources and The purpose of this task is to confirm resource availability for Mandat
3 1 1
Update Project Schedule the particular phase. ory

The purpose of this task is to ensure the involvement of the


team and other key resources and their commitment to the
3 1 2 Perform Kickoff Meeting
project schedule. The meeting is also used to examine the
approach for the specific project phase.
The purpose of this deliverable is to initiate sprint in formal
3 2 Sprint Initiation (Iterative)
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
Conduct Sprint Planning
3 2 1 owner team any questions that may still remain open. The
Meeting (Iterative)
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 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
Execution, Monitoring and
3 3 phase (see deliverable Project Management Plan) guide
Controlling Results
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 task is to update the project
Update Project Management management plan and the subsidiary plans based on the Mandat
3 3 1
Plan changes agreed during the projects change management ory
process.
The purpose of this task is to ensure consistent planning,
execution and monitoring of sprint activities. This includes:
Team Activities
The team performs their sprint tasks as to the sprint
backlog, taking priority and done criteria into account
The team attends the Daily Stand-up Meeting. The Daily
Stand-up Meeting serves for information exchange among
the team members. It should not exceed 15 minutes and
occurs same time same place each day. After the meeting,
the team updates the sprint backlog (what are remaining
tasks and efforts). For more information please refer to the
Scrum Meeting Guidelines.
Scrum-of Scrum Meetings are conducted to coordinate the
work between different scrum teams. Scrum of Scrum
Perform Sprint Execution meetings allow teams to discuss their work, focusing
3 3 2
Activities (Iterative) especially on areas of overlap and integration. For more
information please refer to the Scrum Meeting Guidelines
Product Owner Activities
Prepares ready-state user stories for the next sprint(s).
Aligns expectations and requirements with his business
stakeholders.
Is available for answering questions from the team.
Scrum Master Activities
Makes sure that the Scrum process is followed (organizing
and facilitating Daily Scrums, daily updates of remaining
tasks and effort by team, organization of sprint review and
retrospective meetings)
Solves blocks and supports team, including escalation.
Ensures that management or others do not influence
team.

The purpose of this activity is to assure that the project is


Direct and manage project
3 3 3 executed according to what was agreed to in project charter,
execution
scope statement and project management plan.
The purpose of this activity is to assure that resources are
Monitor and control project assigned to all scheduled project activities (and tasks) and
3 3 4
activities that work is progressing and deliverables are produced as
expected.

The purpose of this activity is to capture and manage project


Manage Issues, Risks and Mandat
3 3 5 issues and risks and changes related to those e.g. changes
Changes ory
of project scope, timeline, costs etc.

The purpose of this activity to make sure that project


Communicate Status and
stakeholders are aware of status and progress of the project Mandat
3 3 6 progress to project
including potential disturbances due to existing risks and ory
stakeholders
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
Perform Scrum-Of-Scrums
3 3 7 the same structure. Some teams conduct daily SCRUM of
Meeting (Iterative)
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.
3 4 Organizational Alignment 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
Execute Role Mapping and
3 4 1 (mapping of new business user roles to existing roles and Optional
Transition Planning
organizational structure) and determine an appropriate
transition approach for the business.

The purpose of this task is to get to get complex


Conduct Sounding
3 4 2 organizational feedback regarding the progress and
Board/Pulse Checks
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
Communicate Sprint Scope
3 4 3 team. This may include end users, key stakeholders, people
and Plan (Iterative)
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
Communicate Sprint Result
3 4 4 include end users, key stakeholders, people external to the
(Iterative)
project that have interest in information about the progress
of the project and accomplishments of the project team.

Refine and Execute The purpose of this task is update communication plan and
3 4 5
Communication Plan execute accordingly

The purpose of this deliverable is to determine the potential


Educational Readiness
3 5 issues with the SAP education strategy and solution before
Review
they impact the quality of the SAP software deployment.
The purpose of this task is to capture feedback on both the
Prepare Educational
3 5 1 training strategy and approach, determine issues and
Readiness Report
propose resolutions for identified issues.

The purpose of the deliverable End User Training Content


End User Training Delivery Enabled is to ensure availability of end user training
3 6 Optional
Enabled material, training environment, logistics infrastructure and
skilled instructors.

This task ensures a consistent appearance of the training


Prepare End User Training
3 6 1 materials and documentation by providing the development
Materials and Documentation
team with standard templates.

The purpose of this task is to ensure that the training


3 6 2 Set up Training Environment environment is correctly populated with correct data for Optional
training.
The purpose of this task is to provide a detailed outline of
Perform Training of the presentations and activities that serve to educate and
3 6 3
Trainers prepare the trainers scheduled to instruct end-user training
classes
The purpose of this task is to prepare the execution of end-
Develop End User Training user training by mapping end users to appropriate training
3 6 4 Optional
Schedule and Logistics plan courses, developing a training schedule and logistics plan,
and inviting end users to courses
The purpose of the Configured General Settings and
Configured General Settings Organizational Structure deliverable is to complete and Mandat
3 7
and Organizational Structure document the initial configuration of the system on the basis ory
of the decisions made in the business blueprint phase.

The purpose of this task is to implement the configuration


3 7 1 Configure General Settings related to general settings, and to document this in Solution
Manager.

The purpose of this task is to implement the configuration


Configure Organizational
3 7 2 related to organizational structure, and to document this in
Structure
Solution Manager.

The purpose of the Configured Master Data Objects 1-n


Configured Master Data deliverable is to configure the master data in the SAP Mandat
3 8
Objects #1 - n software system according to the business process ory
requirements specified in the business blueprint phase.

Prepare and Load master data


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

Configure Master Data The purpose of this task is to complete configuration of


3 8 2
Objects #1 - n master data in the system

The purpose of the Core Configuration and Documentation


Core Configuration and
deliverable is to ensure that the configuration is Mandat
3 9 Documentation - Process #1 -
implemented, tested and documented. ory
n

Complete Core Configuration, The purpose of this task is to implement the Core
3 9 1 including documentation and Configuration, write valid test cases and to document this in
test cases Solution Manager.

3 9 2 Prepare Unit Test Cases The purpose of this task is to prepare the test cases

3 9 3 Prepare String Test Cases The purpose of this task is to prepare the test cases
Execute Business Process The purpose of this task is to perform unit test for the
3 9 4 Optional
Unit Test configuration

The objective of this task is to resolve any issues identified


Perform defect resolution for during the Business Process Unit Test. It is crucial that the
3 9 5
Business Process Unit Test issues are re-tested by users that reported them (or
designated re-testers) and that they are confirmed.

Execute Business Process The purpose of this task is to perform string test for the
3 9 6 Optional
String Test configuration

The objective of this task is to resolve any issues identified


Perform defect resolution for during the Process String Test. It is crucial that the issues
3 9 7
Process String Test 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


Delta Configuration - Process ensure that the configuration is implemented, tested and Mandat
3 10
#1 - n documented. ory

The purpose of this task is to implement the Delta


3 10 1 Complete Delta Configuration Configuration, write valid test cases and to document this in
Solution Manager.

The objective of this task is to develop process


Complete Delta Process
3 10 2 documentation for any changed processes or for any new
Documentation
processes added to the standard.

The objective of this task is to develop process test cases


Complete Delta Process Test
3 10 3 for any changed processes or for any new processes added
Cases
to the standard solution.

Execute Business Process The purpose of this task is to perform unit and string test for
3 10 4 Optional
Unit and String Test Cases the configuration

The objective of this task is to resolve any issues identified


Perform defect resolution for during the Unit and String Test. It is crucial that the issues
3 10 5
Unit and String Test are re-tested by users that reported them (or designated re-
testers) and that they are confirmed.

The purpose of this deliverable is to develop and test the


Enhancement Development - Mandat
3 11 RICEFW objects. Documentation to be stored in Solution
RICEFW Object #1 - n ory
Manager.

Develop RICEFW Object #1 - The purpose of this task is to develop the RICEFW object
3 11 1
n according to the functional specification,

The purpose of this task is to document the RICEFW object


Document RICEFW Object #1 information in a technical specification and define the
3 11 2
-n appropriate test case(s). Documentation is stored in Solution
Manager.
Execute Test Cases - The purpose of this task is to perform unit and string test of
3 11 3 Optional
RICEFW Object #1 - n the developments.

The objective of this task is to resolve any issues identified


Perform defect resolution for during the RICEFW object(s) Test. It is crucial that the
3 11 4
RICEFW Object(s) Test 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


3 11 5 Conduct Final Code Review 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-
3 12 Business Process Procedure user training documentation and test case creation. The
procedures may also be used by security to develop roles
and authorizations.

Develop Business Process The purpose of this task is to validate and complete
3 12 1
Procedure Document Business Process Procedures from the blueprint phase.

Validate and Complete


The purpose of this task is to validate and complete
3 12 2 Business Process Procedure
Business Process Procedures from the blueprint phase.
Document

The purpose of the value audit deliverable during the


realization phase is to monitor and control the
3 13 Value Audits implementation of key process changes and value enablers, Optional
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
3 13 1 Perform Value Audit 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


3 14 Scenario Test #1 - n the scenarios designed can be supported by the solution
implemented.
Prepare Test Case - Scenario The purpose of this task is to identify and document
3 14 1
#1 - n applicable test case(s) for the scenario.
Execute Test Case - Scenario
3 14 2 The purpose of this task is to perform scenario test. Optional
#1 - n
The objective of this task is to resolve any issues identified
Resolve Issues for Scenario during the scenario testing. It is crucial that the issues are
3 14 3
#1 - n re-tested by users that reported them (or designated re-
testers) and that they are confirmed.

Obtain Customer Sign-off for


3 14 4 Purpose of this task is to obtain customer approval (sign-off)
Testing of Scenario #1 - n

The purpose of the quality assurance infrastructure and


Quality Assurance environment design and setup deliverable is to install a Mandat
3 15
Environment (QAS) viable, correctly configured technical QA environment that is ory
available for use by the project team to perform QA testing.

Execute Technical Installation


The purpose of this task is to install SAP components
3 15 1 of SAP Products for QAS
needed for the realization of project scope.
environment
Execute Technical Upgrade of
The purpose of this task is to upgrade SAP components
3 15 2 SAP Products for QAS
needed for the realization of project scope.
environment

The purpose of this task is to build the quality assurance


Import Configuration and
(QA) environment with changes that have been unit-tested
3 15 3 Development Objects to QAS
and released from the development environment.
Environment

Set up Role Assignment /


The purpose of this task is to set up users in the Quality
3 15 4 Authorizations / Test Users in
Assurance environment.
QAS

Prepare and Load Master


The purpose of this task is to prepare master data required
3 15 5 Data into QAS Environment
for all business processes in QAS.
for <SCOPE OPTION>

The objective of this task is to perform any remaining


Perform Manual Configuration
3 15 6 manual configuration changes in the Quality Assurance
Settings in QAS
environment.

This milestone signifies completion of Build activities and


3 16 MILESTONE: Build to Test 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,
3 17 Sprint Closing
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
Conduct Sprint Review
3 17 1 user story is amended by the product owner team, prioritized
Meeting
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
3 17 2 Signoff Sprint Results 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 potential improvements of
the SCRUM process. The objective of this task is to serve as
continuous improvement mechanism for the team to adjust
3 17 3 Conduct Sprint Retrospective 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 the preliminary cutover plan deliverable is to
document the strategy, scope and timelines for moving from Mandat
3 18 Preliminary Cutover plan
the as-is solution to the to-be solution and the hyper care ory
period immediately following go-live.
Conduct Organizational
The purpose of this task is to assess to what level the
3 18 1 Change Management Optional
organization is prepared for the cut over/transition
Readiness Check

Conduct Production Support This purpose of this task is to check to what extent the
3 18 2
Readiness Check support organization is operational and ready for cut over

Conduct Master Data Process This task checks that proper governance of master data
3 18 3
Governance Readiness Check 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
Prepare Preliminary Cutover documenting activities such as the transfer of data from the
3 18 4
plan 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
Review Preliminary Cutover
3 18 5 and other constraints. At the end of the review the project
Plan with customer
team will have understanding of necessary adjustments to
the preliminary cutover plan.
The purpose of this task is to refine the preliminary cutover
Refine Preliminary Cutover
3 18 6 plan based on information the project team learned in the
Plan
cutover plan review with customer.
The purpose of Approved Integration Test is to ensure
functional correctness. It test the integration of SAP
Mandat
3 19 Approved Integration Test solutions with non-SAP applications and interfaces and can
ory
be executed in an iterative manner.

The purpose of this task is to define and document


Prepare Integration Test Plan,
integration test cases, end-to-end customer business
3 19 1 including test of roles and
process scenarios, according to the test plan. Test plans and
authorizations
test case documentation is stored in Solution Manager.

Prepare and document The purpose of this task is to document the integration test
3 19 2
Integration Test Case #1 - n case outlined in the integration test plan

The objective of this task is to perform the Integration test


Execute Integration Test Case according to previously defined plan. During the test all
3 19 3
#1 - n issues must be logged and documented in the system for
traceability purpose.
The objective of this task is to resolve any issues identified
Perform defect resolution for during the Integration Test. It is crucial that the issues are re-
3 19 4
Integration Test tested by users that reported them (or designated re-testers)
and that they are confirmed.
Obtain Integration Test The purpose of this task is to obtain customer approval
3 19 5
Results Sign-off (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
Mandat
3 20 Legacy Data Migration designed to move, cleanse, transform, and enrich legacy
ory
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,


Develop Data Migration programs, and processes that support the extraction,
3 20 1
Program Units validation, harmonization, enrichment, and cleansing of the
legacy data.
The purpose of this task is to execute and validate the
Execute and validate Manual
3 20 2 manual conversion as described in the manual data
Data Migration
migration approach
The purpose of this task is to visualize the data quality
3 20 3 Obtain Data Quality Reports
metrics defined in the data quality plan
The purpose of this task is to load the cleansed legacy data
3 20 4 Perform SAP Target Load Test 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
Obtain Data Migration Test Mandat
3 20 5 various test cycles so the team can monitor the accuracy
Results ory
and efficiency of the data migration solution.
The purpose of this task is to provide one final assessment
Conduct Final Data Quality Mandat
3 20 6 at the end of the realization phase to report on the quality of
Assessment ory
the converted legacy data
The purpose of this deliverable is to execute the User
Approved User Acceptance acceptance test (UAT). This is the last test cycle of an SAP Mandat
3 21
Test solution implementation and is an essential part of gaining ory
end-user acceptance of the software system.
The purpose of this task is to define and document UAT test
Prepare UA Test Plan for
3 21 1 cases according to the test plan. Test plans and test case
<SCOPE OPTION>
documentation is stored in Solution Manager

Prepare and Document User


The purpose of this task is to document the integration test
3 21 2 Acceptance Test Cases for
case outlined in the UAT test plan
<SCOPE OPTION>

The objective of this task is to perform the End User


Execute UA Test Plan for Acceptance test according to previously defined plan. During
3 21 3
<SCOPE OPTION> 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
Perform UA Defect Resolution during the User Acceptance Test. It is crucial that the issues Mandat
3 21 4
for <SCOPE OPTION> are re-tested by users that reported them (or designated re- ory
testers) and that they are confirmed.
Obtain UA Test Results Sign- The purpose of this task is to execute the testing, document
3 21 5
off 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
3 22 SAP Data Archiving 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
Capture Legal and Business
3 22 1 retention requirements needed in prier to establish the
Retention Requirements
baseline for data arched and removal plan.
The purpose of this task is to develop the data archive plan
3 22 2 Prepare 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
Prepare Data Archive Storage storage plan needed for the execution of each data archive
3 22 3
Plan run and creates the indexes for each archive execution.

Conduct Data Archive The purpose of this task is to test the data archive
3 22 4
Implementation Test implementation execution in QAS.
The purpose of the production infrastructure and
Production Environment environment design and setup deliverable is to install a Mandat
3 23
(PRD) viable, correctly configured technical production environment ory
to support productive operations of the delivered solution.

Execute Technical Installation


The purpose of this task is to install and set up the
3 23 1 of SAP Products for PRD
production environment.
Environment

Execute Technical Upgrade of


The purpose of this task is to upgrade the production
3 23 2 SAP Products for PRD
environment.
Environment

Import Configuration and The purpose of this task is to build the production (PRD)
3 23 3 Development Objects to PRD environment with changes that have been tested and
Environment released from the quality assurance (QA) environment.

Set up Role assignment /


The purpose of this task is to set up users in the production
3 23 4 Authorizations / Test Users in
environment.
PRD for <SCOPE OPTION>

Populate PRD with Test The purpose of this task is to ensure that appropriate master
3 23 5 Master Data for <SCOPE data is available for testing in the production environment
OPTION> (system test).

Prepare and Load master data


The purpose of this task is to prepare master data required
3 23 6 into PRD environment for
for all business processes in PRD.
<SCOPE OPTION>

Perform Manual Configuration


The purpose of this task is to perform any remaining manual
3 23 7 Settings in PRD for <SCOPE
configuration changes in the production environment.
OPTION>

The purpose of this deliverable is to execute the setup of


3 24 Failover Environment Optional
Availability and Continuity Management (ACM)
Prepare Failover Environment The purpose of this task is to define the approach and plan
3 24 1
Design and Plan for Availability and Continuity Management.

Set-up Failover Environment


The purpose of this task is to set and execute the identified
3 24 2 and Execute Identified
failure scenarios.
Scenarios

The purpose of this task is to obtain the results from the


Obtain Failover Environment
3 24 3 failover scenario execution and determine the appropriate
Test Results
mitigation actions for the test findings.

The purpose of planned Performance and System Test is to


checks the entire system, consisting of databases,
Mandat
3 25 System and Performance Test applications servers, front ends, printers etc. The
ory
performance test measures the throughput and response
times of the system.
The task defines and documents the identified test cases
3 25 1 Prepare System Test Plan related to system and performance test. Outcome is
documented in a test plan.
The task defines and documents the identified test cases
Prepare Performance Test
3 25 2 related to system and performance test. Outcome is
Plan
documented in a test plan.
The purpose of this task is to document the test case
3 25 3 Prepare System Test Cases
outlined in the test plan
Prepare Performance Test The purpose of this task is to document the test case
3 25 4
Cases outlined in the test plan

The purpose of this task is to execute the performance tests


3 25 5 Execute 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
Perform Performance Test during the performance or load testing. Upon resolution the
3 25 6
Defect Resolution issues need to be re-tested and confirmed by responsible
testers.
The purpose of this task is to obtain customer approval
3 25 7 Obtain Test Results Sign-off
(sign-off)
The purpose of this service is to support the start of
production of an SAP Solution. During this service, SAP
3 26 SAP Going Live Check service engineers check the solution for potential risks and Optional
give recommendations ensuring optimal performance and
system availability for core business processes.

The purpose of this task is to perform the first session of the


SAP GoingLive Check.
The service consiste of two sessions - Analysis and
Perform SAP Going Live Verification, and includes:
Check - Analysis Session and - Verification of the technical capabilities of the production
3 26 1
schedule the Verification environment (sizing plausibility)
Session - 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
System User Roles and
3 27 Administration deliverable is to establish an effective Optional
Authorization Administration
operation processes for security

Set up administrative
The purpose of this task is to set-up, document and execute
3 27 1 procedures for Roles and
the administrative procedure for Roles and Authorizations.
Authorizations

The purpose of the technical operations and handover


strategy deliverable is to update refine two prior deliverables
Technical Operations and
3 28 from the Business Blueprint phase, and prepare a strategy Optional
Handover Plan
to hand off operations of the solution landscape to the post-
production support organization.

The purpose of this task is to ensure that proper


Validate Support Center/Help
3 28 1 staffing(people and competence) is in place for the support
Desk Staffing Strategy
org/team

The purpose of this task is to ensure that adequate support


3 28 2 Establish Support Processes
processes are in place for the Go Live phase and beyond.

This task describes the considerations that are required to


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

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
Phase Closure and Sign-Off Mandat
3 29 outstanding issues
phase Deliverables ory
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,
Conduct Knowledge
3 29 1 experiences, project highlights and lessons learned Optional
Management Gate
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
Conduct Project Quality
3 29 2 gate have been completed in compliance with
Gate(s)
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 Project Management Review is to provide a


proactive quality assurance review, with an impartial analysis
Conduct Project Management
3 29 3 of all aspects of the project across all project management
Review Service
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
Conduct Design Review being implemented. It delivers an impartial analysis of all
3 29 4
Service 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.
The purpose of this task is to ensure that each contract is
closed by verifying that all work specified in the contractual
3 29 5 Manage Fulfilled Contracts
arrangement was completed, and that all defined
deliverables were accepted.

Obtain Customer Sign-Off for


3 29 6 Purpose of this task is to obtain customer approval (sign-off)
Phase Completion

MILESTONE: Test to This milestone concludes testing activities and start of


3 30
Deployment 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
4 Final Preparation 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.
The purpose of the phase initiation deliverable is to formally
4 1 Phase Initiation
recognize that a new project phase starts.

Allocate Resources and The purpose of this task is to confirm resource availability for Mandat
4 1 1
Update Project Schedule the particular phase. ory

The purpose of this task is to ensure the involvement of the


team and other key resources and their commitment to the
4 1 2 Perform Kickoff Meeting
project schedule. The meeting is also used to examine the
approach for the specific project phase.
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
Execution, Monitoring and
4 2 phase (see deliverable Project Management Plan) guide
Controlling Results
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 task is to update the project
Update Project Management management plan and the subsidiary plans based on the Mandat
4 2 1
Plan changes agreed during the projects change management ory
process.
The purpose of this activity is to assure that the project is
Direct and manage project
4 2 2 executed according to what was agreed to in project charter,
execution
scope statement and project management plan.
The purpose of this activity is to assure that resources are
Monitor and control project assigned to all scheduled project activities (and tasks) and
4 2 3
activities that work is progressing and deliverables are produced as
expected.

The purpose of this activity is to capture and manage project


Manage Issues, Risks and Mandat
4 2 4 issues and risks and changes related to those e.g. changes
Changes ory
of project scope, timeline, costs etc.

The purpose of this activity to make sure that project


Communicate Status and
stakeholders are aware of status and progress of the project Mandat
4 2 5 progress to project
including potential disturbances due to existing risks and ory
stakeholders
issues.
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
Organizational and Production level is not there, it is critical to determine where additional
4 3
Support Readiness Check 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


Perform Business validation role mapping and change impact analysis. This is done with
4 3 1 Optional
and Transition Planning the impacted business stakeholders in order to gain
sponsors approval.

Validate that Master Data The purpose of this task is to ensure the customer
4 3 2 Support Processes is establishes the means to manage their data in an integrated Optional
established 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
Establish Business Process
4 3 3 Monitoring Optional
Operations
- Data Volume Management
- Job Scheduling Management
- Transactional Consistency and Data Integrity

This task describes how all SAP technologies can be


Establish System administered to run a customer solution efficiently. The
4 3 4 Optional
Administration and Control 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


Establish Security / Role and
4 3 5 manage security, roles and authorizations in their productive Optional
Authorization Management
environment.

The purpose of this task is to extract the knowledge about


Execute Transition to the scope, customizations, and business processes of the
4 3 6 Optional
Production Support 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
Pre Go-Live End-User Training
4 4 solution. In the checklist, items governing training delivery,
Delivery
communications, and future planning clarify the status of all
aspects of the training initiative.

Validate and adapt end user


4 4 1 The purpose of this task is to prepare the training delivery.
training material developed

The objective of this task is to deliver end user training to


4 4 2 Deliver End User training identified end user groups according to the previously
developed training schedule.
Collect Training Evaluations The purpose of this task is to capture feedback on both the
4 4 3 Optional
feedback training session and the trainer delivering the material

This task checks how prepared the people in the


Perform People Readiness
4 4 4 organization are with regards to the identified changes and Optional
assessment
received EU training.

The purpose of this deliverable is to present the findings and


recommendations from the results of technical tests such as
Approved Technical System
4 5 disaster recovery tests, backup and restore tests, and other
Tests
required technical or basis-related tests to the customer or
project team for final signoff in order to exit system testing.
The purpose of this task is to prepare and execute the
Execute Technical System
4 5 1 system tests. The outcome/results should be approved by
Tests
the customer.
The objective of this task is to resolve issues identified
Perform System Test Defect
4 5 2 during the system testing. Upon resolution the issues need
Resolution
to be re-tested and confirmed by responsible testers.
Obtain System Test Results
4 5 3 Purpose of this task is to obtain customer approval (sign-off)
Sign-off
The purpose of production cutover is to perform the cutover
to the production software and go live. At this point, the
4 6 Production Cutover
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
Execute Go Live Simulations 1 cutover activities. During simulation, the main objective is to Mandat
4 6 1
thru N validate and document the tasks, sequence, and duration of ory
items on the cutover plan.

Conduct Data Quality This task verifies that master data support is set up and Mandat
4 6 2
Readiness Check process is operational ory

The purpose of this task is to complete the Cut Over plan Mandat
4 6 3 Finalize Cutover Plan
with results obtained from the Go Live simulations. ory

The objective of this task is to perform all the cutover


preparation activities remaining to be closed prior to cutover
Perform Pre-Cutover
4 6 4 weekend. The detailed cutover plan contains the complete
Weekend Closing Activities
listing of all pre-cutover activities, their dependencies,
owners, and timing.

Final Check of Production


This task will confirm that the productive system is ready for
4 6 5 Readiness and Sign-Off for Optional
Go Live.
transition to Production

The purpose of this task is the loading of production data


from legacy systems into the production environment. Once
Perform Cutover Weekend
all preparations and configurations on both the technical and
4 6 6 Activities including Final
application levels are completed, the final productive
Production Data Load
solution can be set up and data loaded. The solution is live
in a production environment

Obtain Production Data Load Mandat


4 6 7 Purpose of this task is to obtain customer approval (sign-off)
Sign-off ory

Purpose of this task is to hand over the finalized


Initiate Solution Manager
implementation project and it's content, and set up as a
4 6 8 Update - Solution Optional
productive solution in SAP Solution Manager. This provides
Documentation
the basis for the follow up activities in the Run Phase.

The purpose of this deliverable is to formally close the


4 7 Release Closing 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
Prepare Product Backlog for ready them for next release/sprint planning meeting. The
4 7 1
Next Release/Sprint 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 potential improvements of
the SCRUM process. The objective of this task is to serve as
continuous improvement mechanism for the team to adjust
Conduct Release
4 7 2 to changing project environment and needs. The team will
Retrospective
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 update the Release and Sprint
Update the Release and Plan according to changed priorities and focus of the team.
4 7 3
Sprint plan It is accountability of Product Owner to maintain the Release
and Sprint plan and keep it current during the project.
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
Phase Closure and Sign-Off Mandat
4 8 outstanding issues
phase Deliverables ory
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,
Conduct Knowledge
4 8 1 experiences, project highlights and lessons learned Optional
Management Gate
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
4 8 2 Conduct Project Quality Gate 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 Project Management Review is to provide a


proactive quality assurance review, with an impartial analysis
Conduct Project Management
4 8 3 of all aspects of the project across all project management
Review Service
disciplines, enabling early detection of project issues with
actionable recommendations.
The purpose of this task is to ensure that each contract is
closed by verifying that all work specified in the contractual
4 8 4 Manage Fulfilled Contracts
arrangement was completed, and that all defined
deliverables were accepted.

Obtain Customer Sign-Off for The purpose of this task is to obtain customer approval
4 8 5
Phase Completion (sign-off)
This milestone signifies formal transition to production
MILESTONE: Production environment. Production is up and running, cutover
4 9
System Live 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
5 Go Live Support support are planned and executed in this phase. At the
end of the designated extra-care period, sustaining
production support processes planned in final
preparation and executed as part of go-live support
become the core support for continuous improvement in
the ongoing solution.

The purpose of the phase initiation deliverable is to formally


5 1 Phase Initiation
recognize that a new project phase starts.

Allocate Resources and The purpose of this task is to confirm resource availability for Mandat
5 1 1
Update Project Schedule the particular phase. ory

The purpose of this task is to ensure the involvement of the


team and other key resources and their commitment to the
5 1 2 Perform Kickoff Meeting
project schedule. The meeting is also used to examine the
approach for the specific project phase.

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
Execution, Monitoring and
5 2 phase (see deliverable Project Management Plan) guide
Controlling Results
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 task is to update the project
Update Project Management management plan and the subsidiary plans based on the Mandat
5 2 1
Plan changes agreed during the projects change management ory
process.
The purpose of this activity is to assure that the project is
Direct and manage project
5 2 2 executed according to what was agreed to in project charter,
execution
scope statement and project management plan.
The purpose of this activity is to assure that resources are
Monitor and control project assigned to all scheduled project activities (and tasks) and
5 2 3
activities that work is progressing and deliverables are produced as
expected.

The purpose of this activity is to capture and manage project


Manage Issues, Risks and Mandat
5 2 4 issues and risks and changes related to those e.g. changes
Changes ory
of project scope, timeline, costs etc.

The purpose of this activity to make sure that project


Communicate Status and
stakeholders are aware of status and progress of the project Mandat
5 2 5 progress to project
including potential disturbances due to existing risks and ory
stakeholders
issues.

The purpose of EU training during go-live support is to


Post Go live End-User ensure that end users have adopted the solution, knowledge
5 3 Optional
Training resources are maintained, and responses to the end-user
acceptance survey are positive.
Prepare End-User Training for This purpose of this task is to adapt available training
5 3 1
<SCOPE OPTION> material and make it suitable for End User training.

This task executes the delivery of EU training as well as


Deliver End-User Training for
5 3 2 capturing feedback on both the training session and the
<SCOPE OPTION>
trainer.
Collect Training Evaluations The purpose of this task is to capture feedback on both the
5 3 3
feedback training session and the trainer delivering the material

This task checks how prepared the people in the


Perform People Readiness
5 3 4 organization are with regards to the identified changes and
assessment
received EU training.
The purpose of the production support and transfer to
solution deliverable is to confirm that the resources and
SAP Going Live Check -
5 4 processes are in place to support the ongoing solution and
Verification Session
to complete the steps required to close the project and finish
documentation.
Conduct SAP Going Live
The purpose of this task is to verify that the requirements
5 4 1 Check - Verification Session
identified in earlier sessions are met.
Remote

The purpose of the production support and transfer to


solution deliverable is to confirm that the resources and
Production Support After Go
5 5 processes are in place to support the ongoing solution and Optional
Live
to complete the steps required to close the project and finish
documentation.

The purpose of this task is to implement ongoing production


5 5 1 Provide Post Go Live Support 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
Monitoring Open Issues to
5 5 2 open project issues which is a prerequisite for the final
Resolution
project closure.
The objective of this task is to resolve any functional issues
identified during the hyper care period after cutover. It is
5 5 3 Resolve Functional Issues
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
5 5 4 Resolve Technical Issues
crucial that the issues are re-tested and confirmed by users
that reported them.

The purpose of this task is to ensure knowledge transfer


Complete Transition to
regarding the scope, customizations, and business
5 5 5 Customers Production Optional
processes in the customers production environments to the
Support organization
long-term SAP support center team.

Purpose of this task is to hand over the finalized


Finalize Solution Manager
implementation project and it's content, and set up as a
5 5 6 Update - Solution Optional
productive solution in SAP Solution Manager. This provides
Documentation
the basis for the follow up activities in the Operate Phase.
Obtain Solution Transition to
5 5 7 Production Acceptance Purpose of this task is to obtain customer approval (sign-off)
Protocol Sign-off

This milestone signifies formal transition from post


5 6 MILESTONE: Deploy to Run production sustainment support to long term support and
operation of the new environment
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
Project Closure and Sign-Off Mandat
5 7 outstanding issues
Project Deliverables ory
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,
Conduct Knowledge
5 7 1 experiences, project highlights and lessons learned Optional
Management Gate
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
5 7 2 Conduct Project Quality Gate 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 Project Management Review is to provide a


proactive quality assurance review, with an impartial analysis
Conduct Project Management
5 7 3 of all aspects of the project across all project management
Review Service
disciplines, enabling early detection of project issues with
actionable recommendations.
The purpose of this task is to ensure that each contract is
closed by verifying that all work specified in the contractual
5 7 4 Manage Fulfilled Contracts
arrangement was completed, and that all defined
deliverables were accepted.
The purpose of this activity is to achieve a closure of all
Resolve and close open
5 7 5 open project issues which is a prerequisite for the final
issues
project closure.
The purpose of this activity is to document the results of the
Finalize Project Closeout
5 7 6 project, both regarding achieved objectives, deliverables as
Report
well as adherence to schedule, costs and delivered value.
The purpose of this activity is to formally close the project by
Obtain Sign-off for Project
obtaining customer signatures on dedicated
5 7 7 Closure and Results
deliverables/documents e.g. Project Quality Gate, Project
Acceptance
Closeout Report
MILESTONE: Project
5 8 This milestone marks official closure of the project
Complete
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
6 Operate
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
Operations Maturity
6 1 customer's support operations to determine areas in need of
Assessment
optimization

Perform evaluation and The purpose of this activity is to assess business and
assessment of operations technical requirements for operations and to define what
6 1 1
capabilities, including CoE aspects of the operations need to be adjusted, enhanced or
operational set up implemented.

Prepare Maturity Assessment The report should detail assessment results and finding,
6 1 2
Report including proposed actions for how to bridge identified gaps.
Centrally document and relate business processes and
Solution Documentation technical information of SAP and non-SAP Solutions
6 2
Optimized ensuring transparency, efficient maintenance and
collaboration
Re-visit result of ALM roadmap workshop from the project
Perform assessment of preparation, lessons learned findings from the
6 2 1
Solution Documentation set up 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
Solution Implementation Is a part of the application lifecycle and is designed to
6 3
Optimized decouple technical installation from business innovation
Uses the SAP Solution Manager to implement the innovation
in the system landscape

Re-visit result of ALM roadmap workshop from the project


Perform assessment of
preparation, lessons learned findings from the
6 3 1 Solution Implementation set
implementation project and determine if potential gaps exist
up
for the Solution Implementation area.
The template management approach allows customers with
multi-site SAP installations to efficiently manage their
Template Management
6 4 business processes across geographical distances from
Optimized
initial template definition to template implementation and
template optimization, for example as part of a global rollout
Re-visit result of ALM roadmap workshop from the project
Perform assessment of preparation, lessons learned findings from the
6 4 1
Template Management set up 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
6 5 Test Management Optimized
software change events

Re-visit result of ALM roadmap workshop from the project


Perform assessment of Test preparation, lessons learned findings from the
6 5 1
Management set up 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
Change Control Management
6 6 solution and minimized risk through segregation of duties
Optimized
and transparency of changes
Efficient solution management all project and system
information is saved in SAP Solution Manager

Re-visit result of ALM roadmap workshop from the project


Perform assessment of
preparation, lessons learned findings from the
6 6 1 Change Control Management
implementation project and determine if potential gaps exist
set up
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
Application Incident Partner Support employees.
6 7
Management Optimized Is integrated in all ALM processes of SAP Solution Manager,
in any SAP Business Suite solution and could be connected
to an Non-SAP Help Desk application
Includes follow up activities as knowledge research, root
cause analysis or Change Management

Re-visit result of ALM roadmap workshop from the project


Perform assessment of preparation, lessons learned findings from the
6 7 1
Incident Management set up 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
Technical Operations centralized tools for all aspects of operations in SAP
6 8
Optimized Solution Manager
Provides End-to-End reporting functionality either out-of-the-
box or individually created by customers

Re-visit result of ALM roadmap workshop from the project


Perform assessment of preparation, lessons learned findings from the
6 8 1
Technical Operations set up implementation project and determine if potential gaps exist
for the Technical Operations area.
SAP Business Process Integration & Automation
Management (BPIAM) comprises the most important
Business Process Operations application related operations topics necessary to ensure
6 9
Optimized the smooth and reliable flow of the core business processes
to meet a company's business requirements.

Re-visit result of ALM roadmap workshop from the project


Perform assessment of preparation, lessons learned findings from the
6 9 1
Process Operations set up 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)).
Maintenance Management
6### SAP Notes are collected and released as Support
Optimized
Packages. Support Packages are applied to SAP solutions
to comply with legal requirements or run on latest
technology.

Re-visit result of ALM roadmap workshop from the project


Perform assessment of
preparation, lessons learned findings from the
6###1 Maintenance Management set
implementation project and determine if potential gaps exist
up
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
Upgrade Management
6### Allows SAP customers to better understand and manage the
Optimized
major technical risks and challenges in an upgrade project,
and to make the upgrade project a non-event for the
business.

Re-visit result of ALM roadmap workshop from the project


Perform assessment of preparation, lessons learned findings from the
6###1
Upgrade Management set up implementation project and determine if potential gaps exist
for the Upgrade Management area.
Q-Gate Key Accountable
Work Stream
Deliverable Role

_Phase

PM - Project
Management

PM - Project Project
Management Manager

Project Guideline
PM - Project Project
(incl. Travel
Management Manager
Guideline)

PM - Project
Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project
Project Charter
Management

PM - Project Project
Management Manager

OCM -
Organizational Project
Change Manager
Management
PM - Project Project
Management Manager

PM - Project Project
Management Manager

Phase Kick Off PM - Project


Meeting Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Scope Statement PM - Project


Document Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Application
Management Consultant

PM - Project Project
Management Manager

Work Breakdown PM - Project Project


Structure (WBS) Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager
PM - Project
Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager
Project
Budgetplan PM - Project Project
(internal & Management Manager
external)
Project
PM - Project
Management
Management
Plan(s)

PM - Project Project
Management Manager

PM - Project Project
Management Manager
ALM - Application
Lifecycle
Management

andards and tools, such as SCRUM board, burn-down chart, product backlog template and retrospective template. Organization of daily
early defined and understood, test procedure is defined, etc.)
unit tested) PM - Project Project
est is defined (automated), test data
Management
is ready) Manager
tation is complete, ALM Solution Documentation is ready, Feature passed Integration Test)
ation process == definition of done of the previous step. Using clear definition of Ready and Done is critical for SCRUM based implemen

Solution Manager
Usage guideline, ALM - Application Business
Business Process Lifecycle Consultant
Modeling Management
Standards

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

ALM - Application
Application
Lifecycle
Consultant
Management

Test
Test Management ISM - Test Management
Standards Management Consultant

Change Request
TSM - Technical
and Transport Application
Solution
Management Consultant
Management
Standards (CTS)
TSM - Technical
Application
Solution
Consultant
Management

Post
TSM - Technical
Implementation Technology
Solution
Service and Consultant
Management
Support

ALM - Application
Application
Lifecycle
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

PM - Project
Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager
Risk List (internal
& external),
PM - Project Project
Project Change
Management Manager
log, Project
Issues log

Project
(Performance) PM - Project Project
Report (internal & Management Manager
external)

OCM -
Organizational
OCM Roadmap
Change
Management
OCM -
Business
Organizational
Consultant
Change
Management

Training - Training

Project Team Education


Training Plan & Training - Training Consultant
Schedule

Training - Training

PM - Project Project
Management Manager

Business Process
BPM - Business
Map
Process
Business Process
Management
List

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management
BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

VM - Value
Value Map
Management

Business
VM - Value
Consultant
Management

PM - Project Application
Management Consultant

Business
Value Audit of VM - Value
Consultant
Scope Management

BPM - Business
Process
Management

BPM - Business Business


Process Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management
ISM - Test
Management

ISM - Test Technology


Management Consultant

ISM - Test Project


Management Manager

Data Migration
Approach, Start DM - Data Migration
and Scope

Application
DM - Data Migration
Consultant

Technology
DM - Data Migration
Architect

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Technology
DM - Data Migration
Architect

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant
Solution TSM - Technical
Landscape Solution
Design Management

TSM - Technical
Solution
Solution
Architect
Management

TSM - Technical
Technology
Solution
Architect
Management

TSM - Technical
Solution
Management

TSM - Technical
Technology
Solution
Architect
Management

TSM - Technical
Solution
Management

TSM - Technical
Solution
Solution
Architect
Management

Proj Support TSM - Technical


Tools & Sys Solution
Setup Management
TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

PM - Project
Management
Project (phase)
PM - Project Project
Lessons Learned
Management Manager
(internal)

PM - Project Business
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

_Milestone

_Phase

PM - Project
Management

Project Schedule PM - Project Project


(incl. milestones) Management Manager

PM - Project Project
Management Manager

PM - Project
Management
Project
PM - Project Project
Management
Management Manager
Plan(s)

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Risk List (internal


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

Project
(Performance) PM - Project Project
Report (internal & Management Manager
external

OCM -
Stakeholder
Organizational
Analysis
Change
(Internal)
Management

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

OCM -
Organizational
Change
Management

OCM -
Business
Organizational
Consultant
Change
Management

OCM -
Business
Organizational
Consultant
Change
Management

Training Project
Training - Training
Plan

Education
Training - Training Consultant

End User
Education
Training and
Training - Training Consultant
Documentation
Developed

Training - Training
Business
Training - Training Consultant

Training - Training Instructor

Training - Training

Education
Training - Training Consultant

Education
Training - Training Consultant

BPM - Business
Process
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management
BPM - Business Integration
Process Development
Management Consultant

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Process
Management

Business
BPM - Business
Blueprint Application
Process
Documents(Org Consultant
Management
Structure)

BPM - Business
Application
Process
Consultant
Management

BPM - Business
User Role Application
Process
Document Consultant
Management

BPM - Business
Application
Process
Consultant
Management
BPM - Business
Solution
Process
Documentation
Management

BPM - Business
Application
Process
Consultant
Management

PM - Project Application
Management Consultant

BPM - Business
Solution
Process
Documentation
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management
PM - Project Application
Management Consultant

Value Audit of VM - Value


Scope Management

Business
VM - Value
Consultant
Management

Development BPM - Business


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

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business Integration


Process Development
Management Consultant

BPM - Business Integration


Process Development
Management Consultant

PM - Project
Management

PM - Project Project
Management Manager
PM - Project Project
Management Manager

PM - Project
Management

PM - Project Application
Management Consultant

PM - Project Application
Management Consultant

BPM - Business
Process
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Process
Management
BPM - Business
Application
Process
Consultant
Management

BPM - Business
Project
Process
Manager
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Project
Process
Manager
Management

Data Migration
DM - Data Migration
Design / Plan

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Test Cases & Application


DM - Data Migration
Results Consultant

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant
DA - Data Archiving

Technology
DA - Data Archiving
Architect

TSM - Technical
Solution
Management

TSM - Technical
Technology
Solution
Architect
Management

BPM - Business
Technology
Process
Architect
Management

TSM - Technical
Solution
Management

Authorization TSM - Technical


Technology
Requirements Solution
Consultant
and Design Management

Solution TSM - Technical


Landscape Solution
Design Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

TSM - Technical
Application
Solution
Consultant
Management

Test Strategy ISM - Test


Plans & Results Management

ISM - Test Technology


Management Consultant

ISM - Test Technology


Management Consultant

ISM - Test Technology


Management Consultant

PM - Project
Management

PM - Project Application
Management Consultant

PM - Project Project
Management Manager
PM - Project Project
Management Manager

Delivery of
projects Results
PM - Project
Delivery
Management
Acceptance
Protocol

Project (phase)
PM - Project Project
Lessons Learned
Management Manager
(internal)

PM - Project Business
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager
PM - Project Project
Management Manager

PM - Project Project
Management Manager

_Milestone

_Phase

PM - Project
Management

Project Schedule PM - Project Project


(incl. milestones) Management Manager

PM - Project Project
Management Manager

PM - Project
Management

PM - Project Project
Management Manager

PM - Project
Management

Project
PM - Project Project
Management
Management Manager
Plan(s)
PM - Project Application
Management Consultant

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Risk List (internal


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

Project
(Performance) PM - Project Project
Report (internal & Management Manager
external

PM - Project Project
Management Manager
OCM -
Organizational
Change
Management

OCM -
Business
User Role Organizational
Consultant
Document Change
Management

OCM -
Business
Organizational
Consultant
Change
Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

OCM -
Business
Organizational
Consultant
Change
Management

Training - Training

Education
Training - Training Consultant

End User
Training and
Training - Training
Documentation
Developed

Education
Training - Training Consultant

Training
Education
Environment
Training - Training Consultant
Population and
Testing
Education
Training - Training Consultant

End User
Training Education
Training - Training
Schedule and Coordinator
Logistics
Solution
Documentation
BPM - Business
(incl. Process list,
Process
Configuration,
Management
Interfaces,
Developments)

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

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

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

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

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management
BPM - Business
Test cases & Application
Process
Results Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Test cases & Application
Process
Results Consultant
Management

BPM - Business
Application
Process
Consultant
Management

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

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Test cases & Application
Process
Results Consultant
Management

BPM - Business
Application
Process
Consultant
Management

Development BPM - Business


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

BPM - Business Integration


Process Development
Management Consultant

BPM - Business Integration


Process Development
Management Consultant
BPM - Business Integration
Test cases &
Process Development
Results
Management Consultant

BPM - Business Integration


Process Development
Management Consultant

BPM - Business Integration


Process Development
Management Consultant

BPM - Business
Process
Management

BPM - Business
Application
Process
Consultant
Management

BPM - Business
Application
Process
Consultant
Management

Value Audit of VM - Value


Scope Management

Business
VM - Value
Consultant
Management

ISM - Test
Management

ISM - Test Application


Management Consultant
Test cases & ISM - Test Application
Results Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Application


Management Consultant

Solution TSM - Technical


Landscape Solution
Design Management

TSM - Technical
Technology
Solution
Consultant
Management
TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

Application
DM - Data Migration
Consultant

TSM - Technical
Application
Solution
Consultant
Management

_Milestone

PM - Project
Management

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Production CutOver - Cut Over


Cutover Plan Management
OCM -
Business
Organizational Project
Readiness
Change Manager
Approach
Management
OCM -
Organizational Project
Change Manager
Management

Application
DM - Data Migration
Consultant

CutOver - Cut Over Application


Management Consultant

CutOver - Cut Over Project


Management Manager

CutOver - Cut Over Project


Management Manager

Test Strategy ISM - Test


Plans & Results Management

ISM - Test Technology


Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Technology


Management Consultant
Data Migration
DM - Data Migration
Design / Plan

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant
Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

Test cases & Application


DM - Data Migration
Results Consultant

Test cases & Technology


DM - Data Migration
Results Architect

Testplans & ISM - Test


Results - UAT Management

ISM - Test Technology


Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Application


Management Consultant

Testplans &
ISM - Test Application
Results -
Management Consultant
Regression

ISM - Test Project


Management Manager
DA - Data Archiving

Technology
DA - Data Archiving
Architect

Application
DA - Data Archiving
Consultant

Application
DA - Data Archiving
Consultant

Application
DA - Data Archiving
Consultant

Solution TSM - Technical


Landscape Solution
Design Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

Application
DM - Data Migration
Consultant

Application
DM - Data Migration
Consultant

TSM - Technical
Application
Solution
Consultant
Management

Failover
TSM - Technical
Environment
Solution
Design, Setup
Management
and Test Results
TSM - Technical
Technology
Solution
Architect
Management

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

Test Plans & ISM - Test


Results Management

ISM - Test Technology


Management Consultant

ISM - Test Technology


Management Consultant

ISM - Test Application


Management Consultant
ISM - Test Application
Management Consultant
Test
ISM - Test Management
Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Technology


Management Consultant

TSM - Technical
SAP Going Live
Solution
Check
Management

TSM - Technical
Technology
Solution
Consultant
Management
System User
Roles and
Authorization
TSM - Technical
Administration
Solution
and
Management
System
Authentication
Management

TSM - Technical
Technology
Solution
Consultant
Management

Technical
TSM - Technical
Operations and
Solution
Handover
Management
Strategy

TSM - Technical
Technology
Solution
Consultant
Management

TSM - Technical
Technology
Solution
Consultant
Management

BPM - Business
Technology
Process
Consultant
Management

Delivery of
projects Results
PM - Project
Delivery
Management
Acceptance
Protocol

Project (phase)
PM - Project Project
Lessons Learned
Management Manager
(internal)
PM - Project Business
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

_Milestone

_Phase

PM - Project
Management

Project Schedule PM - Project Project


(incl. milestones) Management Manager

PM - Project Project
Management Manager
PM - Project
Management

Project
PM - Project Project
Management
Management Manager
Plan(s)

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Risk List (internal


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

Project
(Performance) PM - Project Project
Report (internal & Management Manager
external

OCM -
Organizational
Change
Management

Functional/Techni
cal Requirements OCM -
Business
and Production Organizational
Consultant
Support Change
Processes Management
Defined

Master Data
Support Application
DM - Data Migration
Processes Consultant
Established
ALM - Application
Business Process Technology
Lifecycle
Operation Consultant
Management

System ALM - Application


Technology
Administration Lifecycle
Consultant
and Control Management

Security / Role TSM - Technical


Technology
and Authorization Solution
Consultant
Management Management

ALM - Application
Transition to Technology
Lifecycle
Support Consultant
Management

Training - Training

Education
Training - Training
Coordinator

Education
Training - Training Consultant

Training Education
Training - Training
Evaluations Coordinator

End User OCM -


Education
Training Delivery Organizational
Consultant
and Readiness Change
Checklist Management

ISM - Test
Management

ISM - Test Technology


Management Consultant

ISM - Test Application


Management Consultant

ISM - Test Technology


Management Consultant
CutOver - Cut Over
Management

Testplans & CutOver - Cut Over Application


Results Management Consultant

Data Migration Application


DM - Data Migration
Design / Plan Consultant

Production CutOver - Cut Over Application


Cutover Plan Management Consultant

CutOver - Cut Over Application


Management Consultant

Readiness for CutOver - Cut Over Application


Cutover - Signoff Management Consultant

CutOver - Cut Over Application


Management Consultant

Production CutOver - Cut Over Project


Cutover Plan Management Manager

Solution Manager
Update, CutOver - Cut Over Technology
Solution Management Consultant
Documentation

PM - Project
Management

PM - Project Application
Management Consultant

PM - Project Project
Management Manager
PM - Project Project
Management Manager

Delivery of
projects Results
PM - Project
Delivery
Management
Acceptance
Protocol

Project (phase)
PM - Project Project
Lessons Learned
Management Manager
(internal)

PM - Project Business
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

_Milestone
_Phase

PM - Project
Management

Project Schedule PM - Project Project


(incl. milestones) Management Manager

PM - Project Project
Management Manager

PM - Project
Management

Project
PM - Project Project
Management
Management Manager
Plan(s)

PM - Project Project
Management Manager

PM - Project Project
Management Manager

Risk List (internal


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

Project
(Performance) PM - Project Project
Report (internal & Management Manager
external

Go-Live Training
Training - Training
Sessions
Education
Training - Training Consultant

Education
Training - Training Consultant

Education
Training - Training
Coordinator
OCM -
Education
Organizational
Consultant
Change
Management

TSM - Technical
Solution
Management

CutOver - Cut Over Technology


Management Consultant

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

CutOver - Cut Over Technology


Management Consultant

CutOver - Cut Over Project


Management Manager

CutOver - Cut Over Application


Management Consultant

CutOver - Cut Over Technology


Management Consultant

Transition to
Standard Support
ALM - Application
Processes, Technology
Lifecycle
System Consultant
Management
Administration
and Control

Solution Manager
ALM - Application
Update, Technology
Lifecycle
Solution Consultant
Management
Documentation
PM - Project Project
Management Manager

_Milestone

Delivery of
projects Results
PM - Project
Delivery
Management
Acceptance
Protocol

Project (phase)
PM - Project Project
Lessons Learned
Management Manager
(internal)

PM - Project Business
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

PM - Project Project
Management Manager

_Milestone
_Phase

PM - Project
Management

Business
PM - Project
Consultant
Management

PM - Project Project
Management Manager

ALM - Application
Lifecycle
Management

ALM - Application
Application
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

Test
ALM - Application
Management
Lifecycle
Consultant
Management
ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Application
Lifecycle
Consultant
Management
ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management

ALM - Application
Lifecycle
Management

ALM - Application
Technology
Lifecycle
Consultant
Management
WBS # WBS item title

1 Project Preparation

1 1 Project Initiation

1 1 1 Allocate Resources - hard booking with resource management

1 1 2 Prepare Team Onboarding Document

1 1 3 Communicate the delivery model and made mobility arrangements

1 2 Project Governance

1 2 1 Define Project Organization

1 2 2 Assign Roles and Responsibilities

1 2 3 Complete communication management plan

1 3 Project Charter

1 3 1 Prepare Project Charter Document

1 3 2 Identify Stakeholders

1 3 3 Obtain Project Charter Sign-off

1 4 Kick-Off Workshop

1 4 1 Prepare for Kickoff Meeting


1 4 2 Perform Kickoff Meeting

1 5 Scope Statement

1 5 1 Review Scope Statement with Customer

1 5 2 Refine Acceptance Criteria

1 6 Project Schedule and Budget

1 6 1 Develop delivery schedule and assign resources

1 6 2 Define Initial Release and Sprint schedule, Assign Resources

1 6 3 Include key workshops into the project schedule


1 6 4 Obtain Customer sign-off for project schedule

1 6 5 Establish Cost and Schedule baseline

1 7 Project Management Plan


1 7 1 Prepare Project Management Plan

1 8 Project and Operational Standards

1 8 1 Determine Solution Documentation Procedure

1 8 2 Determine Solution Implementation Procedure

1 8 3 Determine Test Management Procedure

1 8 4 Determine Change Control Management Procedure

1 9 Execution, Monitoring, and Controlling of Results

1 9 1 Direct and manage project execution

1 9 2 Monitor and control project activities

1 9 3 Manage Issues, Risks and Changes

1 9 4 Communicate Status and progress to project stakeholders

1 10 Organizational Change Management Roadmap


1 10 1 Prepare Organizational Change Management Roadmap

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

1 11 1 Prepare training strategy and plan document

1 12 Project Team Training

1 12 1 Conduct Solution Training and knowledge transfer

1 13 Business Process Map

1 13 1 Prepare Business Process Map

1 13 2 Validate and Complete business process map

1 14 Data Migration Approach and Strategy

1 14 1 Prepare Data Migration Scope and Requirements Document

1 14 2 Complete the Data Migration approach and strategy document

Technical Requirements and Design and Solution Landscape


1 15
Deployment Plan

1 15 1 Define Solution Landscape Concept

1 15 2 Define Solution Deployment Concept

1 16 Interface Inventory
1 16 1 Prepare Interface Inventory document

1 17 Initial Hardware Sizing Proposal

1 17 1 Complete HW sizing estimation for solution landscape

1 18 Project Support Tools and System Setup

1 18 1 Verify Technical System Requirements (frontend / 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


Install SAP Best Practices solution builder content add-on,
1 18 7
installation data and solution file

Setup of project logistics and infrastructure, including team


1 18 8
collaboration environment

Prepare authorization roles in the systems for the project team


1 18 9
(DEV)

1 19 Demo Environment

Pre-Assembled Rapid Deployment Solution installed in customer


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

Perform post activation tasks related to the Pre-Assembled Rapid


1 19 3
Deployment Solution

1 20 Phase Closure and Sign-Off phase Deliverables

1 20 1 Conduct Project Quality Gate

1 21 MILESTONE: Project Start to Design

2 Scope Validation

2 1 Phase Initiation

2 1 1 Allocate Resources and Update Project Schedule

2 2 Execution, Monitoring and Controlling Results

2 2 1 Update Project Management Plan

2 2 2 Direct and manage project execution


2 2 3 Conduct SCRUM Meetings

2 2 4 Monitor and control project activities

2 2 5 Manage Issues, Risks and Changes

2 2 6 Communicate Status and progress to project stakeholders

2 3 Stakeholder Analysis

2 3 1 Conduct classification of project Stakeholders

2 3 2 Identify Key Users

2 4 Change Impact Analysis


2 4 1 Validate organizational alignment approach

2 4 2 Establish Baseline of Current State

2 5 End User Training Strategy and Plan

2 5 1 Conduct Learning Needs Analysis

2 5 2 Develop Detailed End-User Training Plan

2 6 Project Team Training

2 6 1 Conduct Blueprint Ramp-up Training

2 7 Scope Validation

For <General Settings #1 - n> - Conduct Validation and Fit-gap


2 7 1
Analysis

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


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

2 7 4 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 User Access and Security

2 9 1 Authorization Requirements and Design

Pre-Assembled Rapid Deployment Solution Transfer into


2 10
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 Phase Closure and Sign-Off phase Deliverables

2 12 1 Conduct Project Quality Gate

2 13 MILESTONE: Design to Build

3 Realization

3 1 Phase Initiation

3 1 1 Allocate Resources and Update Project Schedule

3 2 Sprint Initiation (Iterative)

3 2 1 Conduct Sprint Planning Meeting (Iterative)

3 3 Execution, Monitoring and Controlling Results


3 3 1 Perform Sprint Execution Activities (Iterative)

3 3 2 Direct and manage project execution

3 3 3 Monitor and control project activities

3 3 4 Manage Issues, Risks and Changes

3 3 5 Communicate Status and progress to project stakeholders

3 3 6 Perform Scrum-Of-Scrums Meeting (Iterative)

3 4 Organizational Alignment

3 4 1 Execute Role Mapping and Transition Planning


3 5 Knowledge Transfer

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

For <SCOPE OPTION> - Perform Solution Walkthrough and


3 5 2
knowledge transfer to Key Users

3 5 3 Perform KT for delta scope

3 6 End User Training Delivery Enabled

3 6 1 Prepare End User Training Materials and Documentation

Configured General Settings and Organizational Structure (Cycle #1


3 7
- n)

3 7 1 Configure General Settings

3 7 2 Configure Organizational Structure

3 8 Configured Master Data Objects (Cycle #1 - n)

For <MASTER DATA OBJECT NAME> - Prepare and Load Master


3 8 1
Data

3 9 Core Configuration and Documentation - Process (Cycle #1 - n)

Complete Core Configuration, including documentation and test


3 9 1
cases

3 10 Delta Configuration - Process (Cycle #1 - n)

3 10 1 Complete Delta Configuration

3 10 2 Complete Delta Process Documentation

3 10 3 Complete Delta Process Test Cases

3 10 4 Execute Business Process Unit and String Test Cases

3 10 5 Perform defect resolution for Unit and String Test


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 Business Process Procedure

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

Execute Technical Installation of SAP Products for QAS


3 15 1
environment

3 15 2 Import Configuration and Development Objects to QAS Environment

3 15 3 Set up Role Assignment / Authorizations / Test Users in QAS


For <SCOPE OPTION> - Prepare and Load of Master Data into
3 15 4
QAS Environment
For <SCOPE OPTION> - Prepare and load transactional data into
3 15 5
QAS
3 15 6 Perform Manual Configuration Settings in QAS

3 16 MILESTONE: Build to Test

3 17 Preliminary Cutover plan

3 17 1 Prepare Preliminary Cutover plan

3 17 2 Refine Preliminary Cutover Plan

3 18 Approved Integration Test (Cycle #1 - n)

Prepare Integration Test Plan, including test of roles and


3 18 1
authorizations

3 18 2 Prepare and document Integration Test Case #1 - n

3 18 3 Execute Integration Test Case #1 - n

3 18 4 Perform defect resolution for Integration Test

3 18 5 Obtain Integration Test Results Sign-off

3 19 Legacy Data Migration (Cycle #1 - n)

3 19 1 Perform SAP Target Load Test


3 20 Approved User Acceptance Test (Cycle #1 - n)

3 20 1 For <SCOPE OPTION> - Prepare UA Test Plan

For <SCOPE OPTION> - Prepare and Document User Acceptance


3 20 2
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 Production Environment (PRD)

Execute Technical Installation of SAP Products for PRD


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

3 21 3 Import Configuration and Development Objects to PRD Environment

For <SCOPE OPTION> - Set up Role assignment / Authorizations /


3 21 4
Test Users in PRD
3 21 5 For <SCOPE OPTION> - Populate PRD with Test Master Data
For <SCOPE OPTION> - Prepare and Load master data into PRD
3 21 6
environment
For <SCOPE OPTION> - Import of System Fast-track Configuration
3 21 7
into PRD
For <SCOPE OPTION> - Perform Manual Configuration Settings in
3 21 8
PRD

3 22 System and Performance Test (Cycle #1 - n)

3 22 1 Prepare Performance Test Plan

3 22 2 Prepare Performance Test Cases

3 22 3 Perform Performance Test Defect Resolution

3 23 SAP Going Live Check


Perform SAP Going Live Check - Analysis Session and schedule the
3 23 1
Verification Session

3 24 Technical Operations and Handover Plan

3 24 1 Validate Support Center/Help Desk Staffing Strategy

3 24 2 Set-up Business Process Monitoring

3 25 Phase Closure and Sign-Off phase Deliverables

3 25 1 Conduct Project Quality Gate(s)

3 25 2 Obtain Customer Sign-Off for Phase Completion


3 26 MILESTONE: Test to Deployment

4 Final Preparation

4 1 Phase Initiation

4 1 1 Allocate Resources and Update Project Schedule


4 2 Execution, Monitoring and Controlling Results

4 2 1 Direct and manage project execution

4 2 2 Monitor and control project activities

4 2 3 Manage Issues, Risks and Changes

4 2 4 Communicate Status and progress to project stakeholders

4 3 Pre Go-Live End-User Training Delivery

4 3 1 Deliver End User training

4 4 Approved Technical System Tests

4 4 1 Execute Technical System Tests

4 5 Production Cutover

4 5 1 Conduct Data Quality Readiness Check

4 5 2 Finalize Cutover Plan

4 5 3 Perform Pre-Cutover Weekend Closing Activities

Final Check of Production Readiness and Sign-Off for transition to


4 5 4
Production

Perform Cutover Weekend Activities including Final Production Data


4 5 5
Load

4 5 6 Obtain Production Data Load Sign-off


4 5 7 Initiate Solution Manager Update - Solution Documentation

4 6 Phase Closure and Sign-Off phase Deliverables

4 6 1 Conduct Project Quality Gate

4 7 MILESTONE: Production System Live

5 Go Live Support

5 1 Phase Initiation

5 1 1 Allocate Resources and Update Project Schedule

5 2 Execution, Monitoring and Controlling Results

5 2 1 Monitor and control project activities

5 3 Post Go live End-User Training

5 3 1 For <SCOPE OPTION> - Prepare End-User Training

5 3 2 For <SCOPE OPTION> - Deliver End-User Training


5 4 SAP Going Live Check - Verification Session

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

5 5 Production Support After Go Live

5 5 1 Provide Post Go Live Support

5 6 MILESTONE: Deploy to Run

5 7 Improvement Roadmap

5 7 1 Perform Refinement & Improvement Planning Workshops

5 7 2 Document Improvement Roadmap

5 8 Project Closure and Sign-Off Project Deliverables

5 8 1 Conduct Knowledge Management Gate

5 8 2 Conduct Project Quality Gate

5 8 3 Resolve and close open issues

5 8 4 Finalize Project Closeout Report

5 8 5 Obtain Sign-off for Project Closure and Results Acceptance


6 Operate

6 1 Operations Maturity Assessment

Perform evaluation and assessment of operations capabilities,


6 1 1
including CoE operational set up

6 1 2 Prepare Maturity Assessment Report

6 2 Solution Documentation Optimized

6 2 1 Perform assessment of Solution Documentation set up

6 3 Solution Implementation Optimized

6 3 1 Perform assessment of Solution Implementation set up

6 4 Template Management Optimized

6 4 1 Perform assessment of Template Management set up

6 5 Test Management Optimized

6 5 1 Perform assessment of Test Management set up

6 6 Change Control Management Optimized

6 6 1 Perform assessment of Change Control Management set up


6 7 Application Incident Management Optimized

6 7 1 Perform assessment of Incident Management set up

6 8 Technical Operations Optimized

6 8 1 Perform assessment of Technical Operations set up

6 9 Business Process Operations Optimized

6 9 1 Perform assessment of Process Operations set up

6 10 Maintenance Management Optimized

6 10 1 Perform assessment of Maintenance Management set up

6 11 Upgrade Management Optimized

6 11 1 Perform assessment of Upgrade Management set up


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

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.

The purpose of this activity is to collect all input required for the project charter and document it into a
format suitable for both communication purpose as for formal sign-off purpose, if possible utilizing the
accelerator file(s) provided

The purpose of this activity is to ensure that the correct groupings of stakeholders have been identified for
the project.
The purpose of this activity is to achieve a formal sign-off of the project charter.

The purpose of this deliverable is to kick-off the project/phase and ensure that all needed information is
shared with the resources for a successful 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 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.

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 resources to the scheduled
activities and tasks.

The purpose of this task is to define a high level release plan, determine the length and number of sprints
per release. During this activity the project team needs to take into accounts business needs, project
objectives & goals, available technical environment, complexity of the solution, geographical and
organizational scope of the project and other aspects (like seasonality of customer's business). The
outcome of this task is high level release plan that includes key features targeted in each release and
number/duration of sprints (note that the sprint duration should be fixed for all project teams and should
not vary).

The purpose of this activity is to extract all planned workshops during the project/phase into a schedule
that facilitates workshop planning
Purpose of this task is to obtain customer approval (sign-off)
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 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 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 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 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 task is to prepare the training strategy and plan.

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

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 confirm that the access to the Cloud environment is possible via the customer
LAN
The purpose of this task is to validate and ensure a proper Solution Manager setup.

The purpose of this task is to confirm that the Solution Manager can connect to the SAP application in the
Cloud environement (Hybrid approach)

The purpose of this task is to ensure that the business process structure in SolMan is supporting the
solution documentation and all continued project activities in the coming phases (business process
management, value management, configuration & development, test, training and cut over).

The purpose of this task is to validate that customer has SAP Solution Builder installed and setup.
The purpose of this task is to install SAP Best Practices solution builder content add-on, installation data
and solution file

The objective of this task is to setup project logistics, systems and infrastructure that will support delivery
of the project. This may include setup of computers, setup of project team room, telephony, etc.

The purpose of this task is to prepare authorization roles in the systems for the project team

The purpose of the demo environment deliverable is to install a technical development-like system to be
used for demonstration and visualization purposes.

The purpose of this task is to installed the virtual Pre-Assembled Rapid Deployment Solution and make it
available in the system landscape of the customer.
The purpose of this task is to perform unit test of the activated pre-assembled RDS solution and to
confirm that relevant solution scope and business processes have been activated without issues.

The purpose of this task is to check that the SAP system is running correctly and to ensure that the
remote service connection is enabled.

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

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

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 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 as-is and future state to-be business process maps to
quantify the delta transition gap

The purpose of this task is to re-visit the stakeholder identification results, determine the detailed level of
change impacts for the identified stakeholder (groups) in order to create transparency about the
organizational and system changes.

The purpose of this task is to identify key users needed for the different areas (depending on the scope of
this project).

The purpose of the Change impact analysis deliverable is to ensure that the organizational and technical
changes in business processes have been identified 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 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:
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 solution validation / fit-gap analysis deliverable is to validate the predefined scenarios,
processes and enhancements; identify potential gaps between delivered product and customer
requirements. The deliverable only captures requirements for gaps. It follows an iterative approach.
Existing documentation and models can be altered, changes have to be marked and documented in
Solution Manager.

This task validates predefined general settings and that these are still relevant for the scope of the
implementation, such as organizational structures or customer or material masters, and to identify
potential gap between delivered product and customer requirements.esign a solution for these business
objects within the SAP solution. These objects are associated to processes and reflected in applications
so understanding these relationships is essential for overall integration and cross-process integrity.

This task validates predefined scenario solution documentation, identifies potential gap between delivered
product and customer requirements. Only requirements for gap are being captured. It follows an iterative
approach. Existing documentation and models can be altered, changes have to be marked and
documented in Solution Manager
This task validates predefined process solution documentation, identifies potential gap between delivered
product and customer requirements. Only requirements for gap are being captured. It follows an iterative
approach. Existing documentation and models can be altered, changes have to be marked and
documented in Solution Manager.

This task validates the pre-defined RICEFW Objects (reports, forms etc.). Additional customization and
enhancements should be kept to a minimum.

This purpose of this task is to analyze identified gaps and additional requirements and determine effort
(and duration) for the realization phase.

The purpose of the legacy data migration deliverables is to develop the designs, plans, and procedures to
support the migration of legacy data during the 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 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.

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.

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

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

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 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 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 task is to ensure consistent planning, execution and monitoring of sprint activities.
This includes:
Team Activities
The team performs their sprint tasks as to the sprint backlog, taking priority and done criteria into
account
The team attends the Daily Stand-up Meeting. The Daily Stand-up Meeting serves for information
exchange among the team members. It should not exceed 15 minutes and occurs same time same place
each day. After the meeting, the team updates the sprint backlog (what are remaining tasks and efforts).
For more information please refer to the Scrum Meeting Guidelines.
Scrum-of Scrum Meetings are conducted to coordinate the work between different scrum teams. Scrum
of Scrum meetings allow teams to discuss their work, focusing especially on areas of overlap and
integration. For more information please refer to the Scrum Meeting Guidelines
Product Owner Activities
Prepares ready-state user stories for the next sprint(s).
Aligns expectations and requirements with his business stakeholders.
Is available for answering questions from the team.
Scrum Master Activities
Makes sure that the Scrum process is followed (organizing and facilitating Daily Scrums, daily updates
of remaining tasks and effort by team, organization of sprint review and retrospective meetings)
Solves blocks and supports team, including escalation.
Ensures that management or others do not influence team.

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.

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 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 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 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 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 document
this in Solution Manager.

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

The objective of this task is to resolve any issues identified during the Unit and String Test. It is crucial
that the issues are re-tested by users that reported them (or designated re-testers) and that they are
confirmed.
The purpose of this deliverable is to accommodate all RDS or Service Specific enhancements, coded
assets, etc. Each asset will have separate line item in this structure

The purpose of this service specific <Asset Name> is to <explain purpose of the extension specific
task>.
Note: This task is a place holder for any tasks that are specific to extensions like reports, interfaces, etc.
that are delivered in the service or RDS

The purpose of this deliverable is to develop and test the RICEFW objects. 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 crucial
that the issues are re-tested by users that reported them (or designated re-testers) and that they are
confirmed.

The purpose of this task is to perform final code review of the development objects and confirm readiness
for transport into QAS.

The purpose of the Business Process Procedures deliverable is to provide the basis for end-user training,
end-user training documentation and test case creation. The procedures may also be used by security to
develop roles and authorizations.

The purpose of this task is to validate and complete Business Process Procedures from the blueprint
phase.
The purpose of this task is to validate and complete Business Process Procedures from the blueprint
phase.
The purpose of this deliverable is to provide evidence that the scenarios designed can be supported by
the solution implemented.
The purpose of this task is to identify and document applicable test case(s) for the scenario.
The purpose of this task is to perform scenario test.
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.

Purpose of this task is to obtain customer approval (sign-off)

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 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 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 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 executed in an iterative manner.

The purpose of this task is to define and document integration test cases, end-to-end customer business
process scenarios, according to the test plan. Test plans and test case documentation is stored in
Solution Manager.

The purpose of this task is to document the integration test case outlined in the integration test plan

The objective of this task is to perform the Integration test according to previously defined plan. During the
test all issues must be logged and documented in the system for traceability purpose.

The objective of this task is to resolve any issues identified during the Integration Test. It is crucial that the
issues are re-tested by users that reported them (or 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 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 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 them (or designated re-testers) and that they are
confirmed.

The purpose of this task is to execute the testing, document the results and obtain customer approval
(sign-off)

The purpose of the production infrastructure and environment design and setup deliverable is to install a
viable, correctly configured technical production 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).
The purpose of this task is to prepare master data required for all business 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.

The task defines and documents the identified test cases related to system and performance test.
Outcome is documented in a test plan.
The purpose of this task is to document the test case outlined in the test plan

The 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.
The service consiste of two sessions - Analysis and Verification, and includes:
- Verification of the technical capabilities of the production environment (sizing plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components and Plug-Ins

The purpose of the technical operations and handover strategy deliverable is to update refine two prior
deliverables from the Business Blueprint phase, and prepare 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.

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

Purpose of this task is to obtain customer approval (sign-off)


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.

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

This task will confirm that the productive system is ready for Go Live.

The purpose of this task is the loading of production data from legacy systems into the production
environment. Once all preparations and configurations on both the technical and application levels are
completed, the final productive solution can be set up and data loaded. The solution is live in a production
environment

Purpose of this task is to obtain customer approval (sign-off)


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

This milestone signifies formal transition to production environment. Production is up and running, cutover
sustainment activities, end-user on-boarding and support are under way.

The purpose of this phase is to provide support for the solution during the period immediately
following production cutover. Exceptional items such as additional production support,
exceptional business monitoring processes, and extraordinary technical support are planned and
executed in this phase. At the end of the designated extra-care period, sustaining production
support processes planned in final preparation and executed as part of go-live support become
the core support for continuous improvement in the ongoing solution.

The purpose of 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 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 resources are assigned to all scheduled project activities (and
tasks) and that work is progressing and deliverables are produced as expected.

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

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.

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 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 activity is to achieve a closure of all open project issues which is a prerequisite for the
final project closure.

The purpose of this activity is to document the results of the project, both regarding achieved objectives,
deliverables as well as adherence to schedule, costs and delivered value.

The purpose of this activity is to formally close the project by obtaining customer signatures on dedicated
deliverables/documents e.g. Project Quality Gate, Project Closeout Report
Solution operations are initially set up during the implementation project. The primary goal of this
phase is to further optimize and automate the operability of the solution. Operability is the ability
to maintain IT systems in a functioning and operating condition, guaranteeing systems availability
and required performance levels to support the execution of the 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

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

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 Template Management area.

Functional and performance testing of SAP-centric business processes to ensure validated system
behavior after software change events

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

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

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

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

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

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 Maintenance Management area.

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

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 Upgrade Management area.
Q-Gate Relevant Q-Gate Key Deliverable Work Stream

_Phase

PM - Project Management

PM - Project Management
Project Guideline (incl. Travel
Mandatory PM - Project Management
Guideline)

PM - Project Management

PM - Project Management

Steering Committee Definition,


Mandatory PM - Project Management
Org-Structure, Roles

PM - Project Management

PM - Project Management

Mandatory Project Charter PM - Project Management

PM - Project Management

OCM - Organizational Change


Management
PM - Project Management

Mandatory Phase Kick Off Meeting PM - Project Management

PM - Project Management
PM - Project Management

Mandatory Scope Statement Document PM - Project Management

PM - Project Management

PM - Project Management

PM - Project Management

Project Schedule (incl.


Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management
PM - Project Management
Project Budgetplan (internal &
Mandatory PM - Project Management
external)

Mandatory Project Management Plan(s) PM - Project Management


PM - Project Management

ALM - Application Lifecycle Management

Solution Manager Usage


guideline,
Mandatory ALM - Application Lifecycle Management
Business Process Modeling
Standards

Software System Configuration


Optional Standards, Enhancement and ALM - Application Lifecycle Management
Modification Standards

Optional Test Management Standards ISM - Test Management

Change Request and Transport


Optional TSM - Technical Solution Management
Management Standards (CTS)

PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external)

OCM - Organizational Change


Optional OCM Roadmap
Management
OCM - Organizational Change
Management

Training - Training

Project Team Training Plan &


Optional Training - Training
Schedule

Training - Training

Training - Training

Business Process Map


Mandatory BPM - Business Process Management
Business Process List

BPM - Business Process Management

BPM - Business Process Management

Data Migration Approach, Start


Optional DM - Data Migration
and Scope

DM - Data Migration

DM - Data Migration

Optional Solution Landscape Design TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management


TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

Optional Proj Support Tools & Sys Setup TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

BPM - Business Process Management


ISM - Test Management

BPM - Business Process Management

PM - Project Management

PM - Project Management

_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

Mandatory Project Management Plan(s) PM - Project Management

PM - Project Management
PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external

OCM - Organizational Change


Optional Stakeholder Analysis (Internal)
Management

OCM - Organizational Change


Management

OCM - Organizational Change


Management

Organizational Change OCM - Organizational Change


Optional
Management Plan Management
OCM - Organizational Change
Management

OCM - Organizational Change


Optional Business Readiness Approach
Management

Mandatory Training Project Plan Training - Training

Training - Training

End User Training and


Optional Training - Training
Documentation Developed

Training - Training

Training - Training

BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management


BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

Mandatory Data Migration Design / Plan DM - Data Migration

DM - Data Migration

DM - Data Migration

TSM - Technical Solution Management

Authorization Requirements and


Mandatory TSM - Technical Solution Management
Design

Mandatory Solution Landscape Design TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

Mandatory Test Strategy Plans & Results ISM - Test Management

DM - Data Migration

ISM - Test Management


Delivery of projects Results
Mandatory PM - Project Management
Delivery Acceptance Protocol

PM - Project Management

_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)
PM - Project Management

PM - Project Management

PM - Project Management
PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external

PM - Project Management

OCM - Organizational Change


Management

OCM - Organizational Change


Optional User Role Document
Management
Training - Training

Training - Training

Training - Training

Training - Training

End User Training and


Optional Training - Training
Documentation Developed

Training - Training

Solution Documentation (incl.


Mandatory Process list, Configuration, BPM - Business Process Management
Interfaces, Developments)

BPM - Business Process Management

BPM - Business Process Management

Solution Documentation (incl.


Mandatory Process list, Configuration, BPM - Business Process Management
Interfaces, Developments)

BPM - Business Process Management

Solution Documentation (incl.


Mandatory Process list, Configuration, BPM - Business Process Management
Interfaces, Developments)

BPM - Business Process Management

Solution Documentation (incl.


Mandatory Process list, Configuration, BPM - Business Process Management
Interfaces, Developments)

BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

Optional Test cases & Results BPM - Business Process Management

BPM - Business Process Management


Solution Documentation (incl.
Mandatory Process list, Configuration, BPM - Business Process Management
Interfaces, Developments)

BPM - Business Process Management

Development list(incl. RICEFW,


Mandatory BPM - Business Process Management
SOA, Migration)

BPM - Business Process Management

BPM - Business Process Management

Optional Test cases & Results BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

BPM - Business Process Management

ISM - Test Management

ISM - Test Management


Optional Test cases & Results ISM - Test Management

ISM - Test Management

ISM - Test Management

Mandatory Solution Landscape Design TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

DM - Data Migration
DM - Data Migration

TSM - Technical Solution Management

_Milestone

Mandatory Production Cutover Plan CutOver - Cut Over Management

CutOver - Cut Over Management

CutOver - Cut Over Management

Mandatory Test Strategy Plans & Results ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

Mandatory Data Migration Design / Plan DM - Data Migration

DM - Data Migration
Mandatory Testplans & Results - UAT ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

Mandatory Testplans & Results - Regression ISM - Test Management

ISM - Test Management

Mandatory Solution Landscape Design TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

TSM - Technical Solution Management

DM - Data Migration

DM - Data Migration

TSM - Technical Solution Management

TSM - Technical Solution Management

Mandatory Test Plans & Results ISM - Test Management

ISM - Test Management

ISM - Test Management

ISM - Test Management

Optional SAP Going Live Check TSM - Technical Solution Management


TSM - Technical Solution Management

Technical Operations and


Optional TSM - Technical Solution Management
Handover Strategy

TSM - Technical Solution Management

BPM - Business Process Management

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

PM - Project Management

PM - Project Management
_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)
PM - Project Management

PM - Project Management

PM - Project Management

Risk List (internal & external),


Mandatory Project Change log, Project PM - Project Management
Issues log

Project (Performance) Report


Mandatory PM - Project Management
(internal & external

Training - Training

Training - Training

ISM - Test Management

ISM - Test Management

CutOver - Cut Over Management

Mandatory Data Migration Design / Plan DM - Data Migration

Mandatory Production Cutover Plan CutOver - Cut Over Management

CutOver - Cut Over Management

Optional Readiness for Cutover - Signoff CutOver - Cut Over Management

CutOver - Cut Over Management

Mandatory Production Cutover Plan CutOver - Cut Over Management


Solution Manager Update,
Optional CutOver - Cut Over Management
Solution Documentation

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

PM - Project Management

_Milestone

_Phase

PM - Project Management
Project Schedule (incl.
Mandatory PM - Project Management
milestones)

PM - Project Management

PM - Project Management

Optional Go-Live Training Sessions Training - Training

Training - Training

Training - Training
TSM - Technical Solution Management

CutOver - Cut Over Management

Support Process Enabled,


Optional Governance Model for CutOver - Cut Over Management
Operations

CutOver - Cut Over Management

_Milestone

PM - Project Management

PM - Project Management

PM - Project Management

Delivery of projects Results


Mandatory PM - Project Management
Delivery Acceptance Protocol

Project (phase) Lessons Learned


Optional PM - Project Management
(internal)

PM - Project Management

PM - Project Management

PM - Project Management

PM - Project Management
_Phase

PM - Project Management

PM - Project Management

PM - Project Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management


ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management

ALM - Application Lifecycle Management


Accountable Role

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager
Project Manager

Business Consultant

Business Consultant

Test Management Consultant

Application Consultant

Project Manager

Project Manager

Project Manager

Project Manager
Business Consultant

Education Consultant

Education Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Solution Architect

Technology Architect
Technology Architect

Solution Architect

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant
Application Consultant

Application Consultant

Business Manager

Project Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Business Consultant

Education Consultant
Business Consultant

Business Consultant

Education Consultant

Education Consultant

Business Consultant

Application Consultant

Application Consultant
Application Consultant

Integration Development Consultant

Application Consultant

Application Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant

Technology Consultant
Business Manager

Project Manager

Project Manager
Application Consultant

Project Manager

Project Manager

Project Manager

Project Manager

Project Manager

Business Consultant
Application Consultant

Application Consultant

Application Consultant

Education Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant
Technology Consultant

Integration Development Consultant

Integration Development Consultant

Integration Development Consultant

Integration Development Consultant

Integration Development Consultant

Application Consultant

Application Consultant

Application Consultant
Application Consultant

Application Consultant

Application Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant
Application Consultant

Application Consultant

Application Consultant

Project Manager

Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Technology Consultant

Application Consultant
Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Project Manager

Technology Consultant

Technology Consultant

Technology Consultant

Technology Consultant

Application Consultant

Application Consultant

Technology Architect

Application Consultant

Technology Consultant

Application Consultant

Application Consultant
Technology Consultant

Technology Consultant

Technology Consultant

Business Manager

Project Manager

Project Manager
Project Manager

Project Manager

Project Manager

Project Manager

Education Consultant

Technology Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Application Consultant

Project Manager
Technology Consultant

Business Manager

Project Manager

Project Manager

Education Consultant

Education Consultant
Technology Consultant

Technology Consultant

Project Manager

Project Manager

Project Manager

Business Manager

Project Manager

Project Manager

Project Manager
Business Consultant

Project Manager

Application Consultant

Technology Consultant

Technology Consultant

Test Management Consultant

Technology Consultant
Technology Consultant

Technology Consultant

Application Consultant

Technology Consultant

Technology Consultant

You might also like