Project Preparation and Initiation WBS

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

management
1 1 2 Carry out Handover from Opportunity Management Phase
1 1 4 Obtain Project Manager Agreement
1 1 5 Prepare Team Onboarding Document
1 2 Project Governance
1 2 1 Define Project Organization
1 2 3 Assign Roles and Responsibilities
1 2 4 Complete communication management plan
1 3 Project Charter
1 3 1 Prepare Project Charter Document
1 3 2 Identify Stakeholders
1 3 4 Obtain Project Charter Sign-of

1 4 Kick-Of Workshop
1 4 1 Prepare for Kickof Meeting
00C000Public
1 4 2 Perform Kickof Meeting
1 5 Scope Statement
1 5 1 Document Customer Requirements
1 5 3 Review Scope Statement with Customer
1 5 6 Create Work Breakdown Structure and WBS Dictionary
1 5 7 Refine Acceptance Criteria
1 5 8 Obtain customer sign of for project scope

1 6 Project Schedule and Budget
1 6 1 Develop delivery schedule and assign resources
1 6 3 Include key workshops into the project schedule
1 6 4 Obtain Customer sign-of for project schedule

1 6 5 Establish Cost and Schedule baseline
1 7 Project Management Plan
00C000Public
1 7 1 Prepare Project Management Plan
1 7 2 Obtain Project Management Plan Sign-Of
1 8 Project and Operational Standards
1 8 1 Conduct ALM Roadmap
1 8 3 Determine Solution Documentation Procedure
1 8 4 Determine Innovation Management Procedure
1 8 5 Determine Template Management Procedure
1 8 6 Determine Test Management Procedure
1 8 7 Determine Change Control Management Procedure
1 8 8 Determine Application Incident Management Procedure
00C000Public
1 8 9 Determine Technical Operations
1 8 10 Determine Business Process Operations
1 8 11 Determine Maintenance Management
1 8 12 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
00C000Public
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
1 13 4 Demonstrate the business processes and predefined

options list for <SCOPE OPTION>
1 13 8 Complete Customer Blueprint and Configuration
Requirements Template
1 13 9 Validate and Complete business process map
1 14 Value Determination
1 14 1 Prepare Value Map
1 14 3 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.
00C000Public
1 16 Prepare Testing Policy
1 16 1 Prepare Testing Policy document
1 16 2 Obtain Customer Sign-Of 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
1 17 8 Conduct Risk Assessment for Data Migration and Prepare

Mitigation Plan
1 17 9 Complete the Data Migration approach and strategy

document
1 18 Technical Requirements and Design and Solution Landscape

Deployment Plan
1 18 1 Define Solution Landscape Concept
1 18 2 Define Solution Deployment Concept
1 19 Interface Inventory
1 19 1 Prepare Interface Inventory document
00C000Public
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 3 Verify Functional System Requirements
1 21 4 Check availability of SAP Solution Manager
1 21 5 Install or Upgrade SAP Solution Manager

1 21 7 Set up Business Process Hierarchy in SAP Solution Manager
1 21 10 Setup of project logistics and infrastructure, including team

collaboration environment
1 21 11 Install SAP GUI on project team computers

1 21 12 Test Remote Access and Establish OSS Connection (both GUI
and Web Access)
1 21 13 Prepare SAP Best Practice Activation
1 21 14 Execute Technical Installation of SAP Products (Pre-defined

solution Components)
1 21 15 Perform Installation check
1 21 18 Review installation check and knowledge transfer
1 21 19 Prepare authorization roles in the systems for the project

team (DEV)
1 21 20 Set up of testing tools
00C000Public
1 22 Phase Closure and Sign-Of 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-Of for Phase Completion

2 Business Blueprint
2 1 Phase Initiation
2 1 1 Allocate Resources and Update Project Schedule
2 2 Execution, Monitoring and Controlling Results
2 2 1 Update Project Management Plan
00C000Public
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
00C000Public
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 Solution Validation / Fit-Gap Analysis
2 9 1 Conduct Validation and Fit-gap Analysis - Scenario #1 - n
2 9 2 Conduct Validation and Fit-gap Analysis - Process #1 - n
2 9 3 Validate pre-defined RICEFW Objects (reports, forms etc.)
2 9 4 Determine Gap list and efort estimation
2 10 Business Solution Design for Business Objects
2 10 1 Define Business Organization Structure
00C000Public
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 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
00C000Public
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 17 Visualization
2 17 1 Conduct Visualizations
2 17 2 Prepare Initial Business Process Procedure document
2 19 Legacy Data Migration
2 19 1 Ensure Master Data Management Processes Ownership
2 19 2 Conduct Data Mapping workshops (master data for pre-

defined solutions)
2 19 3 Conduct Data Quality Assessment
2 19 4 Define Automated Data Migration Approach
2 19 5 Define Manual Data Migration Approach
2 19 6 Prepare Data Quality Plan
2 19 7 Prepare Data Security Design and plans
00C000Public
2 20 Legacy Data Archive
2 20 1 Prepare baseline framework for the legacy data archiving

solution
2 21 Technical Solution Design
2 21 1 Prepare technical infrastructure specification
2 22 User Access and Security
2 22 1 Authorization Requirements and Design
2 23 Development Environment (DEV)
2 23 1 Execute Technical Installation of SAP Products for DEV

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

DEV
2 23 9 Create master data in DEV environment - Master Data #1 - n
2 24 Testing Strategy
2 24 1 Prepare Test Strategy document
2 24 2 Define Test data approach and validated pre-defined master

data
00C000Public
2 24 3 Review and Validate Testing Strategy with customer
2 24 4 Obtain customer sign-of on Testing Strategy.

2 24 5 Initiate Performance Testing preparation activities
2 26 5 Conduct Design Review Service
2 26 6 Manage Fulfilled Contracts

3 Realization
00C000Public
3 4 Organizational Alignment
3 4 1 Execute Role Mapping and Transition Planning
3 4 2 Conduct Sounding Board/Pulse Checks
3 4 5 Refine and Execute Communication Plan

3 5 Educational Readiness Review
3 5 1 Prepare Educational Readiness Report
3 8 Knowledge Transfer
3 8 1 Prepare for Key User Knowledge Transfer for <SCOPE

OPTION>
00C000Public
3 8 2 Perform Solution Walkthrough and knowledge transfer to
Key Users for <SCOPE OPTION>
3 9 End User Training Delivery Enabled
3 9 1 Prepare End User Training Materials and Documentation
3 9 2 Set up Training Environment
3 9 3 Perform Training of the Trainers
3 9 4 Develop End User Training Schedule and Logistics plan
3 10 Configured General Settings and Organizational Structure
3 10 1 Configure General Settings
3 10 2 Configure Organizational Structure
3 11 Configured Master Data Objects #1 - n
3 11 1 Prepare and Load master data - Master Data Object

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

test cases
3 12 2 Prepare Unit Test Cases
3 12 3 Prepare String Test Cases
00C000Public
3 12 4 Execute Business Process Unit Test
3 12 5 Perform defect resolution for Business Process Unit Test
3 12 6 Execute Business Process String Test
3 12 7 Perform defect resolution for Process String Test
3 13 Delta Configuration - Process #1 - n
3 13 1 Complete Delta Configuration
3 13 5 Complete Delta Process Documentation
3 13 6 Complete Delta Process Test Cases
3 13 7 Execute Business Process Unit and String Test Cases
3 13 8 Perform defect resolution for Unit and String Test
3 15 Enhancement Development - RICEFW Object #1 - n
3 15 1 Develop RICEFW Object #1 - n
3 15 2 Document RICEFW Object #1 - n
3 15 3 Execute Test Cases - RICEFW Object #1 - n
3 15 4 Perform defect resolution for RICEFW Object(s) Test
3 15 5 Conduct Final Code Review
3 16 SOA / Composite Application Development #1 - n
3 16 1 Develop, document and test Enterprise Service #1 - n
00C000Public
3 16 2 Develop, document and test Composite and/or Mobile
Application #1 - n
3 16 3 Conduct Final Code Review for SOA / Composite Application
3 17 Business Process Procedure
3 17 1 Develop Business Process Procedure Document
3 17 2 Validate and Complete Business Process Procedure

Document
3 18 Value Audits
3 18 1 Perform Value Audit
3 19 Scenario Test #1 - n
3 19 1 Prepare Test Case - Scenario #1 - n
3 19 2 Execute Test Case - Scenario #1 - n
3 19 3 Resolve Issues for Scenario #1 - n
3 19 4 Obtain Customer Sign-of for Testing of Scenario #1 - n

3 20 Quality Assurance Environment (QAS)
3 20 1 Execute Technical Installation of SAP Products for QAS

environment
3 20 2 Execute Technical Upgrade of SAP Products for QAS
environment
3 20 3 Import Configuration and Development Objects to QAS
Environment
3 20 4 Set up Role Assignment / Authorizations / Test Users in QAS
3 20 5 Prepare and Load Master Data into QAS Environment for

<SCOPE OPTION>
3 20 8 Perform Manual Configuration Settings in QAS
3 23 Preliminary Cutover plan
3 23 1 Conduct Organizational Change Management Readiness

Check
00C000Public
3 23 2 Conduct Production Support Readiness Check
3 23 3 Conduct Master Data Process Governance Readiness Check
3 23 4 Prepare Preliminary Cutover plan
3 23 5 Review Preliminary Cutover Plan with customer
3 23 6 Refine Preliminary Cutover Plan
3 24 Approved Integration Test
3 24 1 Prepare Integration Test Plan, including test of roles and

authorizations
3 24 2 Prepare and document Integration Test Case #1 - n
3 24 3 Execute Integration Test Case #1 - n
3 24 4 Perform defect resolution for Integration Test
3 24 5 Obtain Integration Test Results Sign-of

3 25 1 Develop Data Migration Program Units
3 25 2 Execute and validate Manual Data Migration
3 25 3 Obtain Data Quality Reports
3 25 4 Perform SAP Target Load Test
3 25 5 Obtain Data Migration Test Results
00C000Public
3 25 6 Conduct Final Data Quality Assessment
3 26 Approved User Acceptance Test
3 26 1 Prepare UA Test Plan for <SCOPE OPTION>
3 26 2 Tool adaption and delta UAT training
3 26 3 Prepare and Document User Acceptance Test Cases for

<SCOPE OPTION>
3 26 4 Execute UA Test Plan for <SCOPE OPTION>
3 26 5 Perform UA Defect Resolution for <SCOPE OPTION>
3 26 6 Obtain UA Test Results Sign-of
3 27 SAP Data Archiving
3 27 1 Capture Legal and Business Retention Requirements
3 27 2 Prepare Data Archive Plan
3 27 3 Prepare Data Archive Storage Plan
3 27 4 Conduct Data Archive Implementation Test

3 28 Production Environment (PRD)
3 28 1 Execute Technical Installation of SAP Products for PRD

Environment
3 28 2 Execute Technical Upgrade of SAP Products for PRD
Environment
3 28 3 Import Configuration and Development Objects to PRD
Environment
3 28 4 Set up Role assignment / Authorizations / Test Users in PRD
for <SCOPE OPTION>
3 28 5 Populate PRD with Test Master Data for <SCOPE OPTION>
3 28 6 Prepare and Load master data into PRD environment for

<SCOPE OPTION>
3 28 9 Perform Manual Configuration Settings in PRD for <SCOPE
OPTION>
00C000Public
3 29 Failover Environment
3 29 1 Prepare Failover Environment Design and Plan
3 29 2 Set-up Failover Environment and Execute Identified

Scenarios
3 29 3 Obtain Failover Environment Test Results
3 30 System and Performance Test
3 30 1 Prepare System Test Plan
3 30 2 Prepare Performance Test Plan
3 30 3 Prepare System Test Cases

3 30 4 Prepare Performance Test Cases
3 30 5 Execute Performance Tests
3 30 6 Perform Performance Test Defect Resolution
3 30 7 Obtain Test Results Sign-of

3 31 SAP Going Live Check
3 31 1 Perform SAP Going Live Check - Analysis Session and

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

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

4 Final Preparation
00C000Public
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
00C000Public
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-of

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
00C000Public
4 6 4 Perform Pre-Cutover Weekend Closing Activities
4 6 5 Final Check of Production Readiness and Sign-Of for

transition to Production
4 6 6 Perform Cutover Weekend Activities including Final
Production Data Load
4 6 7 Obtain Production Data Load Sign-of
4 6 8 Initiate Solution Manager Update - Solution Documentation

5 Go Live Support
00C000Public
5 3 Knowledge Support Strategy
5 3 1 Define Mid-Term and Long-Term Knowledge Support

Strategy for Customer
5 4 Post Go live End-User Training
5 4 1 Prepare End-User Training for <SCOPE OPTION>
5 4 2 Deliver End-User Training for <SCOPE OPTION>
5 5 SAP Going Live Check - Verification Session
00C000Public
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-of
5 9 End User Acceptance Survey
5 9 1 Prepare and distribute Survey to EU
5 10 Project Closure and Sign-Of Project Deliverables
00C000Public
5 10 5 Resolve and close open issues
5 10 6 Finalize Project Closeout Report
5 10 8 Obtain Sign-of for Project Closure and Results Acceptance
6 Operate
6 1 Operations Maturity Assessment
6 1 1 Perform evaluation and assessment of operations

capabilities, including CoE operational set up
6 1 2 Prepare Maturity Assessment Report
6 2 Solution Documentation Optimized
6 2 1 Perform assessment of Solution Documentation set up
6 3 Solution Implementation Optimized
6 3 1 Perform assessment of Solution Implementation set up
6 4 Template Management Optimized
6 4 1 Perform assessment of Template Management set up
6 5 Test Management Optimized
00C000Public
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
00C000Public
6 11 Upgrade Management Optimized
6 11 1 Perform assessment of Upgrade Management set up
00C000Public
Q-Gate
Description Relevant
This phase provides initial planning and preparation for the project. Although each project has
its own unique objectives, scope, and priorities, the deliverables outlined below assist in
completing the initiation and planning steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that a new project exists.
It supports the decision to accept the project, align stakeholders such as clients, customers, and
SAP management around a project and its scope, provide updated information for planning, and
obtain a commitment to proceed. It ensures alignment between SAP, the 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 deliverable is to carry out a handover from the opportunity team to the Mandatory
delivery team.
The purpose of the project manager agreement is to define key performance indicators and the Mandatory
conditions for cooperation between the SAP Consulting Delivery Executive and the SAP project
manager.
The purpose of this activity is to prepare the onboarding package for external consultants from Mandatory
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 Mandatory
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 Mandatory
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-of 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-of of the project charter.
The purpose of this deliverable is to kick-of the project/phase and ensure that all needed Mandatory
information is shared with the resources for a successful project execution.
The purpose of this task is to prepare the kickof meeting which will helps ensure the involvement
of the team and other key resources and their commitment to the project schedule.
00C000Public
The purpose of this activity is to gather the whole project team, including all remotely involved
resources, to kick-of 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 Mandatory
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 Mandatory
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-of)

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 efort (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 Mandatory
scheduled activities and tasks.
The purpose of this activity is to extract all planned workshops during the project/phase into a
schedule that facilitates workshop planning
The purpose of this activity is to create project schedule and cost baseline against which tracking, Mandatory
change management and status reporting is done.
The purpose of the project management plan deliverable is to develop the project management Mandatory
plan and the subsidiary plans on the basis of the project scope defined in the project charter.
00C000Public
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-of purpose, if
possible utilizing the accelerator file(s) provided
The purpose of this activity is to achieve a formal sign-of 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 efective 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 Mandatory
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 is to determine the customers approach for the identification, adaptation Optional
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 Optional
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 Optional
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 ofers 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.
00C000Public
The purpose of this task is to determine the customers approach of monitoring, alerting, analyzing Optional
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 efectively 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 Mandatory
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 Mandatory
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 Optional
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
00C000Public
The purpose of this deliverable is to develop a comprehensive training strategy that provides all
team members with a phase-based learning path for acquiring the skills and knowledge needed to
complete the project successfully. This learning path leads to project readiness as well as
certification on the specific applications the team members will be using.
The purpose of this task is to prepare the training strategy and plan. Optional
The purpose of this deliverable is to provide an overview of the SAP software to be implemented
so that all project team members have an understanding of the SAP solution for their areas of
responsibility.
The purpose of this task is to train the involved project team in the SAP solutions expected to be
used and/or chosen for the project scope
The purpose of the business process map is to derive and agree on the scope for the start of the Mandatory
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 Optional
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.
00C000Public
The purpose of this deliverable is to outline key elements of the testing methodology that the
project will use as guiding principles going forward. This is should be aligned with the customers
"Enterprise" approach on how to conduct testing (Not to be updated over time)
The purpose of this task is to collect all required information needed for the Test Policy, and to
document it in a format suitable for communication.
The purpose of the data migration approach and Strategy deliverable is to capture and Optional
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 efort.
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-of
purpose.
The purpose of the technical requirements and design deliverable is to provide the project with a Optional
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.
00C000Public
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 Optional
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)
00C000Public
The purpose of the phase closure and sign-of 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 Optional
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 efectively 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 phase is to create the business blueprint, which is a detailed process-
oriented and technical documentation of the results gathered during requirements and design
workshops or based on pre-delivered solution or service description.
A blueprint consists of multiple documents illustrating how the company intends to run its
business using SAP solutions.
The purpose of the phase initiation deliverable is to formally recognize that a new project phase
starts.
The purpose of this task is to confirm resource availability for the particular phase. Mandatory
The purpose of this task is to ensure the involvement of the team and other key resources and
their commitment to the project schedule. The meeting is also used to examine the approach for
the specific project phase.
The purpose of this task is to update the project management plan and the subsidiary plans Mandatory
based on the changes agreed during the projects change management process.
00C000Public
The purpose of this task is to ensure that each contract is closed by verifying that all work Mandatory
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 Optional
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 diferent areas (depending on the
scope of this project).
The purpose of the Change impact analysis deliverable is to ensure that the organizational and Optional
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 Mandatory
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.
00C000Public
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 kickof 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 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
efort (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. Mandatory
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.
00C000Public
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 Mandatory
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-of 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-of
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 Optional
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.
00C000Public
The purpose of this deliverable is to specify and detail how to realize the solution, both Core Mandatory
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 Mandatory
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.
00C000Public
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 Mandatory
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 Mandatory
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.
00C000Public
The objective of this task is to communicate the testing strategy (functional and performance) to
the customer project team and validate it.
Purpose of this task is to start the requirements gathering process (e.g. KPI and benchmarks). This
activity is aligned with the documented overall performance test strategy and will continue until
the finalization of the performance test concept
The purpose of the phase closure and sign-of deliverable is to: Mandatory
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 ofers actionable risk
mitigation recommendations.
The purpose of this task is to ensure that each contract is closed by verifying that all work
accepted.
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
starts.
00C000Public
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 Optional
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.
00C000Public
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 Optional
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 Optional
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 Optional
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 Mandatory
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 Mandatory
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 Mandatory
configuration is implemented, tested and documented.
The purpose of this task is to implement the Core Configuration, write valid test cases and to
The purpose of this task is to prepare the test cases
00C000Public
The purpose of this task is to perform unit test for the configuration Optional
The objective of this task is to resolve any issues identified during the Business Process Unit Test. It
is crucial that the issues are re-tested by users that reported them (or designated re-testers) and
that they are confirmed.
The purpose of this task is to perform string test for the configuration Optional
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
The purpose of the Delta Configuration deliverable is to ensure that the configuration is Mandatory
implemented, tested and documented.
The purpose of this task is to implement the Delta Configuration, write valid test cases and to
The objective of this task is to develop process documentation for any changed processes or for
any new processes added to the standard.
The objective of this task is to develop process test cases for any changed processes or for any new
processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration Optional
The objective of this task is to resolve any issues identified during the Unit and String Test. It is
The purpose of this deliverable is to develop and test the RICEFW objects. Documentation to be Mandatory
stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the functional specification,
The purpose of this task is to document the RICEFW object information in a technical specification
and define the appropriate test case(s). Documentation is stored in Solution Manager.
The purpose of this task is to perform unit and string test of the developments. Optional
The objective of this task is to resolve any issues identified during the RICEFW object(s) Test. It is
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.
00C000Public
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. Optional
The objective of this task is to resolve any issues identified during the scenario testing. It is crucial
that the issues are re-tested by users that reported them (or designated re-testers) and that they
are confirmed.
The purpose of the quality assurance infrastructure and environment design and setup deliverable Mandatory
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 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.
The purpose of the preliminary cutover plan deliverable is to document the strategy, scope and Mandatory
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 Optional
over/transition
00C000Public
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 Mandatory
integration of SAP solutions with non-SAP applications and interfaces and can be executed in an
iterative manner.
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 the legacy data migration deliverable is to develop, implement, and test the data Mandatory
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 Mandatory
the accuracy and efficiency of the data migration solution.
00C000Public
The purpose of this task is to provide one final assessment at the end of the realization phase to Optional
report on the quality of the converted legacy data
User acceptance test (UAT) is the last test cycle of an SAP solution implementation and is an Mandatory
essential part of gaining end-user acceptance of the software system.
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
Purpose of this task is to execute the testing, document the results and obtain customer approval
(sign-of)
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 Mandatory
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 objective of this task is to perform any remaining manual configuration changes in the
production environment.
00C000Public
Setup of Availability and Continuity Management (ACM) Optional
The purpose of this task is to define the approach and plan for Availability and Continuity
Management.
The purpose of this task is to set and execute the identified failure scenarios.
The purpose of this task is to obtain the results from the failover scenario execution and
determine the appropriate mitigation actions for the test findings.
The purpose of planned Performance and System Test is to checks the entire system, consisting of
databases, applications servers, front ends, printers etc. The performance test measures the
throughput and response times of the system.
The task defines and documents the identified test cases related to system and performance test.
Outcome is documented in a test plan.
The task defines and documents the identified test cases related to system and performance test.
Outcome is documented in a test plan.
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 service is to support the start of production of an SAP Solution. During this Optional
service, SAP service engineers check the solution for potential risks and give recommendations
ensuring optimal performance and system availability for core business processes.
The SAP GoingLive Check consists 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 Optional
an efective 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 Optional
prior deliverables from the Business Blueprint phase, and prepare a strategy to hand of
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.
00C000Public
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.
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 ofers actionable risk
mitigation recommendations.
accepted.
The purpose of the final preparation phase is to finalize readiness of the solution and its
supporting tools and processes for production go live. This includes, but is not limited to, system
tests, end-user training, system management, and cutover activities (including data migration).
The phase deliverables also serve to enable the resolution of all crucial open issues. On
successful completion of this phase, the business is ready to run the live SAP software system.
starts.
00C000Public
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 Optional
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 Optional
an integrated environment.
00C000Public
This task provide a single defined support approach for monitoring and measuring the customers Optional
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 Optional
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 Optional
authorizations in their productive environment.
The purpose of this task is to extract the knowledge about the scope, customizations, and Optional
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 Optional
delivering the material
This task checks how prepared the people in the organization are with regards to the identified Optional
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 signof in order to exit
system testing.
The purpose of this task is to prepare and execute the system tests. The outcome/results should
be approved by the customer.
The objective of this task is to resolve issues identified during the system testing. Upon resolution
the issues need to be re-tested and confirmed by responsible testers.
The purpose of production cutover is to perform the cutover to the production software and go
live. At this point, the organizational, business, functional, technical, and system aspects of the
project are ready to be used in production.
The purpose of this task is to rehearse or simulate the cutover activities. During simulation, the Mandatory
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 Mandatory
Complete the Cut Over plan with results obtained from the Go Live simulations. Mandatory
00C000Public
The objective of this task is to perform all the cutover preparation activities remaining to be closed
prior to cutover weekend. The detailed cutover plan contains the complete listing of all pre-
cutover activities, their dependencies, owners, and timing.
This task will confirm that the productive system is ready for Go Live. Optional
The purpose of this task is the loading of production data from legacy systems into the production
environment. Once all preparations and configurations on both the technical and application
levels are completed, the final productive solution can be set up and data loaded. The solution is
live in a production environment
Purpose of this task is to obtain customer approval (sign-of) Mandatory
Purpose of this task is to hand over the finalized implementation project and it's content, and set Optional
up as a productive solution in SAP Solution Manager. This provides the basis for the follow up
activities in the Run Phase.
satisfaction
accepted.
The purpose of this phase is to provide support for the solution during the period immediately
following production cutover. Exceptional items such as additional production support,
exceptional business monitoring processes, and extraordinary technical support are planned and
executed in this phase. At the end of the designated extra-care period, sustaining production
support processes planned in final preparation and executed as part of go-live support become
the core support for continuous improvement in the ongoing solution.
starts.
00C000Public
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 Optional
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.
00C000Public
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.
This task ensures knowledge transfer regarding the scope, customizations, and business processes Optional
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 Optional
up as a productive solution in SAP Solution Manager. This provides the basis for the follow up
activities in the Operate Phase.
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.
satisfaction
00C000Public
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
Solution operations are initially set up during the implementation project. The primary goal of
this phase is to further optimize and automate the operability of the solution. Operability is the
ability to maintain IT systems in a functioning and operating condition, guaranteeing systems
availability and required performance levels to support the execution of the enterprises
business operations.
The Operations Maturity Assessment evaluates the SAP customer's support operations to
determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements for operations and to
define what aspects of the operations need to be adjusted, enhanced or implemented.
The report should detail assessment results and finding, including proposed actions for how to
bridge identified gaps.
Centrally document and relate business processes and technical information of SAP and non-SAP
Solutions ensuring transparency, efficient maintenance and collaboration
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Solution
Documentations area.
Represents the identification, adaptation and implementation of new and enhanced future-proof
business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical installation from
business innovation
Uses the SAP Solution Manager to implement the innovation in the system landscape
from the implementation project and determine if potential gaps exist for the Solution
Implementation area.
The template management approach allows customers with multi-site SAP installations to
efficiently manage their business processes across geographical distances from initial template
definition to template implementation and template optimization, for example as part of a global
rollout
from the implementation project and determine if potential gaps exist for the Template
Management area.
Functional and performance testing of SAP-centric business processes to ensure validated system
behavior after software change events
00C000Public
from the implementation project and determine if potential gaps exist for the Test Management
area.
Workflow-based management of business and technology-driven changes, with integrated project
management and synchronized deployment capabilities.
Standardized process leading to improved reliability of solution and minimized risk through
segregation of duties and transparency of changes
Efficient solution management all project and system information is saved in SAP Solution
Manager
from the implementation project and determine if potential gaps exist for the Change Control
Management area.
Enables a centralized and common incident and issue message processing in multiple organization
levels
Ofers a communication channel with all relevant stakeholders of an incident. The process includes
business user, SAP experts@customer, SAP Service&Support and Partner Support employees.
Is integrated in all ALM processes of SAP Solution Manager, in any SAP Business Suite solution and
could be connected to an Non-SAP Help Desk application
Includes follow up activities as knowledge research, root cause analysis or Change Management
from the implementation project and determine if potential gaps exist for the Incident
Management area.
Represents all capabilities for monitoring, alerting, analysis and administration of SAP solutions
Allows customers to reduce TCO by predefined content and centralized tools for all aspects of
operations in SAP Solution Manager
Provides End-to-End reporting functionality either out-of-the-box or individually created by
customers
from the implementation project and determine if potential gaps exist for the Technical
Operations area.
SAP Business Process Integration & Automation Management (BPIAM) comprises the most
important application related operations topics necessary to ensure the smooth and reliable flow
of the core business processes to meet a company's business requirements.
from the implementation project and determine if potential gaps exist for the Process Operations
area.
SAP Notes provide a solution for known issues. SAP Notes are usually applied upon request (e.g.
current incident in productive environment, information from SAP about potential issue (Hot
News, Security Notes)).
SAP Notes are collected and released as Support Packages. Support Packages are applied to SAP
solutions to comply with legal requirements or run on latest technology.
from the implementation project and determine if potential gaps exist for the Maintenance
Management area.
00C000Public
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 efectively 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.
from the implementation project and determine if potential gaps exist for the Upgrade
Management area.
00C000Public
Q-Gate Key Work Stream Accountable Role
Deliverable
_Phase
PM - Project Management
PM - Project Management Project Manager
Project Handover PM - Project Management Project Manager

Protocol
Project Manager PM - Project Management Project Manager

Agreement
Project Guideline PM - Project Management Project Manager

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

Committee
Definition, Org-
Structure, Roles
Project Charter PM - Project Management
OCM - Organizational Change Manag Project Manager

Phase Kick Of PM - Project Management
Meeting
00C000Public
Scope Statement PM - Project Management

Document
Work Breakdown PM - Project Management Project Manager

Structure (WBS)

Project Schedule PM - Project Management Project Manager

(incl. milestones)

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

Management
Plan(s)
00C000Public
ALM - Application Lifecycle Management
ALM - Application Lifecycle ManagemTechnology Architect
Solution Manager ALM - Application Lifecycle Managem Business Consultant

Usage guideline,
Business Process
Modeling
Standards
Software System ALM - Application Lifecycle Managem Business Consultant

Configuration
Standards,
Enhancement and
Modification
Standards
ALM - Application Lifecycle ManagemApplication Consultant
Test Management ISM - Test Management Test Management

Standards Consultant
Change Request TSM - Technical Solution ManagemenApplication Consultant

and Transport
Management
Standards (CTS)
TSM - Technical Solution ManagemenApplication Consultant
00C000Public
Post TSM - Technical Solution ManagemenTechnology Consultant
Implementation
Service and
Support
Risk List (internal PM - Project Management Project Manager

& external),
Project Change
log, Project Issues
log

(Performance)
Report (internal &
external)
OCM Roadmap OCM - Organizational Change Management
OCM - Organizational Change Manag Business Consultant
00C000Public
Training - Training
Project Team Training - Training Education Consultant

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

Map
Business Process
List
BPM - Business Process Management Application Consultant
Value Audit of VM - Value Management

Scope
VM - Value Management Business Consultant
BPM - Business Process Management
BPM - Business Process Management Business Consultant
00C000Public
ISM - Test Management
ISM - Test Management Technology Consultant
ISM - Test Management Project Manager

Data Migration DM - Data Migration
Approach, Start
and Scope
DM - Data Migration Application Consultant
DM - Data Migration Technology Architect
Solution TSM - Technical Solution Management

Landscape Design
TSM - Technical Solution ManagemenSolution Architect
TSM - Technical Solution ManagemenTechnology Architect
TSM - Technical Solution Management
00C000Public
TSM - Technical Solution ManagemenSolution Architect
Proj Support Tools TSM - Technical Solution Management

& Sys Setup
TSM - Technical Solution ManagemenTechnology Consultant


00C000Public
Project (phase) PM - Project Management Project Manager

Lessons Learned
(internal)
PM - Project Management Business Manager

_Phase

(incl. milestones)

Management
Plan(s)
00C000Public
& external),
Project Change
log, Project Issues
log

(Performance)
Report (internal &
external
Stakeholder OCM - Organizational Change Management

Analysis (Internal)
OCM - Organizational Change Manag Education Consultant
Organizational OCM - Organizational Change Management

Change
Management Plan
OCM - Organizational Change Management
Training Project Training - Training

Plan
Training - Training
00C000Public
Training - Training Business Consultant
Training - Training Instructor
Training - Training
BPM - Business Process Management Integration Development

Consultant
Business Blueprint BPM - Business Process Management Application Consultant

Documents(Org
Structure)
00C000Public
User Role BPM - Business Process Management Application Consultant

Document
Value Audit of VM - Value Management

Scope
00C000Public
Development BPM - Business Process Management
list(incl. RICEFW,
SOA, Migration)

Consultant

Consultant

Design / Plan
00C000Public
DA - Data Archiving
DA - Data Archiving Technology Architect
Authorization TSM - Technical Solution ManagemenTechnology Consultant

Requirements and
Design
Landscape Design
00C000Public

Delivery of PM - Project Management

projects Results
Delivery
Acceptance
Protocol

Lessons Learned
(internal)

_Phase
00C000Public
(incl. milestones)

Management
Plan(s)

& external),
Project Change
log, Project Issues
log

(Performance)
Report (internal &
external
User Role OCM - Organizational Change Manag Business Consultant

Document

Training - Training
Training - Training
Training - Training Application Consultant
00C000Public
Training - Training Application Consultant
End User Training Training - Training

and
Documentation
Developed
Training Training - Training Education Consultant

Environment
Population and
Testing
End User Training Training - Training Education Coordinator

Schedule and
Logistics
Solution BPM - Business Process Management

Documentation
(incl. Process list,
Configuration,
Interfaces,
Developments)

Documentation
Configuration,
Interfaces,
Developments)

Documentation
Configuration,
Interfaces,
Developments)

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

Results

Documentation
Configuration,
Interfaces,
Developments)

Results
Development BPM - Business Process Management

list(incl. RICEFW,
SOA, Migration)
Consultant

Consultant
Test cases & BPM - Business Process Management Integration Development

Results Consultant

Consultant

Consultant

Consultant
00C000Public
Consultant

Consultant
VM - Value Management
ISM - Test Management Application Consultant
Test cases & ISM - Test Management Application Consultant

Results

Landscape Design
Production CutOver - Cut Over Management

Cutover Plan
Business OCM - Organizational Change Manag Project Manager

Readiness
Approach
00C000Public
OCM - Organizational Change Manag Project Manager
CutOver - Cut Over Management Application Consultant
CutOver - Cut Over Management Project Manager
Test Strategy Plans ISM - Test Management

& Results

Design / Plan
Test cases & DM - Data Migration Application Consultant

Results
00C000Public
Test cases & DM - Data Migration Technology Architect
Results
Testplans & ISM - Test Management
Results - UAT
DA - Data Archiving
DA - Data Archiving Application Consultant

Landscape Design
00C000Public
Failover TSM - Technical Solution Management
Environment
Design, Setup and
Test Results

ISM - Test Management Test Management
Consultant

SAP Going Live TSM - Technical Solution Management
Check
System User Roles TSM - Technical Solution Management

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

Operations and
Handover Strategy
00C000Public
BPM - Business Process Management Technology Consultant
CutOver - Cut Over Management
CutOver - Cut Over Management Technology Architect

projects Results
Delivery
Acceptance
Protocol

Lessons Learned
(internal)

_Phase
00C000Public
(incl. milestones)

Management
Plan(s)

& external),
Project Change
log, Project Issues
log

(Performance)
Report (internal &
external
Functional/Techni OCM - Organizational Change Manag Business Consultant

cal Requirements
and Production
Support Processes
Defined
Master Data DM - Data Migration Application Consultant

Support Processes
Established
00C000Public
Business Process ALM - Application Lifecycle ManagemTechnology Consultant
Operation
System ALM - Application Lifecycle ManagemTechnology Consultant

Administration
and Control
Security / Role TSM - Technical Solution ManagemenTechnology Consultant
and Authorization
Management
Transition to ALM - Application Lifecycle ManagemTechnology Consultant

Support
Training - Training
Training - Training Education Coordinator
Training Training - Training Education Coordinator

Evaluations
End User Training OCM - Organizational Change Manag Education Consultant
Delivery and
Readiness
Checklist

Testplans & CutOver - Cut Over Management Application Consultant

Results
Data Migration DM - Data Migration Application Consultant

Design / Plan
Production CutOver - Cut Over Management Application Consultant
Cutover Plan
00C000Public
Readiness for CutOver - Cut Over Management Application Consultant

Cutover - Signof
Production CutOver - Cut Over Management Project Manager

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

projects Results
Delivery
Acceptance
Protocol

Lessons Learned
(internal)

_Phase
00C000Public
(incl. milestones)

Management
Plan(s)

& external),
Project Change
log, Project Issues
log

(Performance)
Report (internal &
external
Training - Training
Go-Live Training Training - Training

Sessions
OCM - Organizational Change Manag Education Consultant
00C000Public
CutOver - Cut Over Management Technology Consultant
Transition to ALM - Application Lifecycle ManagemTechnology Consultant

Standard Support
Processes
Solution Manager ALM - Application Lifecycle ManagemTechnology Consultant

Update,
Solution
Documentation

projects Results
Delivery
Acceptance
Protocol

Lessons Learned
(internal)
00C000Public
_Phase
PM - Project Management Business Consultant
ALM - Application Lifecycle ManagemTechnology Consultant
00C000Public
ALM - Application Lifecycle Managem Test Management
Consultant
00C000Public
00C000Public
WBS # WBS item title
1 Project Preparation
1 1 Project Initiation
1 1 1 Allocate Resources - hard booking with resource

management
1 1 2 Carry out Handover from Opportunity Management
Phase
1 1 4 Obtain Project Manager Agreement
1 1 5 Prepare Team Onboarding Document
1 2 Project Governance
1 2 2 Define Agile Project Organization and Roles
1 2 4 Complete communication management plan
1 3 Project Charter
1 3 1 Prepare Project Charter Document
1 3 2 Identify Stakeholders
1 3 3 Set Stakeholder Expectations for Agile Project
1 3 4 Obtain Project Charter Sign-of

1 4 Kick-Of Workshop
1 4 1 Prepare for Kickof Meeting
1 5 Scope Statement
1 5 1 Document Customer Requirements
00C000Public
1 5 3 Review Scope Statement with Customer
1 5 4 Determine Gap List and Efort Estimation
1 5 5 Communicate result of fit gap analysis including efort

estimates
1 5 6 Create Work Breakdown Structure and WBS Dictionary
1 5 7 Refine Acceptance Criteria
1 5 8 Obtain customer sign of for project scope

1 6 Project Schedule and Budget
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-of for project schedule

1 6 5 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-Of

1 8 Project and Operational Standards
00C000Public
1 8 2 Define and Set Up Agile Project Standards and ALM
Tools
1 8 3 Determine Solution Documentation Procedure
1 8 4 Determine Innovation Management Procedure
1 8 5 Determine Template Management Procedure
1 8 6 Determine Test Management Procedure
1 8 7 Determine Change Control Management Procedure
1 8 8 Determine Application Incident Management

Procedure
1 8 9 Determine Technical Operations
1 8 10 Determine Business Process Operations
1 8 11 Determine Maintenance Management
00C000Public
1 8 12 Determine Upgrade Management
1 9 Execution, Monitoring, and Controlling of Results
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 2 Conduct Agile Training for the Project Team
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
1 13 4 Demonstrate the business processes and predefined

options list for <SCOPE OPTION>
1 13 8 Complete Customer Blueprint and Configuration
Requirements Template
00C000Public
1 13 9 Validate and Complete business process map
1 14 Value Determination
1 14 1 Prepare Value Map
1 14 2 Define and Prioritize Epics
1 14 3 Validate and Complete Value Map
1 15 Business Scenario Design
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-Of 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
00C000Public
1 17 8 Conduct Risk Assessment for Data Migration and
Prepare Mitigation Plan
1 17 9 Complete the Data Migration approach and strategy

document
1 18 Technical Requirements and Design and Solution
Landscape Deployment Plan
1 18 1 Define Solution Landscape Concept

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

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

backend)
1 21 3 Verify Functional System Requirements
1 21 4 Check availability of SAP Solution Manager

1 21 5 Install or Upgrade SAP Solution Manager
1 21 7 Set up Business Process Hierarchy in SAP Solution
Manager
1 21 10 Setup of project logistics and infrastructure, including

team collaboration environment
1 21 11 Install SAP GUI on project team computers
1 21 12 Test Remote Access and Establish OSS Connection
(both GUI and Web Access)
00C000Public
1 21 19 Prepare authorization roles in the systems for the
project team (DEV)
1 21 20 Set up of testing tools

2 Business Blueprint
00C000Public
2 2 3 Conduct SCRUM Meetings

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
00C000Public
2 5 2 Define Communication strategy
2 6 End User Training Strategy and Plan
2 6 1 Conduct Learning Needs Analysis
2 6 2 Develop Detailed End-User Training Plan
2 7 1 Conduct Blueprint Ramp-up Training
2 7 2 Conduct Key User training

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

Environment
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
00C000Public
2 10 4 Define Logical Data Model
2 11 Detailed Design - Business Scenario #1 -n
2 11 2 Complete Business Scenario Design Document
2 11 3 Refine Epics and Update Product Backlog
2 12 Detailed Design - Business Process #1 - n
2 12 2 Complete Business Process Design Document
2 12 3 Demo or Visualize Standard Functionality
2 12 4 Define User Stories and Update Product Backlog
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
00C000Public
2 14 3 Define functional Design - RICEFW Object #1 - n
2 14 4 Define Functional Design - SOA & 3rd party

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

(Iterative)
2 17 Visualization
2 17 3 Capture Initial Visualization Requirements
2 17 4 Build Visualization (Iterative)
2 17 5 Demo Visualizations and Solicit Feedback (Iterative)
2 18 Baseline Build Sign-Of
2 18 1 Conduct Baseline Build and Visualizations Demo
00C000Public
2 18 2 Conduct Acceptance Testing of Baseline Build
2 18 3 Finalize Documentation of Baseline Build
2 18 4 Signof Baseline Build and Visualizations
2 19 1 Ensure Master Data Management Processes

Ownership
2 19 2 Conduct Data Mapping workshops (master data for
pre-defined solutions)
2 19 3 Conduct Data Quality Assessment
2 19 4 Define Automated Data Migration Approach
2 19 5 Define Manual Data Migration Approach
2 19 6 Prepare Data Quality Plan
2 19 7 Prepare Data Security Design and plans
2 20 Legacy Data Archive
2 20 1 Prepare baseline framework for the legacy data

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

Baseline Acceptance
2 22 User Access and Security
2 22 1 Authorization Requirements and Design
2 23 Development Environment (DEV)
2 23 1 Execute Technical Installation of SAP Products for DEV

environment
00C000Public
2 23 2 Execute Technical Upgrade of SAP Products for DEV
environment
2 23 3 Install Solution Documentation in Solution Manager
2 23 4 Execute Technical Installation of 3rd party products
2 23 5 Set up Role assignment / Authorizations / Test Users in

DEV
2 23 6 Perform Manual Configuration in DEV
2 23 8 Validate Role assignment / Authorizations / Test Users

in DEV
2 23 9 Create master data in DEV environment - Master Data
#1 - n
2 24 Testing Strategy
2 24 1 Prepare Test Strategy document
2 24 3 Review and Validate Testing Strategy with customer
2 24 4 Obtain customer sign-of on Testing Strategy.

2 25 Release and Sprint Plan
2 25 1 Update Product Backlog
2 25 2 Conduct Release Planning Meeting
2 25 3 Validate Release and Sprint Plan Against SOW
00C000Public
2 26 3 Execute Baseline Retrospective

3 Realization
3 2 Sprint Initiation (Iterative)

3 2 1 Conduct Sprint Planning Meeting (Iterative)
00C000Public
3 3 2 Perform Sprint Execution Activities (Iterative)

stakeholders
3 3 7 Perform Scrum-Of-Scrums Meeting (Iterative)
3 4 Organizational Alignment
3 4 1 Execute Role Mapping and Transition Planning
3 4 2 Conduct Sounding Board/Pulse Checks
3 4 3 Communicate Sprint Scope and Plan (Iterative)
3 4 4 Communicate Sprint Result (Iterative)
3 4 5 Refine and Execute Communication Plan
00C000Public
3 5 Educational Readiness Review
3 5 1 Prepare Educational Readiness Report
3 9 End User Training Delivery Enabled
3 9 1 Prepare End User Training Materials and

Documentation
3 9 2 Set up Training Environment
3 9 3 Perform Training of the Trainers
3 9 4 Develop End User Training Schedule and Logistics plan
3 10 Configured General Settings and Organizational

Structure
3 10 1 Configure General Settings
3 10 2 Configure Organizational Structure
3 11 Configured Master Data Objects #1 - n
3 11 1 Prepare and Load master data - Master Data Object

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

and test cases
3 12 2 Prepare Unit Test Cases
3 12 3 Prepare String Test Cases
3 12 4 Execute Business Process Unit Test
3 12 5 Perform defect resolution for Business Process Unit
Test
3 12 6 Execute Business Process String Test
3 12 7 Perform defect resolution for Process String Test
00C000Public
3 13 Delta Configuration - Process #1 - n
3 13 1 Complete Delta Configuration
3 13 5 Complete Delta Process Documentation
3 13 6 Complete Delta Process Test Cases
3 13 7 Execute Business Process Unit and String Test Cases
3 13 8 Perform defect resolution for Unit and String Test
3 15 Enhancement Development - RICEFW Object #1 - n
3 15 1 Develop RICEFW Object #1 - n
3 15 2 Document RICEFW Object #1 - n
3 15 3 Execute Test Cases - RICEFW Object #1 - n
3 15 4 Perform defect resolution for RICEFW Object(s) Test
3 15 5 Conduct Final Code Review
3 17 Business Process Procedure
3 17 1 Develop Business Process Procedure Document

3 17 2 Validate and Complete Business Process Procedure
Document
3 18 Value Audits
3 18 1 Perform Value Audit
3 19 Scenario Test #1 - n
3 19 1 Prepare Test Case - Scenario #1 - n

3 19 2 Execute Test Case - Scenario #1 - n
3 19 3 Resolve Issues for Scenario #1 - n
3 19 4 Obtain Customer Sign-of for Testing of Scenario #1 - n
3 20 Quality Assurance Environment (QAS)
00C000Public
3 20 1 Execute Technical Installation of SAP Products for QAS
environment
3 20 2 Execute Technical Upgrade of SAP Products for QAS
environment
3 20 3 Import Configuration and Development Objects to QAS
Environment
3 20 4 Set up Role Assignment / Authorizations / Test Users in

QAS
3 20 5 Prepare and Load Master Data into QAS Environment
for <SCOPE OPTION>
3 20 8 Perform Manual Configuration Settings in QAS
3 22 Sprint Closing
3 22 1 Conduct Sprint Review Meeting
3 22 2 Signof Sprint Results
3 22 3 Conduct Sprint Retrospective
3 23 Preliminary Cutover plan
3 23 1 Conduct Organizational Change Management

Readiness Check
3 23 2 Conduct Production Support Readiness Check
3 23 3 Conduct Master Data Process Governance Readiness

Check
3 23 4 Prepare Preliminary Cutover plan
3 23 5 Review Preliminary Cutover Plan with customer
3 23 6 Refine Preliminary Cutover Plan
3 24 Approved Integration Test
3 24 1 Prepare Integration Test Plan, including test of roles

and authorizations
00C000Public
3 24 2 Prepare and document Integration Test Case #1 - n
3 24 3 Execute Integration Test Case #1 - n
3 24 4 Perform defect resolution for Integration Test
3 24 5 Obtain Integration Test Results Sign-of

3 25 1 Develop Data Migration Program Units
3 25 2 Execute and validate Manual Data Migration
3 25 3 Obtain Data Quality Reports

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

<SCOPE OPTION>
3 26 4 Execute UA Test Plan for <SCOPE OPTION>
3 26 5 Perform UA Defect Resolution for <SCOPE OPTION>
3 26 6 Obtain UA Test Results Sign-of

3 27 SAP Data Archiving
3 27 1 Capture Legal and Business Retention Requirements
3 27 2 Prepare Data Archive Plan
3 27 3 Prepare Data Archive Storage Plan
3 27 4 Conduct Data Archive Implementation Test

3 28 Production Environment (PRD)
00C000Public
3 28 1 Execute Technical Installation of SAP Products for PRD
Environment
3 28 2 Execute Technical Upgrade of SAP Products for PRD
Environment
3 28 3 Import Configuration and Development Objects to PRD
Environment
3 28 4 Set up Role assignment / Authorizations / Test Users in
PRD for <SCOPE OPTION>
3 28 5 Populate PRD with Test Master Data for <SCOPE
OPTION>
3 28 6 Prepare and Load master data into PRD environment
for <SCOPE OPTION>
3 28 9 Perform Manual Configuration Settings in PRD for
<SCOPE OPTION>
3 29 Failover Environment
3 29 1 Prepare Failover Environment Design and Plan

3 29 2 Set-up Failover Environment and Execute Identified
Scenarios
3 29 3 Obtain Failover Environment Test Results
3 30 System and Performance Test
3 30 1 Prepare System Test Plan
3 30 2 Prepare Performance Test Plan
3 30 3 Prepare System Test Cases

3 30 4 Prepare Performance Test Cases
3 30 5 Execute Performance Tests
3 30 6 Perform Performance Test Defect Resolution
3 30 7 Obtain Test Results Sign-of

3 31 SAP Going Live Check
3 31 1 Perform SAP Going Live Check - Analysis Session and

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

Authorizations
00C000Public
3 33 Technical Operations and Handover Plan
3 33 1 Validate Support Center/Help Desk Staffing Strategy
3 33 2 Establish Support Processes
3 33 3 Set-up Business Process Monitoring
3 35 2 Conduct Project Quality Gate(s)

4 Final Preparation
00C000Public

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 5 Approved Technical System Tests
00C000Public
4 5 1 Execute Technical System Tests
4 5 2 Perform System Test Defect Resolution
4 5 3 Obtain System Test Results Sign-of

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

transition to Production
4 6 6 Perform Cutover Weekend Activities including Final
Production Data Load
4 6 7 Obtain Production Data Load Sign-of
4 6 8 Initiate Solution Manager Update - Solution

Documentation
4 7 Release Closing
4 7 1 Prepare Product Backlog for Next Release/Sprint
4 7 2 Conduct Release Retrospective
4 7 3 Update the Release and Sprint plan
00C000Public

5 Go Live Support

stakeholders
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>
00C000Public
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-of
5 10 Project Closure and Sign-Of Project Deliverables
5 10 5 Resolve and close open issues
5 10 6 Finalize Project Closeout Report
5 10 8 Obtain Sign-of for Project Closure and Results

Acceptance
00C000Public
6 Operate
6 1 Operations Maturity Assessment
6 1 1 Perform evaluation and assessment of operations

capabilities, including CoE operational set up
6 1 2 Prepare Maturity Assessment Report
6 2 Solution Documentation Optimized
6 2 1 Perform assessment of Solution Documentation set up
6 3 Solution Implementation Optimized
6 3 1 Perform assessment of Solution Implementation set up
6 4 Template Management Optimized
6 4 1 Perform assessment of Template Management set up
6 5 Test Management Optimized
6 5 1 Perform assessment of Test Management set up
6 6 Change Control Management Optimized
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
00C000Public
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
00C000Public
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 deliverable is to carry out a handover from the opportunity team to the delivery team.
The purpose of the project manager agreement is to define key performance indicators and the conditions for cooperation
between the SAP Consulting Delivery Executive and the SAP project manager.
The purpose of this activity is to prepare the onboarding package for external consultants from SAP and partner companies.
The purpose of this deliverable is to ensure that an efficient management framework is in place for successful project
execution.
The purpose of this task is to determine the structure and composition of agile teams in order to optimally setup the
project organization in line with agile principles. It is required to setup agile teams as cross functional groups that consist of
SCRUM master, Product Owner and team members. Team size should be 7 +/- 2 members. The cross-functional team needs
to be composed of business analyst, functional experts, technical experts and testers required to fully implement feature in
iteration.
The purpose of this task is to complete the communications management plan. This document outlines the processes
required to ensure timely generation, distribution, storage, and retrieval of project information.
The purpose of this deliverable is to clearly and explicitly define the objectives of the proposed project, analyze all possible
benefits and quantify benefits in financial terms. This information and supporting documents align key stakeholders around
the strategic intent of the project.
The purpose of this activity is to collect all input required for the project charter and document it into a format suitable for
both communication purpose as for formal sign-of purpose, if possible utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the correct groupings of stakeholders have been identified for the project.
The purpose of this task is to build agile awareness of key stakeholders, secure commitment to adopt standard SAP
functionality where possible. It is recommended to conduct informal and formal meetings to set the expectations and
confirm the project approach with key project stakeholders.
The purpose of this activity is to achieve a formal sign-of of the project charter.
The purpose of this deliverable is to kick-of 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 kickof 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-of 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
00C000Public
The objective of this task is to review the scope statement document with the customer project manager and key
stakeholders in order to confirm the scope and obtain approval.
The purpose of this task is to determine all gaps for customer solution, document them formally and estimate efort to
cover the identified gaps.
The objective of this task is to present the results of fit gap analysis to customer including the efort estimates to cover the
identified gaps as part of the project/service delivery.
The purpose of this task is to create the work breakdown structure (WBS) for the project, which is a deliverable-oriented,
hierarchical decomposition of the work to be executed by the project team to complete the project. It is the basis for the
organization and coordination of the project. A WBS consists of WBS elements that describe project tasks and subtasks to
perform within a defined time period.
The purpose of this activity is to clearly define the acceptance criteria against which project deliverables and results are
measured that have been listed in the Scope Statement. These should also be updated in the Project Quality Gate
Scorecard. In the context of Agile projects this translates to the definition of Done for the backlog items that are being
delivered in the project.

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

Deliverables and tasks for the current phase
Estimated efort (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, available
technical environment, complexity of the solution, geographical and organizational scope of the project and other aspects
(like seasonality of customer's business). The outcome of this task is high level release plan that includes key features
targeted in each release and number/duration of sprints (note that the sprint duration should be fixed for all project teams
and should not vary).
The purpose of this activity is to extract all planned workshops during the project/phase into a schedule that facilitates
workshop planning
The purpose of this activity is to create project schedule and cost baseline against which tracking, change management and
status reporting is done.
The purpose of the project management plan deliverable is to develop the project management plan and the subsidiary
plans on the basis of the project scope defined in the project charter.
The purpose of this activity is to collect input needed for the project management plan and document it in a format
suitable for both communication purpose as for formal sign-of purpose, if possible utilizing the accelerator file(s) provided
The purpose of this activity is to achieve a formal sign-of 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 efective 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.
00C000Public
The purpose of this task is to define and set up SCRUM standards and tools, such as SCRUM board, burn-down chart,
product backlog template and retrospective template. Organization of daily stand-up meetings, scrum-of-scrum-,
release/sprint planning and retrospective meetings. At this time the project also needs to prepare definition of Ready and
definition of Done for each critical step in the iteration. At minimum the team needs to prepare and agree on definition of
Ready and Done for following:
* Ready for Build (e.g. backlog item has proper size, it is clearly defined and understood, test procedure is defined, etc.)
* Ready for Demo (e.g. backlog item is fully developed and unit tested)
* Ready for Integration Test (e.g. backlog item integration test is defined (automated), test data is ready)
* Ready for Release (e.g. backlog item user level documentation is complete, ALM Solution Documentation is ready, Feature
passed Integration Test)
Note that definition of Ready for one step in the implementation process == definition of done of the previous step. Using
clear definition of Ready and Done is critical for SCRUM based implementations.
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 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 ofers 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)).
00C000Public
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 efectively 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 educate project team on Agile implementation approach, principles and techniques.
The purpose of the business process map is to derive and agree on the scope for the start of the business blueprint phase.
During blueprinting, the process map builds the foundation for the process hierarchy a decomposition of the process
design which is reflected as scenarios, processes, and process steps in SAP Solution Manager.
The purpose of this task is to complete the Business Process Map with the content reflecting the process scope of the
project
The purpose of this task is to ensure that a proper environment is available for the options selection workshops
The purpose of this task is to prepare the scope document with the pre-defined content according to the SOW and solution
documentation
The purpose of this task is to demonstrate available options related the selected processes in scope
The goal of this task is to complete customer blueprint document based on interviews and assessment sessions. The
document details the options customer selected from the pre-defined solution, all modifications and details the
configuration requirements of the solution.
00C000Public
Validate and Complete Business Process Map with pre-defined content depending on delivery model (Industrialized and/or
Assemble to Order process content).
The purpose of Value Determination is to ensure the alignment of the business case value drivers with key process changes
and functionality by establishing a value tracking framework and identifying business stakeholders
The purpose of this task is to review the project business case, map key value drivers to process changes, develop the value
tracking framework (KPI's and PPI's), identify value enablers, as well as assign business accountability for value realization.
The purpose of this task is for the Product Owner to prepare the initial product backlog which consists of the following
elements:
Vision and Business Case: Why do we want to do this? What is the value? What are current pain points?
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 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.
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 efort.
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.
00C000Public
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-of 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.
00C000Public
The purpose of this task is to prepare authorization roles in the systems for the project team
The purpose of this task is the initial set up of all relevant testing tools (the actual configuration will happen during Business
Blueprint)
Ensure that all required deliverables from this phase and the project are complete and accurate, and close any
outstanding issues
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
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 efectively 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 phase is to create the business blueprint, which is a detailed process-oriented and technical
documentation of the results gathered during requirements and design workshops or based on pre-delivered solution or
service description.
A blueprint consists of multiple documents illustrating how the company intends to run its business using SAP solutions.
The purpose of the phase initiation deliverable is to formally recognize that a new project phase starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this task is to ensure the involvement of the team and other key resources and their commitment to the
project schedule. The meeting is also used to examine the approach for the specific project phase.
The purpose of this task is to update the project management plan and the subsidiary plans based on the changes agreed
during the projects change management process.
00C000Public
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 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 diferent 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.
00C000Public
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 kickof 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 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.
00C000Public
The purpose of this task is to define a logical data model for master or transactional data relevant to the implementation
scope across the application landscape, including both legacy and SAP components.
This will help manage the data relationships and align interfaces correctly.
The purpose of the Detailed Design - Business Scenarios deliverable is the continuation of process decomposition started
in project preparation. This includes documentation of requirements, solution design for the scenarios and processes. This
information is populated in the business process hierarchy in SAP Solution Manager.
The purpose of this task is to continue collecting input and finalize the Scenario Design Document, in a format suitable for
both communication purpose as well as for formal sign-of purpose. The documented business scenario provides an
understanding of the essential processes at the scenario level (PL1-2). It also builds the foundation for the business
blueprint phase where process levels 35 are defined.
The purpose of this task is for the Product Owner team to decompose the initial product backlog EPICS into more granular
backlog items that the SCRUM teams can design, develop and deliver in the sprint. The Product Backlog which consists of
the following elements:
Vision and Business Case: Why do we want to do this? What is the value? What are current pain points?
Detailed Business Process scope: What are the business scenarios and processes (down to level 3) to be implemented?
Who will work with the processes and what are their primary business requirements? This will be used as input for the
definition of the user stories.
Priority of each backlog item
Estimated size and efort (the efort is estimated by the SCRUM team not the PO team)
Business Value
How to test the backlog item upon completion (e.g. definition of done for the feature)
The purpose of this deliverable is to design, in detail, the to-be business process down to activity level (PL 3-5) and to
describe gaps where the standard solution does not cover all required functionalities.
The purpose of this task is to continue collecting input and finalize the Business Process Design Document, in a format
suitable for both communication purpose as well as for formal sign-of 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 this task is to capture all identified delta requirements from the demo / visualization sessions in the product
backlog. The requirements are captured in form of user stories that define the requirement from end-user perspective,
provide details on how to test the feature when it is completed, priority of the backlog item and business value. It is
responsibility of Product Owner team to maintain the product backlog and detail the user stories so they are understood by
the SCRUM team.
The purpose of Value Realization is to establish the sustainable mechanisms to monitor and controls the predefined KPI's
and PPI's of the to-be process and/or process changes.
The purpose of this task is to design the Value Dashboard by specifying the KPI's and PPI's and how these are monitored
and controlled during project execution and post Go-Live.
The purpose of this deliverable is to specify and detail how to realize the solution, both Core Configuration and identified
gaps and core enhancements needed to complement standard functionality, in order to fulfill business requirements. These
RICEFW objects are based on process requirements, and they are specified in business process and solution design
documents.
The purpose of this task is to complete the documentation for identified core configuration objects related to business
processes.
The purpose of this task is to complete the documentation for additionally identified configuration objects related to
business processes.
00C000Public
The purpose of this task is to complete the documentation for identified RICEFW objects.
These objects are classified as:
Reports that have to be designed or adjusted
Interfaces that need to be developed
Conversions (mostly related to master data)
Enhancements that need to be performed
Forms for print-out or other purposes
Workflows that need to be implemented or designed
The purpose of this task is to prepare functional design document for all SOA and 3rd party applications / solution
enhancements or extensions.
The purpose of Baseline Build Plan is to define plan to setup fully functional environment to demonstrate the standard
functionality of the SAP solution to the customer product owner team, key users and stakeholders.
The purpose of this task is to determine which user stories will be built in the system and which ones will be visualized. The
decision process is based on customer requirements, understanding of the solution, complexity of the setup and availability
of proper visualization tools. Result of this activity is prioritized list of features that will be built in the system and list of
features that will be visualized.
The purpose of this task is to define plan for building the baseline build system and visualizations that will be used for demo
of the solution to the product owner team and key users. The plan may include multiple sprints depending on the size and
complexity of the baseline build. Teams may also choose to conduct the baseline build as one sprint. The SCRUM meetings
should be already in place and followed during the baseline build to establish regular routine and cadence for the team.
The purpose of Baseline Build is to setup fully functional environment to demonstrate the standard functionality of the SAP
solution to the customer product owner team, key users and stakeholders. The results of the demo is either acceptance of
standard feature or new delta requirement that is captured in the form of user story in the product backlog.
The purpose of this task is to build the baseline functionality defined in the baseline user story. This is conducted in
iterative fashion through out the baseline build. The outcome of this task is fully functional baseline build of user story that
is unit tested and ready for demo to the product owner and key users.
The purpose of this task is to demo the baseline build feature (user story) to the key users and product owner team to
obtain acceptance or solicit input for delta requirement.
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 demo is conducted in iterations that correspond to the cadence of sprints chosen for
the baseline build during the Baseline Build Planning session.
The purpose of the visualizations deliverable is to ensure that the defined processes are exemplified and easier to
understand and judge by the project team members, key users and stakeholders.
The purpose of this task is to initiate the work to document the visualization requirements as part of the business process
requirements documentation.
The purpose of this task is to create visualization of the functionality as defined in the baseline user story. This task is
conducted in iterative fashion through out the baseline build. The outcome of this task is visualization of the baseline build
user story that is ready for demo to the product owner and key users.
The purpose of this task is to demo the baseline build visualization to the key users and product owner team to obtain
acceptance or solicit input for delta requirement.
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 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-of for the baseline build (and visualizations) and product backlog
prior to proceeding to the Realization phase.
The purpose of this task is to demo the baseline build functionality and visualizations to the key users and product owner
team along with the product backlog to obtain acceptance of the baseline build and product backlog.
The results of the demo is either acceptance of standard feature or in exceptional cases new delta requirement that is
captured in the form of user story in the product backlog. This demo is conducted at the end of the Baseline Build to serve
as an input to formal sign-of for the baseline build.
00C000Public
The purpose of this task is for the key users and product owner team to conduct acceptance test of the features built in the
baseline build. This may also include walk-throughs of the visualizations for features that have not been fully built in the
system.
The purpose of this task is to complete documentation of the baseline build and capture it in SAP Solution Manager. In
particular this pertains to configuration documents, test cases, test scripts, visualizations, etc. as defined in the project
documentation standards defined in previous phase.
The purpose of this task is to formally signof the baseline build, visualizations and product backlog. This signals to the
project team that they can proceed to the next phase to iteratively build the features defined in product backlog.
The purpose of the legacy data migration deliverables is to develop the designs, plans, and procedures to support the
migration of legacy data during the implementation of the SAP applications.
The purpose of this task is to ensure that defined processes and procedures needed to ensure correct quality and handling
of master data are operational in the organization.
This task ensures that provided master data for Assemble to order and/or Industrialized content, can be utilized by the
project.
The purpose of this task is to conduct a detailed analysis of legacy data in order to determine:
The availability and quality of existing data to support the SAP applications to be implemented
The complexities and risks associated with the data and migration process
The purpose of this task is to design the specific architecture, programs, processes, and tasks required to support the
extraction, validation, harmonization, enrichment, and cleansing of the legacy data.
The purpose of Manual Data Migration design is to develop the approach for manually bringing legacy data into the SAP
database when automated programs are not available or the data volume does not justify the investment in developing
such programs.
The purpose of the data quality plan is to define the metrics that track and monitor data quality during the data migration
process.
The purpose of data Security Design is to identify and develop the necessary architectural designs and plans to support the
security requirements.
The purpose of legacy data archive is to make legacy master data not considered currently active available for reference in a
format compatible with the master data formats of the SAP solution.
The purpose of this task is to establish the framework for legacy data archiving, meaning the planning for usage of legacy-
data archive objects, the legacy archive specifications, and data retention rules for master-data archive objects.
The purpose of the Technical Solution Design deliverable is to provide a detailed technical and integration design of the
solution to be implemented, accounting for all decisions made during the Business Blueprint phase including business
process definitions, integration with external systems, and physical server deployment.
The purpose of this task is to complete the technical infrastructure specification which provides a technical description of
the entire technology landscape from a physical standpoint, showing where each of the SAP and non-SAP systems are
installed, and the physical or virtual servers assigned to each system along with their specifications
The purpose of this task is to define system environment that will be used for the baseline build. At minimum the
environment needs to have two systems Development and Quality Assurance. It is recommended to also provide team with
Sandbox environment where they can experiment with the functionality during the baseline build.
The purpose of this deliverable is to ensure proper set up of a Roles and Authorizations procedure and approach for the
project.
The purpose of this task is to document the authorization requirements at the level of business scenario and process, to
evaluate chosen authorizations concepts against SAP standards and to determine a feasible implementation approach.
The purpose of the development environment deliverable is to install a viable, correctly configured technical development
environment that is available for use by the project team to begin the realization phase.
00C000Public
The purpose of this task is to upgrade SAP components needed for the realization of project scope.
This task ensures that all solution documentation is made available for the project team. Preferably the repository for this
should be Solution Manager.
This task deals with the installation of 3rd party products needed to realize scope of the project.
The purpose of this task is to set up users in the development environment.
The objective of this task is to perform any remaining manual configuration changes in the Development environment.
The objective of this task is to validate the assignment of user role profiles / authorizations to the test users in the
development landscape.
Prepare master data required for a business process
The purpose of this deliverable is to create project related test framework, which gets content input from the existing Test
Policy (1.16.), to build a central foundation around the taken approach (e.g. Test Approach and Methodology, Test
Standards and Guidelines, Test Case Development, Defect Management, Reporting and Analysis, Roles and Responsibilities)
on functional testing (unit-, string-, integration-, scenario-, user acceptance, regression testing etc.) and performance
testing. The actual test strategy documentation for functional testing and performance testing have to be separated.
The objective of this task is to create a centralized document for functional- and performance testing, which incorporates
standard and procedures which will be used for the detailed test plan preparation / documentation.
The objective of this task is to communicate the testing strategy (functional and performance) to the customer project team
and validate it.
The purpose of this deliverable is to refine the Initial Release Plan that was defined earlier. At this time the team also
defined sprint plan for the first few iterations.
The purpose of this task is to refine the Product Backlog with vital information required for release and sprint planning
activities. The Product Owner Team has responsibility to refine the user stories so they are clearly understood by the
SCRUM teams. Each user story needs to have clear definition of the requirement in the language of the customer, defined
test criteria and assigned business value.
The purpose of this task is to conduct release planning meeting to define scope of product releases based on the prioritized
product backlog. The meeting is lead by Product Owner and its objective is to define scope of the first release and outline
key features slated for follow-on releases.
The purpose of this task is to review the release and sprint plans against the statement of work for the project. The
objective of this task is to identify any new features that have been surfaced during the baseline build that may not be part
of the original scope and may require amendment of SOW or Change Request. This task is the responsibility of SAP Project
Manager and Chief Product Owner/Sponsor from the customer side.

outstanding issues
00C000Public
The purpose of this task is to conduct retrospective meeting with the SCRUM team to identify potential improvements of
the SCRUM process. The objective of this task is to serve as continuous improvement mechanism for the team to adjust to
changing project environment and needs. The team will select one or two key improvements to implement in the next
iteration and handles them as user stories that are added to the product backlog, prioritized and tracked along with other
user stories.
The purpose of this task is to execute a Project Management Review that provides a proactive quality assurance review,
with an impartial analysis of all aspects of the project across all project management disciplines, enabling early detection
of project issues with actionable recommendations.
The purpose of this task is to execute a Design Review of SAP Solution service that provides a proactive quality assurance
review of the design of the SAP solution which is being implemented. It delivers an impartial analysis of all aspects of the
solution design across all relevant design perspectives and leads to an early detection of potential solution risks and
ofers actionable risk mitigation recommendations.
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 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.
00C000Public
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 eforts). For more information please refer to the Scrum Meeting
Guidelines.
Scrum-of Scrum Meetings are conducted to coordinate the work between diferent 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 efort by team, organization of sprint review and retrospective meetings)
Solves blocks and supports team, including escalation.
Ensures that management or others do not influence team.
SCRUM of SCRUMs Meeting is conducted to coordinate the work between diferent project SCRUM teams. SCRUM of
SCRUMs meetings allow teams to discuss their work, focusing especially on areas of overlap and integration. The meeting
cadence is defined for the entire project and follows the same structure. Some teams conduct daily SCRUM of SCRUMs
meeting while others consider weekly meeting sufficient. The main driver for the meeting cadence is the level of
collaboration between the individual SCRUM teams and level of dependencies between the features built in each SCRUM
team.
The purpose of Organizational Alignment is to ensure a smooth transition process towards the new way of working. This
includes the alignment of roles and responsibilities and activities to ensure that all employees are fully aligned to the goals
of the project and organization.
The purpose of this task is to use the results from previous change impact analysis and the role mapping information
(mapping of new business user roles to existing roles and organizational structure) and determine an appropriate transition
approach for the business.
The purpose of this task is to get to get complex organizational feedback regarding the progress and acceptance of the
project from the customers view.
The purpose of this task is to communicate the scope and plan for the sprint to the users outside of the core project team.
This may include end users, key stakeholders, people external to the project that have interest in information about the
project plans and progress.
The purpose of this task is to communicate the sprint results to the users outside of the core project team. This may include
end users, key stakeholders, people external to the project that have interest in information about the progress of the
project and accomplishments of the project team.
The purpose of this task is update communication plan and execute accordingly
00C000Public
The purpose of this deliverable is to determine the potential issues with the SAP education strategy and solution before
they impact the quality of the SAP software deployment.
The purpose of this task is to capture feedback on both the training strategy and approach, determine issues and propose
resolutions for identified issues.
The purpose of the deliverable End User Training Content Enabled is to ensure availability of end user training material,
training environment, logistics infrastructure and skilled instructors.
This task ensures a consistent appearance of the training materials and documentation by providing the development team
with standard templates.
The purpose of this task is to ensure that the training environment is correctly populated with correct data for training.
The purpose of this task is to provide a detailed outline of presentations and activities that serve to educate and prepare
the trainers scheduled to instruct end-user training classes
The purpose of this task is to prepare the execution of end-user training by mapping end users to appropriate training
courses, developing a training schedule and logistics plan, and inviting end users to courses
The purpose of the Configured General Settings and Organizational Structure deliverable is to complete and document the
initial configuration of the system on the basis of the decisions made in the business blueprint phase.
The purpose of this task is to implement the configuration related to general settings, and to document this in Solution
Manager.
The purpose of this task is to implement the configuration related to organizational structure, and to document this in
Solution Manager.
The purpose of the Configured Master Data Objects 1-n deliverable is to configure the master data in the SAP software
system according to the business process requirements specified in the business blueprint phase.
The purpose of this task is to prepare master data required for all business processes' unit and string tests in DEV.
The purpose of this task is to complete configuration of master data in the system
The purpose of the Core Configuration and Documentation deliverable is to ensure that the configuration is implemented,
tested and documented.
The purpose of this task is to implement the Core Configuration, write valid test cases and to document this in Solution
Manager.
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.
00C000Public
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-
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 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-
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.
00C000Public
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.
The purpose of this deliverable is to formally close the sprint by conducting the Sprint Review Meeting with key users,
product owner group and key stakeholders; formally sign-of the results and conduct sprint retrospective.
The purpose of this task is to demonstrate the results of the sprint to product owner team, key users and key project
stakeholders. The results of the demo is either acceptance of backlog item or in cases the feature is not accepted the user
story is amended by the product owner team, prioritized and remains in the product backlog ready for next sprint planning
meeting.
The demo in sprint review meeting serves as an input to formal sign-of for the sprint.
The purpose of this task is to obtain formal acceptance and signof of the sprint results following the sprint review meeting.
The product owner team is the party that provides the sign-of 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
user stories.
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.
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
00C000Public
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-
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
User acceptance test (UAT) is the last test cycle of an SAP solution implementation and is an essential part of gaining end-
user acceptance of the software system.
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.
Purpose of this task is to execute the testing, document the results and obtain customer approval (sign-of)
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.
00C000Public
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 objective of this task is to perform any remaining manual configuration changes in the production environment.
Setup of Availability and Continuity Management (ACM)
The purpose of this task is to define the approach and plan for Availability and Continuity Management.
The purpose of this task is to set and execute the identified failure scenarios.
The purpose of this task is to obtain the results from the failover scenario execution and determine the appropriate
mitigation actions for the test findings.
The purpose of planned Performance and System Test is to checks the entire system, consisting of databases, applications
servers, front ends, printers etc. The performance test measures the throughput and response times of the system.
The task defines and documents the identified test cases related to system and performance test. Outcome is documented
in a test plan.
The task defines and documents the identified test cases related to system and performance test. Outcome is documented
in a test plan.
The purpose of this task is to execute the performance tests and present the findings for these tests. The outcome should
be formally approved by the customer.
The objective of this task is to resolve issues identified during the performance or load testing. Upon resolution the issues
need to be re-tested and confirmed by responsible testers.
The purpose of this service is to support the start of production of an SAP Solution. During this service, SAP service
engineers check the solution for potential risks and give recommendations ensuring optimal performance and system
availability for core business processes.
The SAP GoingLive Check consists 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 efective operation
processes for security
The purpose of this task is to set-up, document and execute the administrative procedure for Roles and Authorizations.
00C000Public
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 of 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.
outstanding issues
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
ofers actionable risk mitigation recommendations.
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.
00C000Public
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 signof in order to exit system testing.
00C000Public
The purpose of this task is to prepare and execute the system tests. The outcome/results should be approved by the
customer.
The objective of this task is to resolve issues identified during the system testing. Upon resolution the issues need to be re-
tested and confirmed by responsible testers.
The purpose of production cutover is to perform the cutover to the production software and go live. At this point, the
organizational, business, functional, technical, and system aspects of the project are ready to be used in production.
The purpose of this task is to rehearse or simulate the cutover activities. During simulation, the main objective is to validate
and document the tasks, sequence, and duration of items on the cutover plan.
This task verifies that master data support is set up and process is operational
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 hand over the finalized implementation project and it's content, and set up as a productive
solution in SAP Solution Manager. This provides the basis for the follow up activities in the Run Phase.
The purpose of this deliverable is to formally close the release and prepare for next release and/or sprint planning meeting.
The purpose of this task is to 'groom' the product backlog. Product Owner Team needs to detail the user stories to ready
them for next release/sprint planning meeting. The stories need to meet definition of Ready for Build so they are
understood by the SCRUM team and can be estimated during the sprint planning meeting.
The purpose of this task is to conduct retrospective meeting with the project team to identify potential improvements of
user stories.
The purpose of this task is to update the Release and Sprint Plan according to changed priorities and focus of the team. It is
accountability of Product Owner to maintain the Release and Sprint plan and keep it current during the project.

outstanding issues
00C000Public
The purpose of this phase is to provide support for the solution during the period immediately following production
cutover. Exceptional items such as additional production support, exceptional business monitoring processes, and
extraordinary technical support are planned and executed in this phase. At the end of the designated extra-care period,
sustaining production support processes planned in final preparation and executed as part of go-live support become the
core support for continuous improvement in the ongoing solution.
The purpose of EU training during go-live support is to ensure that end users have adopted the solution, knowledge
resources are maintained, and responses to the 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.
00C000Public
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.
This task ensures 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.

outstanding issues
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
00C000Public
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
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
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
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
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
Ofers 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
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
00C000Public
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.
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.
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 efectively 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.
project and determine if potential gaps exist for the Upgrade Management area.
00C000Public
Q-Gate Key
Q-Gate Relevant Work Stream Accountable Role
Deliverable
_Phase
Mandatory Project Handover PM - Project Management Project Manager

Protocol
Mandatory Project Manager PM - Project Management Project Manager
Agreement
Mandatory Project Guideline (incl. PM - Project Management Project Manager
Travel Guideline)
Mandatory Project Charter PM - Project Management
OCM - Organizational Change M Project Manager

Mandatory Phase Kick Of Meeting PM - Project Management
Mandatory Scope Statement PM - Project Management

Document
00C000Public
PM - Project Management Application Consultant
Mandatory Work Breakdown PM - Project Management Project Manager

Structure (WBS)


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

00C000Public
Mandatory Solution Manager Usage ALM - Application Lifecycle Man Business Consultant
guideline,
Business Process
Modeling Standards
Optional Software System ALM - Application Lifecycle Man Business Consultant

Configuration Standards,
Enhancement and
Modification Standards
ALM - Application Lifecycle Man Application Consultant
Optional Test Management ISM - Test Management Test Management Consultant

Standards
Optional Change Request and TSM - Technical Solution Manag Application Consultant
Transport Management
Standards (CTS)
TSM - Technical Solution Manag Application Consultant
Optional Post Implementation TSM - Technical Solution Manag Technology Consultant

Service and Support
00C000Public
Mandatory Risk List (internal & PM - Project Management Project Manager

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

Report (internal &
external)
Optional OCM Roadmap OCM - Organizational Change Management
OCM - Organizational Change M Business Consultant
Training - Training
Optional Project Team Training Training - Training Education Consultant

Plan & Schedule
Training - Training
Mandatory Business Process Map BPM - Business Process Management

Business Process List
BPM - Business Process Manage Application Consultant
00C000Public
Optional Value Audit of Scope VM - Value Management
BPM - Business Process Manage Business Consultant
Optional Data Migration Approach, DM - Data Migration

Start and Scope

00C000Public
Optional Solution Landscape TSM - Technical Solution Management

Design
TSM - Technical Solution Manag Solution Architect

TSM - Technical Solution Manag Technology Architect

TSM - Technical Solution Manag Solution Architect
Optional Proj Support Tools & Sys TSM - Technical Solution Management
Setup
TSM - Technical Solution Manag Technology Consultant


00C000Public
Optional Project (phase) Lessons PM - Project Management Project Manager

Learned (internal)

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

Plan(s)
00C000Public


Report (internal &
external
Optional Stakeholder Analysis OCM - Organizational Change Management
(Internal)
OCM - Organizational Change M Education Consultant
Optional Organizational Change OCM - Organizational Change Management

Management Plan
00C000Public
Mandatory Training Project Plan Training - Training
Training - Training
Training - Training Business Consultant
Training - Training Instructor

Training - Training
Mandatory Business Blueprint BPM - Business Process Manage Application Consultant

Documents(Org
Structure)
Mandatory User Role Document BPM - Business Process Manage Application Consultant
00C000Public
Optional Value Audit of Scope VM - Value Management
Mandatory Development list(incl. BPM - Business Process Management

RICEFW, SOA, Migration)
00C000Public
BPM - Business Process Manage Integration Development
Consultant

Consultant
00C000Public
BPM - Business Process Manage Project Manager
BPM - Business Process Manage Project Manager
Mandatory Data Migration Design / DM - Data Migration

Plan
DA - Data Archiving
BPM - Business Process Manage Technology Architect
Mandatory Authorization TSM - Technical Solution Manag Technology Consultant

Requirements and Design
Mandatory Solution Landscape TSM - Technical Solution Management

Design
00C000Public

Mandatory Delivery of projects PM - Project Management

Results
Delivery Acceptance
Protocol

Learned (internal)
00C000Public

_Phase
milestones)

Plan(s)
00C000Public


Report (internal &
external
Optional User Role Document OCM - Organizational Change M Business Consultant
00C000Public
Training - Training
Optional End User Training and Training - Training

Documentation
Developed
Optional Training Environment Training - Training Education Consultant

Population and Testing
Optional End User Training Training - Training Education Coordinator

Schedule and Logistics
Mandatory Solution Documentation BPM - Business Process Management
Configuration, Interfaces,
Developments)

Developments)

Developments)

Optional Test cases & Results BPM - Business Process Manage Application Consultant
00C000Public
Developments)
Mandatory Development list(incl. BPM - Business Process Management

RICEFW, SOA, Migration)

Consultant
Consultant
Optional Test cases & Results BPM - Business Process Manage Integration Development
Consultant
Consultant
Consultant

VM - Value Management

Optional Test cases & Results ISM - Test Management Application Consultant

Design
00C000Public
Mandatory Production Cutover Plan CutOver - Cut Over Management
Optional Business Readiness OCM - Organizational Change M Project Manager

Approach
OCM - Organizational Change M Project Manager
Mandatory Test Strategy Plans & ISM - Test Management

Results
00C000Public

Mandatory Data Migration Design / DM - Data Migration
Plan

Mandatory Test cases & Results DM - Data Migration Application Consultant
Optional Test cases & Results DM - Data Migration Technology Architect
Mandatory Testplans & Results - UAT ISM - Test Management

DA - Data Archiving

Design
00C000Public
Optional Failover Environment TSM - Technical Solution Management

Design, Setup and Test
Results

ISM - Test Management Test Management Consultant

Optional SAP Going Live Check TSM - Technical Solution Management
Optional System User Roles and TSM - Technical Solution Management

Authorization
Administration
and
System Authentication
Management
00C000Public
Optional Technical Operations and TSM - Technical Solution Management
Handover Strategy
BPM - Business Process Manage Technology Consultant

Results
Delivery Acceptance
Protocol

Learned (internal)

_Phase
milestones)

Plan(s)
00C000Public


Report (internal &
external
Optional Functional/Technical OCM - Organizational Change M Business Consultant

Requirements and
Production Support
Processes Defined
Optional Master Data Support DM - Data Migration Application Consultant

Processes Established
Optional Business Process ALM - Application Lifecycle Man Technology Consultant
Operation
Optional System Administration ALM - Application Lifecycle Man Technology Consultant

and Control
Optional Security / Role and TSM - Technical Solution Manag Technology Consultant
Authorization
Management
Optional Transition to Support ALM - Application Lifecycle Man Technology Consultant
Training - Training
Optional Training Evaluations Training - Training Education Coordinator
Optional End User Training OCM - Organizational Change M Education Consultant

Delivery and Readiness
Checklist
00C000Public

Mandatory Testplans & Results CutOver - Cut Over Management Application Consultant
Mandatory Data Migration Design / DM - Data Migration Application Consultant

Plan
Mandatory Production Cutover Plan CutOver - Cut Over Management Application Consultant
Optional Readiness for Cutover - CutOver - Cut Over Management Application Consultant
Signof
Mandatory Production Cutover Plan CutOver - Cut Over Management Project Manager
Optional Solution Manager CutOver - Cut Over Management Technology Consultant

Update,
Solution Documentation

Results
Delivery Acceptance
Protocol

Learned (internal)
00C000Public

_Phase
milestones)

Plan(s)


Report (internal &
external
Optional Go-Live Training Sessions Training - Training

OCM - Organizational Change M Education Consultant
00C000Public
Optional Transition to Standard ALM - Application Lifecycle Man Technology Consultant

Support Processes
Optional Solution Manager ALM - Application Lifecycle Man Technology Consultant
Update,
Solution Documentation

Results
Delivery Acceptance
Protocol

Learned (internal)
00C000Public
_Phase
PM - Project Management Business Consultant
ALM - Application Lifecycle Man Technology Consultant
ALM - Application Lifecycle Man Test Management Consultant
00C000Public
00C000Public

Project Preparation and Initiation WBS

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Preparation and Initiation WBS

Uploaded by

Copyright:

Available Formats

WBS # WBS item title

1 1 1 Allocate Resources - hard booking with resource

1 1 4 Obtain Project Manager Agreement

1 1 5 Prepare Team Onboarding Document

1 2 1 Define Project Organization

1 2 3 Assign Roles and Responsibilities

1 2 4 Complete communication management plan

1 3 1 Prepare Project Charter Document

1 3 4 Obtain Project Charter Sign-of

1 4 1 Prepare for Kickof Meeting

1 5 1 Document Customer Requirements

1 5 3 Review Scope Statement with Customer

1 5 6 Create Work Breakdown Structure and WBS Dictionary

1 5 7 Refine Acceptance Criteria

1 5 8 Obtain customer sign of for project scope

1 6 1 Develop delivery schedule and assign resources

1 6 3 Include key workshops into the project schedule

1 6 4 Obtain Customer sign-of for project schedule

1 7 Project Management Plan

1 7 2 Obtain Project Management Plan Sign-Of

1 8 Project and Operational Standards

1 8 1 Conduct ALM Roadmap

1 8 3 Determine Solution Documentation Procedure

1 8 4 Determine Innovation Management Procedure

1 8 5 Determine Template Management Procedure

1 8 6 Determine Test Management Procedure

1 8 7 Determine Change Control Management Procedure

1 8 8 Determine Application Incident Management Procedure

1 8 10 Determine Business Process Operations

1 8 11 Determine Maintenance Management

1 8 12 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 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

1 13 4 Demonstrate the business processes and predefined

1 13 9 Validate and Complete business process map

1 14 1 Prepare Value Map

1 14 3 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

1 16 1 Prepare Testing Policy document

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

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

1 17 8 Conduct Risk Assessment for Data Migration and Prepare