Académique Documents
Professionnel Documents
Culture Documents
Project Preparation
Project Initiation
2 Identify Stakeholders
Project Governance
Project Charter
Kick-Off Workshop
Scope Statement
1 10
1 10
1 11
1 11
1 12
1 12
1 13
1 13
1 13
1 13
1 13
1 13
1 13
1 14
Value Determination
1 14
1 14
1 15
1 15
1 15
1 15
1 16
1 16
1 16
1 17
1 17
1 17
1 17
1 17
1 17
1 17
1 17
1 17
1 17
1 18
1 18
1 18
1 19
1 19
Interface Inventory
1 20
1 20
1 21
1 21
1 21
1 21
1 21
1 21
1 21
1 21
1 21
1 21
1 21 10
1 22
1 22
1 22
1 22
1 22
1 23
Business Blueprint
Phase Initiation
Stakeholder Analysis
Communication Plan
2 10
2 10
2 10
2 10
2 10
2 11
2 11
2 11
2 12
2 12
2 12
2 12
2 13
2 13
Value Realization
2 14
2 14
2 14
2 14
2 14
2 15
2 15
1 Conduct Visualizations
2 15
2 16
2 16
2 16
2 16
2 16
2 16
2 16
2 16
2 17
2 17
2 18
2 18
2 19
2 19
2 20
2 20
2 20
2 20
2 20
2 20
2 20
2 20
2 20
2 21
Testing Strategy
2 21
2 21
2 21
2 21
2 21
2 22
2 22
2 22
2 22
2 22
2 22
2 22
2 23
Realization
Phase Initiation
1 Allocate Resources and Update Project Schedule
Organizational Alignment
3 10
3 10
3 10
3 10
3 10
3 10
3 11
3 11
3 11
3 11
3 11
3 11
3 12
3 12
3 12
3 12
3 13
3 13
3 13
3 14
3 14
3 15
Scenario Test #1 - n
3 15
3 15
3 15
3 15
3 16
3 16
3 16
3 16
3 16
3 16
3 16
3 17
3 18
3 18
3 18
3 18
3 18
3 18
3 18
3 19
3 19
3 19
3 19
3 19
3 19
3 20
3 20
3 20
3 20
3 20
3 20
3 20
3 21
3 21
3 21
3 21
3 21
3 21
3 21
3 22
3 22
3 22
3 22
3 22
3 23
3 23
3 23
3 23
3 23
3 23
3 23
3 23
3 24
Failover Environment
3 24
3 24
3 24
3 25
3 25
3 25
3 25
3 25
3 25
3 25
3 25
3 26
3 26
3 27
3 27
3 28
3 28
3 28
3 28
3 29
3 29
3 30
3 30
3 30
3 30
3 30
3 30
3 30
3 31
Final Preparation
Phase Initiation
Production Cutover
Go Live Support
Phase Initiation
5 10
Operate
6 10
6 10
6 11
6 11
Description
Q-Gate
Relevant
This phase provides initial planning and preparation for the project.
Although each project has its own unique objectives, scope, and
priorities, the deliverables outlined below assist in completing the
initiation and planning steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that a
new project exists. It supports the decision to accept the project, align
stakeholders such as clients, customers, and SAP management around a
project and its scope, provide updated information for planning, and obtain a
commitment to proceed. It ensures alignment between SAP, the customers
strategic direction, and the satisfaction of operational requirements.
The purpose of phase resources allocation is a confirmation of resource
availability for the particular phase.
The purpose of this activity is to prepare the onboarding package for external
consultants from SAP and partner companies.
The purpose of this deliverable is to ensure that an efficient management
framework is in place for successful project execution.
Mandatory
The purpose of this task is to define the organizational structure, roles and
responsibilities of the project team.
Mandatory
The purpose of this task is to identify and select global company and external
resources for the project in accordance with the required roles, skills and
responsibilities specified in the preceding task. The assignment of people to
roles should also take into account their qualifications and availability for the
whole project time frame.
The purpose of this task is to complete the communications management plan.
This document outlines the processes required to ensure timely generation,
distribution, storage, and retrieval of project information.
The purpose of this deliverable is to clearly and explicitly define the objectives
of the proposed project, analyze all possible benefits and quantify benefits in
financial terms. This information and supporting documents align key
stakeholders around the strategic intent of the project.
Mandatory
The purpose of this activity is to collect all input required for the project charter
and document it into a format suitable for both communication purpose as for
formal sign-off purpose, if possible utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the correct groupings of
stakeholders have been identified for the project.
The purpose of this activity is to achieve a formal sign-off of the project charter.
The purpose of this deliverable is to kick-off the project/phase and ensure that
Mandatory
all needed information is shared with the resources for a successful project
execution.
The purpose of this task is to prepare the kickoff meeting which will helps
ensure the involvement of the team and other key resources and their
commitment to the project schedule.
The purpose of this activity is to gather the whole project team, including all
remotely involved resources, to kick-off the project or project phase. The
meeting is also used to examine the approach for the specific project phase.
Mandatory
Mandatory
The purpose of this activity is to collect input needed for the project
management plan and document it in a format suitable for both communication
purpose as for formal sign-off purpose, if possible utilizing the accelerator
file(s) provided
The purpose of this activity is to achieve a formal sign-off of the project
management plan
The purpose of the Project and Operational Standards deliverable is to provide
consistent means of executing and governing project work in an efficient and
effective manner. The key objective of Project Standards is to identify, define,
approve, and communicate standards related to project execution.
Where and when applicable, the current customer processes and procedures,
related to the project standards should be taken into account when defining the
most suitable standards for the project.
The purpose of this task is to analyze the Application Lifecycle Management
(ALM) maturity at the customer to understand system landscape,
organizational structure requirements, usage of Solution Manager and other
ALM tools and provide recommendations for implementation of ALM
processes with SAP Solution Manager
The purpose of this task is to determine the customers framework to centrally
document and relate business processes and technical information of SAP and
Mandatory
non-SAP Solutions in Solution Manager, ensuring transparency, efficient
maintenance and collaboration
The purpose of this task, also known as Innovation Management, is to
determine the customers approach for the identification, adaptation and
implementation of new and enhanced business and technical scenarios. It is
part of the application lifecycle and designed to decouple technical installation Optional
from business innovation using SAP Solution Manager to implement the
innovation in the system landscape.
The purpose of this task is to determine the customers template management
approach that allows customers with multi-site SAP installations to efficiently
manage their business processes across geographical distances from initial
template definition to template implementation and template optimization, for
example as part of a global rollout
The purpose of this task is to determine the customers approach for managing
functional and performance testing of SAP-centric business processes to
Optional
ensure validated system behavior after software change events.
The purpose of this task is to determine the customers approach of handling
business and technology-driven changes, using a standardized process
leading to improved reliability of solution and minimized risk through
segregation of duties and transparency of changes.
The purpose of this task is to determine the customers approach of a
centralized and common incident and issue message processing for multiple
organization levels. The process offers a communication channel with all
relevant stakeholders of an incident, including business user, customer-side
SAP experts, SAP Service & Support and Partner Support employees.
The Application incident Management is integrated in all ALM processes of
SAP Solution Manager, in any SAP Business Suite solution and can be
connected to an Non-SAP Help Desk application.
Optional
This task uses SAP Business Process Integration & Automation Management
(BPIAM) to cover the most important application related operations topics
necessary to ensure the smooth and reliable flow of the core business
processes to meet a company's business requirements.
The purpose of this task is to determine the customers approach of
Maintenance Management, how SAP Notes are handled and how they are
applied (upon request e.g. current incident in productive environment,
information from SAP about potential issue (Hot News, Security Notes)).
The purpose of this task is to determine the customers approach for the
identification, adaptation and implementation of new and enhanced business
and technical scenarios. It uses Solution Manager to manage the upgrade
project holistically and effectively end-to-end and allows SAP customers to
better understand and manage the major technical risks and challenges in an
upgrade project, and to make the upgrade project a nonevent for the
business.
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see
deliverable Project Management Plan) guide the approach to management,
execution, and control of project activities. The project manager is responsible
for ensuring that the management plans are applied at the appropriate level of
control.
The purpose of this activity is to assure that the project is executed according
to what was agreed to in project charter, scope statement and project
management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
Mandatory
status and progress of the project including potential disturbances due to
existing risks and issues.
The purpose of this deliverable is to present an overview of all planned change
management activities. It guarantees that all activities are related to each other
Optional
as well as to the overall project plan and ensures the checkability of OCM
activities.
The purpose of this activity is to collect all required input for the OCM roadmap
and document it in a format suitable for communication and inclusion into the
project management plan
Optional
Optional
The purpose of this task is to ensure that the business process structure in
SolMan is supporting the solution documentation and all continued project
activities in the coming phases (business process management, value
management, configuration & development, test, training and cut over).
The objective of this task is to setup project logistics, systems and
infrastructure that will support delivery of the project. This may include setup of
computers, setup of project team room, telephony, etc.
The purpose of this task is to install SAP GUI on project team computers.
The objective of this task is to validate that the remote connection to SAP is
working and connection can be established. This is both for the SAPGUI as
well as Web Access.
The objective of this task is to prepare for activation of the SAP Best Practices.
This consists of reviewing the Best Practice technical and functional
requirements and ensuring that the target system is on the correct release and
support package level, that all required SAP notes have been applied, etc.
The purpose of this task is to install pre-determined solution components
The objective of this task is to perform check of the installation of the service
pre-configuration, settings and objects
The objective of this task is to review the completeness of the installation
check and completion of the knowledge transfer
The purpose of this task is to prepare authorization roles in the systems for the
project team
The purpose of this task is the initial set up of all relevant testing tools (the
actual configuration will happen during Business Blueprint)
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project
closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
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 deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see
deliverable Project Management Plan) guide the approach to management,
execution, and control of project activities. The project manager is responsible
for ensuring that the management plans are applied at the appropriate level of
control.
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
The purpose of this activity is to assure that the project is executed according
to what was agreed to in project charter, scope statement and project
management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
Mandatory
Mandatory
The purpose of this task is to ensure that each contract is closed by verifying
that all work specified in the contractual arrangement was completed, and that Mandatory
all defined deliverables were accepted.
The purpose of the stakeholder analysis deliverable is to detect the level of
acceptance or the general attitude regarding the project on the part of all key
Optional
stakeholders, as well as the ways they can influence the project. Execute an
analysis of current state asis and future state tobe business process maps
to quantify the delta transition gap
Mandatory
Mandatory
Mandatory
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.
Mandatory
Mandatory
This task ensures that all solution documentation is made available for the
project team. Preferably the repository for this should be Solution Manager.
This task deals with the installation of 3rd party products needed to realize
scope of the project.
The purpose of this task is to set up users in the development environment.
The objective of this task is to perform any remaining manual configuration
changes in the Development environment.
The objective of this task is to validate the assignment of user role profiles /
authorizations to the test users in the development landscape.
Prepare master data required for a business process
The purpose of this deliverable is to create project related test framework,
which gets content input from the existing Test Policy (1.16.), to build a central
foundation around the taken approach (e.g. Test Approach and Methodology,
Test Standards and Guidelines, Test Case Development, Defect Management,
Reporting and Analysis, Roles and Responsibilities)
Mandatory
on functional testing (unit-, string-, integration-, scenario-, user acceptance,
regression testing etc.) and performance testing. The actual test strategy
documentation for functional testing and performance testing have to be
separated.
The objective of this task is to create a centralized document for functionaland performance testing, which incorporates standard and procedures which
will be used for the detailed test plan preparation / documentation.
Determine overall test data approach by aligning with the overall data migration
approach. The test data approach will be documented as part of the testing
strategy.
The objective of this task is to communicate the testing strategy (functional and
performance) to the customer project team and validate it.
Purpose of this task is to obtain customer approval (sign-off)
Purpose of this task is to start the requirements gathering process (e.g. KPI
and benchmarks). This activity is aligned with the documented overall
performance test strategy and will continue until the finalization of the
performance test concept
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project
closure
The purpose of this task is to collect knowledge assets and lessons learned at
the end of each phase of the project that can be reused later by other projects.
Collecting documents, experiences, project highlights and lessons learned
Optional
throughout the duration of the project can help to facilitate the project by
providing quick access and insights into key deliverables from earlier stages of
the project.
The purpose of this task is to pass the Project Quality Gate by conducting a
quality check at critical stages of the project. Project Quality Gates are an
integral part of SAPs Quality Built In approach for SAP primed, partner or
client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Performance testing
The purpose of the phase initiation deliverable is to formally recognize that a
new project phase starts.
The purpose of this task is to confirm resource availability for the particular
phase.
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 deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see
deliverable Project Management Plan) guide the approach to management,
execution, and control of project activities. The project manager is responsible
for ensuring that the management plans are applied at the appropriate level of
control.
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
The purpose of this activity is to assure that the project is executed according
to what was agreed to in project charter, scope statement and project
management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
Mandatory
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
Mandatory
status and progress of the project including potential disturbances due to
existing risks and issues.
The purpose of Organizational Alignment is to ensure a smooth transition
process towards the new way of working. This includes the alignment of roles
and responsibilities and activities to ensure that all employees are fully aligned
to the goals of the project and organization.
The purpose of this task is to use the results from previous change impact
analysis and the role mapping information (mapping of new business user
Optional
roles to existing roles and organizational structure) and determine an
appropriate transition approach for the business.
The purpose of this task is to get to get complex organizational feedback
regarding the progress and acceptance of the project from the customers
view.
The purpose of this task is update communication plan and execute
accordingly
The purpose of this deliverable is to determine the potential issues with the
SAP education strategy and solution before they impact the quality of the SAP
software deployment.
The purpose of this task is to capture feedback on both the training strategy
and approach, determine issues and propose resolutions for identified issues.
The purpose of the Knowledge Transfer deliverable is to ensure that key users
get a good understanding of the implemented solution.
In this task the SAP project team prepares for training and enablement of the
customer project team to understand the solution and how it is implemented in
their area, as well as trains the key users as defined in the statement of work.
Optional
Optional
Mandatory
Mandatory
The purpose of this task is to prepare master data required for all business
processes' unit and string tests in DEV.
The purpose of this task is to complete configuration of master data in the
system
The purpose of the Core Configuration and Documentation deliverable is to
ensure that the configuration is implemented, tested and documented.
Mandatory
The purpose of this task is to implement the Core Configuration, write valid test
cases and to document this in Solution Manager.
The purpose of this task is to prepare the test cases
The purpose of this task is to prepare the test cases
The purpose of this task is to perform unit test for the configuration
The objective of this task is to resolve any issues identified during the Business
Process Unit Test. It is crucial that the issues are re-tested by users that
reported them (or designated re-testers) and that they are confirmed.
Optional
The purpose of this task is to perform string test for the configuration
Optional
The objective of this task is to resolve any issues identified during the Process
String Test. It is crucial that the issues are re-tested by users that reported
them (or designated re-testers) and that they are confirmed.
Mandatory
The purpose of this task is to implement the Delta Configuration, write valid
test cases and to document this in Solution Manager.
The objective of this task is to develop process documentation for any changed
processes or for any new processes added to the standard.
The objective of this task is to develop process test cases for any changed
processes or for any new processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration
Optional
The objective of this task is to resolve any issues identified during the Unit and
String Test. It is crucial that the issues are re-tested by users that reported
them (or designated re-testers) and that they are confirmed.
The purpose of this deliverable is to develop and test the RICEFW objects.
Documentation to be stored in Solution Manager.
Mandatory
The purpose of this task is to develop the RICEFW object according to the
functional specification,
The purpose of this task is to document the RICEFW object information in a
technical specification and define the appropriate test case(s). Documentation
is stored in Solution Manager.
The purpose of this task is to perform unit and string test of the developments. Optional
The objective of this task is to resolve any issues identified during the RICEFW
object(s) Test. It is crucial that the issues are re-tested by users that reported
them (or designated re-testers) and that they are confirmed.
The purpose of this task is to perform final code review of the development
objects and confirm readiness for transport into QAS.
The purpose of the SOA / composite application development deliverable is to
implement and document the enterprise services, including developing and
realizing the composite application. The technical design and specifications
from the business blueprint phase serve as input.
The purpose of this task is to develop the Enterprise Service according to the
functional specification, document this in a technical specification and define
the appropriate test case(s). Documentation is stored in Solution Manager.
The purpose of this task is to develop the Composite and/or Mobile Application
according to the functional specification, document this in a technical
specification and define the appropriate test case(s). Documentation is stored
in Solution Manager.
The purpose of this task is to perform final code review of the development
objects and confirm readiness for transport into QAS.
Mandatory
The purpose of this task is to assess to what level the organization is prepared
Optional
for the cut over/transition
This purpose of this task is to check to what extent the support organization is
operational and ready for cut over
This task checks that proper governance of master data quality is defined.
The purpose of the preliminary cutover plan task is to document the strategy,
scope and timelines for moving from the as-is solution to the to-be solution and
the hyper care period immediately following go-live. This includes documenting
activities such as the transfer of data from the legacy systems to the SAP
software production system, setting up and initializing the production system,
closing the legacy systems, manually entering certain data in the new system,
setting up and verifying interface connections, importing transports and all
manual configurations.
The purpose of the review of the preliminary cutover plan is to validate the plan
for completeness, dependencies, timing and other constraints. At the end of
the review the project team will have understanding of necessary adjustments
to the preliminary cutover plan.
The purpose of this task is to refine the preliminary cutover plan based on
information the project team learned in the cutover plan review with customer.
The purpose of Approved Integration Test is to ensure functional correctness.
It test the integration of SAP solutions with non-SAP applications and
interfaces and can be executed in an iterative manner.
Mandatory
The purpose of this task is to define and document integration test cases, endto-end customer business process scenarios, according to the test plan. Test
plans and test case documentation is stored in Solution Manager.
The purpose of this task is to document the integration test case outlined in the
integration test plan
The objective of this task is to perform the Integration test according to
previously defined plan. During the test all issues must be logged and
documented in the system for traceability purpose.
The objective of this task is to resolve any issues identified during the
Integration Test. It is crucial that the issues are re-tested by users that reported
them (or designated re-testers) and that they are confirmed.
The purpose of this task is to obtain customer approval (sign-off) of the
integration test.
The purpose of the legacy data migration deliverable is to develop, implement,
and test the data migration programs and processes defined in the business
blueprint phase. This activity consists of iterative development and testing
cycles focused on the analysis of data, refinement of business rules, and
deployment of migration programs and processes designed to move, cleanse,
Mandatory
transform, and enrich legacy data required to support the various test cycles
and ultimately the production cutover. The test cycles enable the migration
team to improve data quality to an acceptable production level, develop a
detailed cutover sequencing plan, and exercise data reconciliation and
validation processes required to support the production cutover.
The purpose of this task is develop the specific architecture, programs, and
processes that support the extraction, validation, harmonization, enrichment,
and cleansing of the legacy data.
The purpose of this task is to execute and validate the manual conversion as
described in the manual data migration approach
The purpose of this task is to visualize the data quality metrics defined in the
data quality plan
The purpose of this task is to load the cleansed legacy data into the SAP
software target structures using a standard SAP load utility such as LSMW.
The purpose of this task is to obtain the results of the various test cycles so the
Mandatory
team can monitor the accuracy and efficiency of the data migration solution.
The purpose of this task is to provide one final assessment at the end of the
realization phase to report on the quality of the converted legacy data
Mandatory
The purpose of this deliverable is to execute the User acceptance test (UAT).
This is the last test cycle of an SAP solution implementation and is an essential Mandatory
part of gaining end-user acceptance of the software system.
The purpose of this task is to define and document UAT test cases according
to the test plan. Test plans and test case documentation is stored in Solution
Manager
The purpose oft his task is to adapt testing tools if needed (e.g. add of field
values and additional security roles) and train project team members, as
usually the test team gets extended before and during the UAT test cycle.
The purpose of this task is to document the integration test case outlined in the
UAT test plan
The objective of this task is to perform the End User Acceptance test
according to previously defined plan. During the test all issues must be logged
and documented in the system for traceability purpose.
The objective of this task is to resolve any issues identified during the User
Acceptance Test. It is crucial that the issues are re-tested by users that
reported them (or designated re-testers) and that they are confirmed.
The purpose of this task is to execute the testing, document the results and
obtain customer approval (sign-off)
The purpose of the SAP data archiving deliverable is to provide a method to
check, remove, and store data that has completed its lifecycle within the
solution. Data that meets the check criteria of data retention rules and is no
longer actively used in the system can be archived and deleted. Storage of the
data is a secondary process to enable data that has been archived and deleted
to still be viewed and reported on even though the data is no longer stored on
the transactional system.
The purpose of this task is to identify legal and business retention
requirements needed in prier to establish the baseline for data arched and
removal plan.
The purpose of this task is to develop the data archive plan that outlines the
planning for data archiving of the business objects at the customer site.
The purpose of this task is to develop the data archive storage plan needed for
the execution of each data archive run and creates the indexes for each
archive execution.
The purpose of this task is to test the data archive implementation execution in
QAS.
Mandatory
Optional
The purpose of this task is to define the approach and plan for Availability and
Continuity Management.
The purpose of this task is to set and execute the identified failure scenarios.
The purpose of this task is to obtain the results from the failover scenario
execution and determine the appropriate mitigation actions for the test findings.
The purpose of planned Performance and System Test is to checks the entire
system, consisting of databases, applications servers, front ends, printers etc.
The performance test measures the throughput and response times of the
system.
The task defines and documents the identified test cases related to system
and performance test. Outcome is documented in a test plan.
The task defines and documents the identified test cases related to system
and performance test. Outcome is documented in a test plan.
Mandatory
The purpose of this task is to document the test case outlined in the test plan
The purpose of this task is to document the test case outlined in the test plan
The purpose of this task is to execute the performance tests and present the
findings for these tests. The outcome should be formally approved by the
customer.
The objective of this task is to resolve issues identified during the performance
or load testing. Upon resolution the issues need to be re-tested and confirmed
by responsible testers.
The purpose of this task is to obtain customer approval (sign-off)
The purpose of this service is to support the start of production of an SAP
Solution. During this service, SAP service engineers check the solution for
Optional
potential risks and give recommendations ensuring optimal performance and
system availability for core business processes.
The purpose of this task is to perform the first session of the SAP GoingLive
Check.
The service consiste of two sessions - Analysis and Verification, and includes:
- Verification of the technical capabilities of the production environment (sizing
plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components
and Plug-Ins
Optional
The purpose of this task is to set-up, document and execute the administrative
procedure for Roles and Authorizations.
The purpose of the technical operations and handover strategy deliverable is to
update refine two prior deliverables from the Business Blueprint phase, and
Optional
prepare a strategy to hand off operations of the solution landscape to the postproduction support organization.
The purpose of this task is to ensure that proper staffing(people and
competence) is in place for the support org/team
The purpose of this task is to ensure that adequate support processes are in
place for the Go Live phase and beyond.
This task describes the considerations that are required to recognize and solve
critical situations during business process operation.
The primary goal of the SAP Technical Integration Check service is to identify
technical integration issues related to the core business processes, the
Optional
solution landscape, and the interfaces to SAP and non-SAP software systems.
The primary goal of the SAP Technical Integration Check service is to identify
technical integration issues related to the core business processes, the
solution landscape, and the interfaces to SAP and non-SAP software systems.
The check assesses your project from the technical perspective and generates
a list of actions that you should take to ensure maximum availability and
performance as well as smooth operations with your solution after going live.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project
closure
The purpose of this task is to pass the Project Quality Gate by conducting a
quality check at critical stages of the project. Project Quality Gates are an
integral part of 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
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 deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see
deliverable Project Management Plan) guide the approach to management,
execution, and control of project activities. The project manager is responsible
for ensuring that the management plans are applied at the appropriate level of
control.
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
Mandatory
The purpose of this activity is to assure that the project is executed according
to what was agreed to in project charter, scope statement and project
management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
Mandatory
status and progress of the project including potential disturbances due to
existing risks and issues.
The purpose of this survey is to take the pulse of the organization, prior to golive, to determine the general comfort level with the upcoming changes. If that
comfort level is not there, it is critical to determine where additional OCM work
needs to be focused. In addition the check of production support readiness is
to ensure that the resources and processes are in place to support the solution
after cutover.
The purpose of this task is to validate the outcome of the role mapping and
change impact analysis. This is done with the impacted business stakeholders Optional
in order to gain sponsors approval.
The purpose of this task is to ensure the customer establishes the means to
manage their data in an integrated environment.
This task provide a single defined support approach for monitoring and
measuring the customers daytoday support operations. The following four
topics needs to be covered:
- Exception Handling and Business Process and Interface Monitoring
- Data Volume Management
- Job Scheduling Management
- Transactional Consistency and Data Integrity
This task describes how all SAP technologies can be administered to run a
customer solution efficiently. The execution is mainly done locally but can be
triggered and managed from a central administration system.
Optional
Optional
Optional
The task ensure that the customer establishes the means to manage security,
Optional
roles and authorizations in their productive environment.
The purpose of this task is to extract the knowledge about the scope,
customizations, and business processes of the customers production
environment and transfer that knowledge to a long-term SAP support center
The purpose of the EU training delivery and readiness checklist is to provide a
checklist summarizing end-user training delivery to ensure readiness for
adoption of the solution. In the checklist, items governing training delivery,
communications, and future planning clarify the status of all aspects of the
training initiative.
The purpose of this task is to prepare the training delivery.
The objective of this task is to deliver end user training to identified end user
groups according to the previously developed training schedule.
Optional
The purpose of this task is to capture feedback on both the training session
and the trainer delivering the material
Optional
This task checks how prepared the people in the organization are with regards
Optional
to the identified changes and received EU training.
The purpose of this deliverable is to present the findings and recommendations
from the results of technical tests such as disaster recovery tests, backup and
restore tests, and other required technical or basis-related tests to the
customer or project team for final signoff in order to exit system testing.
The purpose of this task is to prepare and execute the system tests. The
outcome/results should be approved by the customer.
The objective of this task is to resolve issues identified during the system
testing. Upon resolution the issues need to be re-tested and confirmed by
responsible testers.
Purpose of this task is to obtain customer approval (sign-off)
The purpose of production cutover is to perform the cutover to the production
software and go live. At this point, the organizational, business, functional,
technical, and system aspects of the project are ready to be used in
production.
The purpose of this task is to rehearse or simulate the cutover activities.
During simulation, the main objective is to validate and document the tasks,
sequence, and duration of items on the cutover plan.
Mandatory
This task verifies that master data support is set up and process is operational Mandatory
The purpose of this task is to complete the Cut Over plan with results obtained
Mandatory
from the Go Live simulations.
The objective of this task is to perform all the cutover preparation activities
remaining to be closed prior to cutover weekend. The detailed cutover plan
contains the complete listing of all pre-cutover activities, their dependencies,
owners, and timing.
This task will confirm that the productive system is ready for Go Live.
Optional
The purpose of this task is the loading of production data from legacy systems
into the production environment. Once all preparations and configurations on
both the technical and application levels are completed, the final productive
solution can be set up and data loaded. The solution is live in a production
environment
Purpose of this task is to obtain customer approval (sign-off)
Mandatory
Purpose of this task is to hand over the finalized implementation project and it's
content, and set up as a productive solution in SAP Solution Manager. This
Optional
provides the basis for the follow up activities in the Run Phase.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project
closure
The purpose of this task is to collect knowledge assets and lessons learned at
the end of each phase of the project that can be reused later by other projects.
Collecting documents, experiences, project highlights and lessons learned
Optional
throughout the duration of the project can help to facilitate the project by
providing quick access and insights into key deliverables from earlier stages of
the project.
The purpose of this task is to pass the Project Quality Gate by conducting a
quality check at critical stages of the project. Project Quality Gates are an
integral part of SAPs Quality Built In approach for SAP primed, partner or
client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Mandatory
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
The purpose of this activity is to assure that the project is executed according
to what was agreed to in project charter, scope statement and project
management plan.
The purpose of this activity is to assure that resources are assigned to all
scheduled project activities (and tasks) and that work is progressing and
deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks
and changes related to those e.g. changes of project scope, timeline, costs
etc.
Mandatory
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
Mandatory
status and progress of the project including potential disturbances due to
existing risks and issues.
The purpose of knowledge support strategy is to provide an approach for
identifying and addressing ongoing learning needs, required knowledge
support, and processes for managing training for all solution users.
The purpose of this task is to define knowledge support strategy is to provide a
strategy for identifying and addressing ongoing learning needs, required
knowledge support, and processes for managing training for all solution users.
Since each user demographic has specific needs, the project needs to put in
place a set of ongoing learning plans and techniques.
The purpose of EU training during go-live support is to ensure that end users
Optional
have adopted the solution, knowledge resources are maintained, and
responses to the end-user acceptance survey are positive.
This purpose of this task is to adapt available training material and make it
suitable for End User training.
This task executes the delivery of EU training as well as capturing feedback on
both the training session and the trainer.
The purpose of this task is to capture feedback on both the training session
and the trainer delivering the material
This task checks how prepared the people in the organization are with regards
to the identified changes and received EU training.
The purpose of the production support and transfer to solution deliverable is to
confirm that the resources and processes are in place to support the ongoing
solution and to complete the steps required to close the project and finish
documentation.
The purpose of this task is to verify that the requirements identified in earlier
sessions are met.
The purpose of the production support and transfer to solution deliverable is to
confirm that the resources and processes are in place to support the ongoing
Optional
solution and to complete the steps required to close the project and finish
documentation.
The purpose of this task is to implement ongoing production support to the
SAP software system users and to monitor and optimize system performance.
The purpose of this activity is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.
The objective of this task is to resolve any functional issues identified during
the hyper care period after cutover. It is crucial that the issues are re-tested
and confirmed by users that reported them.
The objective of this task is to resolve any technical issues identified during the
hyper care period after cutover. It is crucial that the issues are re-tested and
confirmed by users that reported them.
The purpose of this task is to ensure knowledge transfer regarding the scope,
customizations, and business processes in the customers production
environments to the long-term SAP support center team.
Optional
Purpose of this task is to hand over the finalized implementation project and it's
content, and set up as a productive solution in SAP Solution Manager. This
Optional
provides the basis for the follow up activities in the Operate Phase.
Purpose of this task is to obtain customer approval (sign-off)
This milestone signifies formal transition from post production sustainment
support to long term support and operation of the new environment
The purpose of the End User Acceptance Survey deliverable is to ensure the
end-user acceptance, which is a key indicator of success for any SAP
implementation. The success of a project depends on how usable and
beneficial end users perceive the new processes and systems to be after golive. One of the key issues is to identify levels of acceptance and analyze what
cause them to vary.
The result of this task will determine the level of acceptance of the organization
and provides information needed for the analysis of what causes the
acceptance levels to vary.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project
closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
The purpose of this task is to ensure that each contract is closed by verifying
that all work specified in the contractual arrangement was completed, and that
all defined deliverables were accepted.
The purpose of this activity is to achieve a closure of all open project issues
which is a prerequisite for the final project closure.
The purpose of this activity is to document the results of the project, both
regarding achieved objectives, deliverables as well as adherence to schedule,
costs and delivered value.
The purpose of this activity is to formally close the project by obtaining
customer signatures on dedicated deliverables/documents e.g. Project Quality
Gate, Project Closeout Report
This milestone marks official closure of the project
Solution operations are initially set up during the implementation project.
The primary goal of this phase is to further optimize and automate the
operability of the solution. Operability is the ability to maintain IT
systems in a functioning and operating condition, guaranteeing systems
availability and required performance levels to support the execution of
the enterprises business operations.
The Operations Maturity Assessment evaluates the SAP customer's support
operations to determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements
for operations and to define what aspects of the operations need to be
adjusted, enhanced or implemented.
The report should detail assessment results and finding, including proposed
actions for how to bridge identified gaps.
Centrally document and relate business processes and technical information of
SAP and non-SAP Solutions ensuring transparency, efficient maintenance and
collaboration
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Solution Documentations area.
Represents the identification, adaptation and implementation of new and
enhanced future-proof business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical
installation from business innovation
Uses the SAP Solution Manager to implement the innovation in the system
landscape
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Solution Implementation area.
The template management approach allows customers with multi-site SAP
installations to efficiently manage their business processes across
geographical distances from initial template definition to template
implementation and template optimization, for example as part of a global
rollout
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Template Management area.
Functional and performance testing of SAP-centric business processes to
ensure validated system behavior after software change events
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Test Management area.
Workflow-based management of business and technology-driven changes,
with integrated project management and synchronized deployment capabilities.
Standardized process leading to improved reliability of solution and minimized
risk through segregation of duties and transparency of changes
Efficient solution management all project and system information is saved in
SAP Solution Manager
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Change Control Management area.
Enables a centralized and common incident and issue message processing in
multiple organization levels
Offers a communication channel with all relevant stakeholders of an incident.
The process includes business user, SAP experts@customer, SAP
Service&Support and Partner Support employees.
Is integrated in all ALM processes of SAP Solution Manager, in any SAP
Business Suite solution and could be connected to an Non-SAP Help Desk
application
Includes follow up activities as knowledge research, root cause analysis or
Change Management
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Incident Management area.
Represents all capabilities for monitoring, alerting, analysis and administration
of SAP solutions
Allows customers to reduce TCO by predefined content and centralized tools
for all aspects of operations in SAP Solution Manager
Provides End-to-End reporting functionality either out-of-the-box or individually
created by customers
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Technical Operations area.
SAP Business Process Integration & Automation Management (BPIAM)
comprises the most important application related operations topics necessary
to ensure the smooth and reliable flow of the core business processes to meet
a company's business requirements.
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Process Operations area.
SAP Notes provide a solution for known issues. SAP Notes are usually applied
upon request (e.g. current incident in productive environment, information from
SAP about potential issue (Hot News, Security Notes)).
SAP Notes are collected and released as Support Packages. Support
Packages are applied to SAP solutions to comply with legal requirements or
run on latest technology.
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Maintenance Management area.
Is the identification, adaptation and implementation of new and enhanced
business and technical scenarios
Uses the SAP Solution Manager to manage the upgrade project holistically and
effectively end-to-end
Allows SAP customers to better understand and manage the major technical
risks and challenges in an upgrade project, and to make the upgrade project a
nonevent for the business.
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential
gaps exist for the Upgrade Management area.
Accountable Role
_Phase
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Steering Committee
Definition, Org-Structure, PM - Project Management
Roles
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Charter
PM - Project Management
PM - Project Management
Project Manager
OCM - Organizational
Change Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Scope Statement
Document
Work Breakdown
Structure (WBS)
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Budgetplan
(internal & external)
PM - Project Management
Project Manager
Project Management
Plan(s)
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Technology Architect
Business Consultant
Software System
Configuration Standards, ALM - Application Lifecycle
Enhancement and
Management
Modification Standards
Business Consultant
Application Consultant
Test Management
Standards
Test Management
Consultant
Application Consultant
Application Consultant
Post Implementation
Service and Support
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Manager
Project (Performance)
Report (internal &
external)
PM - Project Management
Project Manager
OCM Roadmap
OCM - Organizational
Change Management
OCM - Organizational
Change Management
Business Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Training - Training
Value Map
Education Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
VM - Value Management
VM - Value Management
Business Consultant
VM - Value Management
Business Consultant
Business Consultant
Application Consultant
Application Consultant
Technology Consultant
Project Manager
DM - Data Migration
Application Consultant
DM - Data Migration
Technology Architect
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Technology Architect
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Solution Landscape
Design
Solution Architect
Technology Architect
Technology Architect
Solution Architect
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Management
Plan(s)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Manager
Project (Performance)
Report (internal &
external
PM - Project Management
Project Manager
Stakeholder Analysis
(Internal)
OCM - Organizational
Change Management
Organizational Change
Management Plan
Business Readiness
Approach
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
Education Consultant
OCM - Organizational
Change Management
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
Business Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Training - Training
Business Consultant
Training - Training
Instructor
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Application Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Application Consultant
Business Blueprint
Documents(Org
Structure)
Solution Documentation
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Solution Documentation
Application Consultant
Application Consultant
Application Consultant
VM - Value Management
VM - Value Management
Development list(incl.
RICEFW, SOA,
Migration)
Business Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Integration Development
Consultant
Application Consultant
Application Consultant
DM - Data Migration
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DA - Data Archiving
DA - Data Archiving
Technology Architect
Technology Architect
Authorization
Requirements and
Design
Solution Landscape
Design
Delivery of projects
Results
Delivery Acceptance
Protocol
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
DM - Data Migration
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Management
Plan(s)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Manager
Project (Performance)
Report (internal &
external
Project Manager
PM - Project Management
OCM - Organizational
Change Management
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
Business Consultant
OCM - Organizational
Change Management
Business Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Training - Training
Application Consultant
Training - Training
End User Training and
Documentation
Developed
Training Environment
Population and Testing
Application Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Education Coordinator
Solution Documentation
(incl. Process list,
BPM - Business Process
Configuration, Interfaces, Management
Developments)
BPM - Business Process
Management
BPM - Business Process
Management
Application Consultant
Application Consultant
Solution Documentation
(incl. Process list,
BPM - Business Process
Configuration, Interfaces, Management
Developments)
BPM - Business Process
Management
BPM - Business Process
Management
Application Consultant
Application Consultant
Solution Documentation
(incl. Process list,
BPM - Business Process
Configuration, Interfaces, Management
Developments)
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Solution Documentation
(incl. Process list,
BPM - Business Process
Configuration, Interfaces, Management
Developments)
BPM - Business Process
Management
BPM - Business Process
Management
Development list(incl.
RICEFW, SOA,
Migration)
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Application Consultant
Application Consultant
VM - Value Management
VM - Value Management
Business Consultant
Solution Landscape
Design
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
Application Consultant
_Milestone
Business Readiness
Approach
OCM - Organizational
Change Management
Project Manager
OCM - Organizational
Change Management
Project Manager
DM - Data Migration
Application Consultant
Application Consultant
Project Manager
Project Manager
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
DM - Data Migration
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Technology Architect
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Project Manager
DA - Data Archiving
DA - Data Archiving
Technology Architect
DA - Data Archiving
Application Consultant
DA - Data Archiving
Application Consultant
DA - Data Archiving
Application Consultant
Solution Landscape
Design
Failover Environment
Design, Setup and Test
Results
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Architect
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Test Management
Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Delivery of projects
Results
Delivery Acceptance
Protocol
PM - Project Management
PM - Project Management
Technology Architect
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Management
Plan(s)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Manager
Project (Performance)
Report (internal &
external
Project Manager
PM - Project Management
OCM - Organizational
Change Management
Functional/Technical
Requirements and
Production Support
Processes Defined
Master Data Support
Processes Established
OCM - Organizational
Change Management
Business Consultant
DM - Data Migration
Application Consultant
Business Process
Operation
Technology Consultant
System Administration
and Control
Technology Consultant
Technology Consultant
Transition to Support
Technology Consultant
Training - Training
Training - Training
Education Coordinator
Training - Training
Education Consultant
Training Evaluations
Training - Training
Education Coordinator
OCM - Organizational
Change Management
Education Consultant
Technology Consultant
Application Consultant
Technology Consultant
Application Consultant
DM - Data Migration
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Project Manager
Solution Manager
Update,
Solution Documentation
Technology Consultant
Delivery of projects
Results
Delivery Acceptance
Protocol
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Management
Plan(s)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Manager
Project (Performance)
Report (internal &
external
Project Manager
PM - Project Management
Training - Training
Training - Training
Go-Live Training
Sessions
Education Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Education Coordinator
OCM - Organizational
Change Management
Education Consultant
Technology Consultant
Technology Consultant
Project Manager
Application Consultant
Technology Consultant
Transition to Standard
Support Processes,
System Administration
and Control
Technology Consultant
Solution Manager
Update,
Solution Documentation
Technology Consultant
PM - Project Management
Project Manager
_Milestone
OCM - Organizational
Change Management
OCM - Organizational
Change Management
Business Consultant
Delivery of projects
Results
Delivery Acceptance
Protocol
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
PM - Project Management
Business Consultant
PM - Project Management
Project Manager
Application Consultant
Technology Consultant
Technology Consultant
Test Management
Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant
WBS #
Project Preparation
Project Initiation
Project Governance
Project Charter
1
Identify Stakeholders
Kick-Off Workshop
1
Scope Statement
5
1
5
1
1
1
8
1
9
Direct and manage project execution
3
Communicate Status and progress to project
stakeholders
10
Prepare Organizational Change Management
Roadmap
10 1
11
11 1
12
12
13
Prepare Business Process Map
13 1
Prepare Demo Environment for Scope
Refinement Workshops
13 2
13 3
13 4
13
6 Validate and Complete business process map
13
Value Determination
1
14
14 1
14 2
14 3
15
15 1
15 2
Store Scenario Level Solution Documentation in
SAP Solution Manager.
15 3
16
Prepare Testing Policy document
16 1
16 2
17
17 1
17 2
Conduct Data Audit (Data Health Check)
17 3
Prepare Data Migration Scope and Requirements
Document
17 4
17 5
17 6
17 7
17 8
Complete the Data Migration approach and
strategy document
17 9
18
Define Solution Landscape Concept
18 1
Define Solution Deployment Concept
18 2
Interface Inventory
1
19
Prepare Interface Inventory document
19 1
20
Complete HW sizing estimation for solution
landscape
20 1
21
21 1
21 2
Check availability of SAP Solution Manager
21 3
Install or Upgrade SAP Solution Manager
21 4
21 5
21 6
Install SAP GUI on project team computers
21 7
Test Remote Access and Establish OSS
Connection (both GUI and Web Access)
21 8
Prepare authorization roles in the systems for the
project team (DEV)
21 9
Set up of testing tools
21 10
22
22
22
22
3
22
23
Lean Blueprint
2
Phase Initiation
2
1
Allocate Resources and Update Project Schedule
2
Update Project Management Plan
1
Direct and manage project execution
5
Communicate Status and progress to project
stakeholders
Stakeholder Analysis
1
Identify Key Users
4
Validate organizational alignment approach
Communication Plan
1
Define Communication strategy
1
Develop Detailed End-User Training Plan
8
Adaptation of Pre-delivered Training Content
Scope Validation
3
Validate pre-defined RICEFW Objects (reports,
forms etc.)
10
10 1
10 2
10 3
10 4
11
11
11
12
12
12
12
Value Realization
2
13
13 1
14
Finalize Core Configuration Design
14 1
Finalize Delta Configuration Design
14 2
14 3
Define Functional Design - SOA & 3rd party
applications #1 - n
14 4
15
15 1
15 2
Baseline Build
16
16 1
16 2
Visualization
2
17
1 Capture Initial Visualization Requirements
17
17
17
Baseline Build Sign-Off
18
18 1
18 2
18 3
18 4
19
Ensure Master Data Management Processes
Ownership
19 1
Conduct Data Mapping workshops (master data
for pre-defined solutions)
19 2
19 3
19 4
19 5
Prepare Data Quality Plan
19 6
Prepare Data Security Design and plans
19 7
20
20 1
21
21 1
21 2
22
22 1
23
Execute Technical Installation of SAP Products
for DEV environment
23 1
Execute Technical Upgrade of SAP Products for
DEV environment
23 2
Install Solution Documentation in Solution
Manager
23 3
Execute Technical Installation of 3rd party
products
23 4
Set up Role assignment / Authorizations / Test
Users in DEV
23 5
Perform Manual Configuration in DEV
23 6
Validate Role assignment / Authorizations / Test
Users in DEV
23 7
Create master data in DEV environment - Master
Data #1 - n
23 8
Testing Strategy
24
24 1
Review and Validate Testing Strategy with
customer
24 2
24 3
25
25 1
25 2
25 3
26
26 1
26 2
26 3
26 4
26 5
26 6
26 7
27
Realization
3
Phase Initiation
3
1
Allocate Resources and Update Project Schedule
2
Sprint Initiation (Iterative)
3
Update Project Management Plan
2
Direct and manage project execution
5
Communicate Status and progress to project
stakeholders
Organizational Alignment
1
Conduct Sounding Board/Pulse Checks
5
Prepare Educational Readiness Report
1
Set up Training Environment
6
3
6
3
6
3
1
Configure Organizational Structure
7
3
1
Configure Master Data Objects #1 - n
8
3
1
Prepare Unit Test Cases
9
3
2
Prepare String Test Cases
9
3
3
Execute Business Process Unit Test
9
3
9
3
5
Execute Business Process String Test
9
3
9
3
10
10
1
Complete Delta Process Documentation
10
3
2
Complete Delta Process Test Cases
10
3
3
Execute Business Process Unit and String Test
Cases
10
3
10
3
11
11
11
3
11
3
11
3
4
Conduct Final Code Review
11
3
12
12
1
Validate and Complete Business Process
Procedure Document
12
3
13
Value Audits
13
1
14
Scenario Test #1 - n
3
14
3
3
14
14
3
14
3
15
15
1
Execute Technical Upgrade of SAP Products for
QAS environment
15
3
15
3
3
Set up Role Assignment / Authorizations / Test
Users in QAS
15
3
4
Prepare and Load Master Data into QAS
Environment for <SCOPE OPTION>
15
3
5
15
3
16
17
Sprint Closing
17
17
17
18
18
1
Conduct Production Support Readiness Check
18
3
2
18
18
18
5
Refine Preliminary Cutover Plan
18
3
19
19
1
19
19
3
19
3
19
3
20
20
1
20
20
3
20
3
4
Obtain Data Migration Test Results
20
3
5
Conduct Final Data Quality Assessment
20
3
21
21
1
Prepare and Document User Acceptance Test
Cases for <SCOPE OPTION>
21
3
21
3
21
3
4
21
22
22
22
3
22
3
3
3
22
23
23
1
Execute Technical Upgrade of SAP Products for
PRD Environment
23
3
2
Import Configuration and Development Objects to
PRD Environment
23
3
3
Set up Role assignment / Authorizations / Test
Users in PRD for <SCOPE OPTION>
23
3
4
Populate PRD with Test Master Data for <SCOPE
OPTION>
23
3
5
Prepare and Load master data into PRD
environment for <SCOPE OPTION>
23
3
6
23
24
Failover Environment
24
24
3
2
Obtain Failover Environment Test Results
24
3
25
25
1
Prepare Performance Test Plan
25
3
3
3
2
25
25
3
4
25
3
3
25
3
25
26
26
27
27
28
28
1
Establish Support Processes
28
3
2
Set-up Business Process Monitoring
28
3
29
29
29
29
29
29
3
29
3
30
Final Preparation
Phase Initiation
4
1
Allocate Resources and Update Project Schedule
2
Update Project Management Plan
1
Direct and manage project execution
4
Communicate Status and progress to project
stakeholders
1
Validate that Master Data Support Processes is
established
4
Establish Security / Role and Authorization
Management
5
Execute Technical System Tests
1
Perform System Test Defect Resolution
Production Cutover
4
1
Conduct Data Quality Readiness Check
4
Final Check of Production Readiness and SignOff for transition to Production
8
Release Closing
Go Live Support
5
Phase Initiation
5
1
Allocate Resources and Update Project Schedule
2
Update Project Management Plan
1
Direct and manage project execution
4
Communicate Status and progress to project
stakeholders
1
3
2
3
3
Perform People Readiness assessment
3
5
1
5
5
5
5
5
5
5
6
Obtain Solution Transition to Production
Acceptance Protocol Sign-off
5
5
7
6
7
5
7
5
7
5
5
8
Operate
6
Operations Maturity Assessment
6
2
Perform assessment of Solution Documentation
set up
3
Perform assessment of Solution Implementation
set up
4
Perform assessment of Template Management
set up
6
Perform assessment of Change Control
Management set up
7
Perform assessment of Incident Management set
up
8
Perform assessment of Technical Operations set
up
9
Perform assessment of Process Operations set
up
10
Perform assessment of Maintenance
Management set up
10 1
11
Perform assessment of Upgrade Management set
up
11 1
Description
This phase provides initial planning and preparation for the project. Although each project
has its own unique objectives, scope, and priorities, the deliverables outlined below assist
in completing the initiation and planning steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that a new project exists. It
supports the decision to accept the project, align stakeholders such as clients, customers, and
SAP management around a project and its scope, provide updated information for planning,
and obtain a commitment to proceed. It ensures alignment between SAP, the customers strategic
direction, and the satisfaction of operational requirements.
The purpose of phase resources allocation is a confirmation of resource availability for the
particular phase.
The purpose of this activity is to prepare the onboarding package for external consultants from
SAP and partner companies.
The purpose of this deliverable is to ensure that an efficient management framework is in place for
successful project execution.
The purpose of this task is to determine the structure and composition of agile teams in order to
optimally setup the project organization in line with agile principles. It is required to setup agile
teams as cross functional groups that consist of SCRUM master, Product Owner and team
members. Team size should be 7 +/- 2 members. The cross-functional team needs to be
composed of business analyst, functional experts, technical experts and testers required to fully
implement feature in iteration.
The purpose of this task is to complete the communications management plan. This document
outlines the processes required to ensure timely generation, distribution, storage, and retrieval of
project information.
The purpose of this deliverable is to clearly and explicitly define the objectives of the proposed
project, analyze all possible benefits and quantify benefits in financial terms. This information and
supporting documents align key stakeholders around the strategic intent of the project.
The purpose of this activity is to collect all input required for the project charter and document it
into a format suitable for both communication purpose as for formal sign-off purpose, if possible
utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the correct groupings of stakeholders have been
identified for the project.
The purpose of this task is to build agile awareness of key stakeholders, secure commitment to
adopt standard SAP functionality where possible. It is recommended to conduct informal and
formal meetings to set the expectations and confirm the project approach with key project
stakeholders.
The purpose of this activity is to achieve a formal sign-off of the project charter.
The purpose of this deliverable is to kick-off the project/phase and ensure that all needed
information is shared with the resources for a successful project execution.
The purpose of this task is to prepare the kickoff meeting which will helps ensure the involvement
of the team and other key resources and their commitment to the project schedule.
The purpose of this activity is to gather the whole project team, including all remotely involved
resources, to kick-off the project or project phase. The meeting is also used to examine the
approach for the specific project phase.
The purpose of this deliverable is to facilitate an initial understanding of the project scope and
associated project-related assumptions and constraints. The project scope statement evolves
through the initiation and planning of the project and clearly and explicitly defines the deliverables
of the proposed project. This information and supporting documents align key stakeholders
around what the project is going to deliver.
The purpose of this activity is to collect and document both process-related as well as project-/nonprocess-related customer requirements, which in summary and as appendix become part of the
scope statement
The objective of this task is to review the scope statement document with the customer project
manager and key stakeholders in order to confirm the scope and obtain approval.
The purpose of this task is to determine all gaps for customer solution, document them formally
and estimate effort to cover the identified gaps.
The objective of this task is to present the results of fit gap analysis to customer including the
effort estimates to cover the identified gaps as part of the project/service delivery.
The purpose of this task is to create the work breakdown structure (WBS) for the project, which is
a deliverable-oriented, hierarchical decomposition of the work to be executed by the project team
to complete the project. It is the basis for the organization and coordination of the project. A WBS
consists of WBS elements that describe project tasks and subtasks to perform within a defined
time period.
The purpose of this activity is to clearly define the acceptance criteria against which project
deliverables and results are measured that have been listed in the Scope Statement. These
should also be updated in the Project Quality Gate Scorecard. In the context of Agile projects this
translates to the definition of Done for the backlog items that are being delivered in the project.
The purpose of the Project Schedule deliverable is to define the work schedule to be followed, the
resources and associated time commitments required for the project and the phases of the
project. The work breakdown structure (WBS) serves as the foundation for the schedule, the
deliverables to be produced and tasks to be performed, as part of the project. The project budget,
including monitoring and control, outlines all costs associated with the project, including labor,
hardware, software, contracting fees, and facilities.
At a minimum, the schedule should include:
Deliverables and tasks for the current phase
Estimated effort (work) and duration
Task dependencies (such as predecessors and successors)
Scheduled start and finish dates for each task, based on dependencies
Task constraints (such as must-start-on date and must-finish-on date)
Resources assigned to each task
High-level schedule for subsequent phases
The purpose of this task is to define a high level release plan, determine the length and number of
sprints per release. During this activity the project team needs to take into accounts business
needs, project objectives & goals, available technical environment, complexity of the solution,
geographical and organizational scope of the project and other aspects (like seasonality of
customer's business). The outcome of this task is high level release plan that includes key
features targeted in each release and number/duration of sprints (note that the sprint duration
should be fixed for all project teams and should not vary).
The purpose of this activity is to extract all planned workshops during the project/phase into a
schedule that facilitates workshop planning
Purpose of this task is to obtain customer approval (sign-off)
The purpose of this activity is to create project schedule and cost baseline against which tracking,
change management and status reporting is done.
The purpose of the project management plan deliverable is to develop the project management
plan and the subsidiary plans on the basis of the project scope defined in the project charter.
The purpose of this activity is to collect input needed for the project management plan and
document it in a format suitable for both communication purpose as for formal sign-off purpose, if
possible utilizing the accelerator file(s) provided
The purpose of this activity is to achieve a formal sign-off of the project management plan
The purpose of the Project and Operational Standards deliverable is to provide consistent means
of executing and governing project work in an efficient and effective manner. The key objective of
Project Standards is to identify, define, approve, and communicate standards related to project
execution.
Where and when applicable, the current customer processes and procedures, related to the
project standards should be taken into account when defining the most suitable standards for the
project.
The purpose of this task is to define and set up SCRUM standards and tools, such as SCRUM board, burn-down chart, product ba
The purpose of this task is to determine the customers framework to centrally document and relate
business processes and technical information of SAP and non-SAP Solutions in Solution
Manager, ensuring transparency, efficient maintenance and collaboration
The purpose of this task, also known as Innovation Management, is to determine the customers
approach for the identification, adaptation and implementation of new and enhanced business and
technical scenarios. It is part of the application lifecycle and designed to decouple technical
installation from business innovation using SAP Solution Manager to implement the innovation in
the system landscape.
The purpose of this task is to determine the customers template management approach that
allows customers with multi-site SAP installations to efficiently manage their business processes
across geographical distances from initial template definition to template implementation and
template optimization, for example as part of a global rollout
The purpose of this task is to determine the customers approach for managing functional and
performance testing of SAP-centric business processes to ensure validated system behavior after
software change events.
The purpose of this task is to determine the customers approach of handling business and
technology-driven changes, using a standardized process leading to improved reliability of solution
and minimized risk through segregation of duties and transparency of changes.
The purpose of this task is to determine the customers approach of a centralized and common
incident and issue message processing for multiple organization levels. The process offers a
communication channel with all relevant stakeholders of an incident, including business user,
customer-side SAP experts, SAP Service & Support and Partner Support employees.
The Application incident Management is integrated in all ALM processes of SAP Solution
Manager, in any SAP Business Suite solution and can be connected to an Non-SAP Help Desk
application.
The purpose of this task is to determine the customers approach of monitoring, alerting, analyzing
and administrating of SAP solutions. It allows customers to reduce TCO by predefined content and
centralized tools for all aspects of operations in SAP Solution Manager, including End-to-End
reporting functionality either out-of-the-box or individually created by customers
This task uses SAP Business Process Integration & Automation Management (BPIAM) to cover
the most important application related operations topics necessary to ensure the smooth and
reliable flow of the core business processes to meet a company's business requirements.
The purpose of this task is to determine the customers approach of Maintenance Management,
how SAP Notes are handled and how they are applied (upon request e.g. current incident in
productive environment, information from SAP about potential issue (Hot News, Security Notes)).
The purpose of this task is to determine the customers approach for the identification, adaptation
and implementation of new and enhanced business and technical scenarios. It uses Solution
Manager to manage the upgrade project holistically and effectively end-to-end and allows SAP
customers to better understand and manage the major technical risks and challenges in an
upgrade project, and to make the upgrade project a nonevent for the business.
The purpose of this deliverable is to execute the project management plan and control and
monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable Project
Management Plan) guide the approach to management, execution, and control of project
activities. The project manager is responsible for ensuring that the management plans are applied
at the appropriate level of control.
The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks and changes related
to those e.g. changes of project scope, timeline, costs etc.
The purpose of this activity to make sure that project stakeholders are aware of status and
progress of the project including potential disturbances due to existing risks and issues.
The purpose of this deliverable is to present an overview of all planned change management
activities. It guarantees that all activities are related to each other as well as to the overall project
plan and ensures the checkability of OCM activities.
The purpose of this activity is to collect all required input for the OCM roadmap and document it in
a format suitable for communication and inclusion into the project management plan
The purpose of this deliverable is to develop a comprehensive training strategy that provides all
team members with a phase-based learning path for acquiring the skills and knowledge needed to
complete the project successfully. This learning path leads to project readiness as well as
certification on the specific applications the team members will be using.
The purpose of this 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.
Validate and Complete Business Process Map with pre-defined content depending on delivery
model (Industrialized and/or Assemble to Order process content).
The purpose of Value Determination is to ensure the alignment of the business case value drivers
with key process changes and functionality by establishing a value tracking framework and
identifying business stakeholders
The purpose of this task is to review the project business case, map key value drivers to process
changes, develop the value tracking framework (KPI's and PPI's), identify value enablers, as well
as assign business accountability for value realization.
The purpose of this task is for the Product Owner to prepare the initial product backlog which
consists of the following elements:
Vision and Business Case: Why do we want to do this? What is the value? What are current
pain points?
HighLevel Business Process scope: What are the business scenarios and processes (level 1
and level 2) to be implemented?
Who will work with the processes and what are their primary business requirements? This will
be used as input for the definition of the user stories.
The purpose of this task is to validate that identified key process changes, key performance
indicators, and value enablers are accurate and make necessary adjustments to the document
The purpose of this task is to capture Business requirements and relate them to business
scenarios, business objectives and benefits
The purpose of this task is to complete the Business Scenario Design document with relevant predefined business process content (Assemble to order and/or Industrialized content)
The purpose of this task is to store Business Scenario content in Solution Manager, according to
Business Process Hierarchy structure defined for the project.
The purpose of this deliverable is to outline key elements of the testing methodology that the
project will use as guiding principles going forward. This is should be aligned with the customers
"Enterprise" approach on how to conduct testing (Not to be updated over time)
The purpose of this task is to collect all required information needed for the Test Policy, and to
document it in a format suitable for communication.
The purpose of the data migration approach and Strategy deliverable is to capture and
communicate the approach and strategy for the legacy data migration. This deliverable is intended
to educate the SAP and customer project team members on the SAP data migration framework
and methodology used to support the data migration project. In addition, the scope and
requirement for data migration should also be determined
The purpose of this task is to make the necessary arrangements for the execution of the workshop
The purpose of the data migration workshop deliverable is to perform a two-day scoping workshop
to explain the SAP data migration approach and to understand the customers legacy data
systems, business priorities, and technical infrastructure.
The purpose of the data audit is to identify the legacy systems that will supply data for the SAP
applications and to profile the quality of the legacy data.
The purpose of this task is to prepare the data migration scope and requirements document that
captures the overall scope and requirements of the data migration effort.
The purpose of this task is to present data migration scope and requirements document to
customer project team and obtain buy in.
The purpose of this task is to assess customer organization for the demands of data migration
process. The outcome of this task is documented current state of the organization and required
target state.
The purpose of this task is to assess customer infrastructure for the needs of the data migration
process. As a result the project team learns about available tools and identifies any
gaps/requirements to acquire tools to support the migration process.
The purpose of this task is to assess risk for the data migration activities. The risk assessment
focuses on organization, technical risk, data quality risk and other risks that may impact the data
migration activities. During this task the team prepares mitigation strategies for the individual risk
items in the risk register.
The purpose of this activity to collect input needed for the Data Migration Approach and Strategy
document, in a format suitable for both communication purpose as well as for formal sign-off
purpose.
The purpose of the technical requirements and design deliverable is to provide the project with a
specification of the target solution from a software component standpoint. This document is
intended to serve as a reference for the rest of the project team during the Business Blueprint
phase.
Included in this deliverable is the solution landscape deployment plan, which is a high level
description of the overall system landscape approach to be used for the implementation project.
The purpose of this task is to outline the software components and the design of the future
solution landscape.
The purpose of this task is to describe the concept of how the solution in scope will be deployed.
The purpose of the interface inventory deliverable is to preliminarily identify the external systems,
applications, and business objects or transactions that must be integrated with the SAP solution to
realize the objectives of the project
The purpose of this task is to collect necessary information for the interface inventory document.
The purpose of the initial hardware sizing proposal is to begin the process of assessing the
hardware infrastructure requirements.
The purpose of this task is to completed sizing estimates for the Solution Manager system and
Production and non-Production environments.
The purpose of the project support tools and system setup deliverable is to establish the basic
tools and processes necessary to support the project.
One of the most vital project tools is the SAP Solution Manager, the centerpiece of SAPs
Application Lifecycle Management tools. The SAP Solution Manager provides a central point of
access for a variety of essential project support functions, including:
The purpose of this task is to validate all technical system requirements for delivery of the service
or project. The objective is to ensure that all required technical requirements have been satisfied
and work can be performed by the team.
The purpose of this task is to validate all functional requirements for delivery of the service or
project. The objective is to ensure that all required functional requirements have been satisfied
and work can be performed by the team.
The purpose of this task is to validate that customer has SAP Solution Manager installed and
setup.
The purpose of this task is to validate and ensure a proper Solution Manager setup.
The purpose of this task is to ensure that the business process structure in SolMan is supporting
the solution documentation and all continued project activities in the coming phases (business
process management, value management, configuration & development, test, training and cut
over).
The objective of this task is to setup project logistics, systems and infrastructure that will support
delivery of the project. This may include setup of computers, setup of project team room,
telephony, etc.
The purpose of this task is to install SAP GUI on project team computers.
The objective of this task is to validate that the remote connection to SAP is working and
connection can be established. This is both for the SAPGUI as well as Web Access.
The purpose of this task is to prepare authorization roles in the systems for the project team
The purpose of this task is the initial set up of all relevant testing tools (the actual configuration will
happen during Business Blueprint)
Ensure that all required deliverables from this phase and the project are complete and
accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to collect knowledge assets and lessons learned at the end of each
phase of the project that can be reused later by other projects. Collecting documents,
experiences, project highlights and lessons learned throughout the duration of the project can help
to facilitate the project by providing quick access and insights into key deliverables from earlier
stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a quality check at critical
stages of the project. Project Quality Gates are an integral part of SAPs Quality Built In approach
for SAP primed, partner or client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been completed in
compliance with recommended practices and to the customers satisfaction
To enable project management to continuously communicate the process and build quality
directly into the project
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/update the business blueprint, which is a detailed
process-oriented and technical documentation of the results gathered during requirements
and design workshops or based on validation of predefined solution or service description.
A blueprint consists of multiple documents illustrating how the company intends to run its
business using SAP solutions.
The purpose of the phase initiation deliverable is to formally recognize that a new project phase
starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this task is to ensure the involvement of the team and other key resources and
their commitment to the project schedule. The meeting is also used to examine the approach for
the specific project phase.
The purpose of this deliverable is to execute the project management plan and control and
monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable Project
Management Plan) guide the approach to management, execution, and control of project
activities. The project manager is responsible for ensuring that the management plans are applied
at the appropriate level of control.
The purpose of this task is to update the project management plan and the subsidiary plans
based on the changes agreed during the projects change management process.
The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.
The purpose of this task is to plan, setup and conduct various SCRUM meetings in order to keep
the project teams aligned around common vision, share information amongst the SCRUM teams
and align individuals within each team. The purpose of these standard meetings is to inform others
about work that individual team members do on given day and surface any blockers that team
members need help addressing .
In Agile implementation project the teams conduct following meetings:
1. Daily SCRUM meeting - short (about 15 minutes) session within each SCRUM team facing the
SCRUM board team members report to the team about what they work on and whether they are
encountering any issues that they need help with. Objective of this session is to inform and align
the team work.
2. Regular SCRUM of SCRUMs meeting - session in which SCRUM Masters from individual
SCRUM teams share information about what each SCRUM team works on, surface any cross
team alignment topics and resolve any issues that arise between the teams. The session is very
similar to integration team meetings conducted in traditional projects. Note: Cadence of these
sessions needs to be calibrated, but they should be done on at least bi-weekly basis. The more
often they are done the shorter they can be.
3. Sprint Demo - the purpose of this meeting is to demonstrate the results of the sprint to customer
and obtain acceptance to release the features developed during the sprint. The meeting is
attended by Product Owner team, End users and SCRUM team. It is conducted at the end of
sprint.
4. Sprint Retrospective - or process improvement meeting is conducted right after Sprint Demo
meeting prior to closing the sprint. The objective of this meeting is for the SCRUM team to conduct
The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks and changes related
to those e.g. changes of project scope, timeline, costs etc.
The purpose of this task is to ensure that each contract is closed by verifying that all work
specified in the contractual arrangement was completed, and that all defined deliverables were
accepted.
The purpose of the stakeholder analysis deliverable is to detect the level of acceptance or the
general attitude regarding the project on the part of all key stakeholders, as well as the ways they
can influence the project. Execute an analysis of current state asis and future state tobe
business process maps to quantify the delta transition gap
The purpose of this task is to re-visit the stakeholder identification results, determine the detailed
level of change impacts for the identified stakeholder (groups) in order to create transparency
about the organizational and system changes.
The purpose of this task is to identify key users needed for the different areas (depending on the
scope of this project).
The purpose of the Change impact analysis deliverable is to ensure that the organizational and
technical changes in business processes have been identified and documented by comparing the
as-is and the to-be business processes.
The purpose of this task is to validate the chosen approach with key stakeholders for the
continued project execution.
The purpose of this task is to define the baseline for where organizational change management
starts and against which progress and success of the OCM-activities are measured.
The purpose of the communication plan deliverable is to summarize all planned communication
measures and to help identify the dependencies among various activities. The communication
plan is aligned to the overall OCM roadmap and addresses mainly external communication to
stakeholders, key users, end users, and suppliers.
The purpose of this task is to provide a set of key messages to describe the benefit of the SAP
solution and the change impact for every stakeholder group. Due to the individual goals and
interests of stakeholder groups, it is necessary to define specific key messages for each
stakeholder group, for example to specify what to tell particular employees.
The purpose of this task is to define the communication strategy for the change management
activities.
The purpose of the End User Training Strategy and Plan deliverable is to develop a high level
training plan that provides the recommended approach and corresponding activities to prepare the
end users for using the new system.
The purpose of this task is to perform an analysis of the end-user population to be trained and
determine where the skills levels, knowledge gaps, and training requirements are located. This
analysis contains the key customer information for definition of the end-user training and
documentation of high-level project plan recommendations, proposals, and preliminary strategies.
The purpose of this task is to develop a working document to track evolution of documents and
progress of processes for all education aspects of the project
The purpose of the Project Team Training deliverable is to ensure that the project team is
informed about the way of working during the Blueprint Phase including usage of Solution
Manager for Solution Documentation.
The purpose of this task is to clarify deliverables and expectations, methodology, and tools.
Typically two to three days should be reserved for this training. Once the team members or at
minimum the team leads are identified, they will be brought on board with this ramp-up training
before the phase kickoff meeting. The blueprint ramp-up deliverable:
The purpose of this task is to train the key users for the solution in scope (pre-defined content)
The purpose of the end user training content deliverable is to create a curriculum plan that covers
the skills that end users will need to possess to use the system. This document will be refined
throughout the project.
The purpose of this task is to validate and adapt the standard end user training material being predelivered within the solution. (delivery model 3&4).
The purpose of this task is to prepare training content in the system environment being set up for
the project.
The purpose of solution validation / fit-gap analysis deliverable is to validate the predefined
scenarios, processes and enhancements; identify potential gaps between delivered product and
customer requirements. The deliverable only captures requirements for gaps. It follows an iterative
approach. Existing documentation and models can be altered, changes have to be marked and
documented in Solution Manager.
This task validates predefined general settings and that these are still relevant for the scope of the
implementation, such as organizational structures or customer or material masters, and to identify
potential gap between delivered product and customer requirements.esign a solution for these
business objects within the SAP solution. These objects are associated to processes and reflected
in applications so understanding these relationships is essential for overall integration and crossprocess integrity.
This task validates predefined scenario solution documentation, identifies potential gap between
delivered product and customer requirements. Only requirements for gap are being captured. It
follows an iterative approach. Existing documentation and models can be altered, changes have to
be marked and documented in Solution Manager
This task validates predefined process solution documentation, identifies potential gap between
delivered product and customer requirements. Only requirements for gap are being captured. It
follows an iterative approach. Existing documentation and models can be altered, changes have to
be marked and documented in Solution Manager.
This task validates the pre-defined RICEFW Objects (reports, forms etc.). Additional customization
and enhancements should be kept to a minimum.
The purpose of this task is to capture all identified delta requirements from the validation sessions
in the product backlog.
The requirements are captured in form of user stories that define the requirement from end-user
perspective, provide details on how to test the feature when it is completed, priority of the backlog
item and business value.
The purpose of business objects modeling (cross-process view) is to identify business objects that
are relevant for the scope of the implementation, such as organizational structures or customer or
material masters, and to design a solution for these business objects within the SAP solution.
Business objects are associated to processes and reflected in applications. Understanding these
relationships is essential for overall integration and cross-process integrity.
Business object modeling may also build the foundation for service modeling, if the project is
implementing a service-oriented architecture (SOA).
The purpose of this task is to capture the design and requirements of the organizational structure.
This should reflect multiple views of a company i.e. Legal, Fiscal, Functional, Product-oriented,
Regional and geographical, Customer-group, Distribution-channels, Purchasing-channels etc.
depending on the process scope.
It is best to store all organizational structure deliverables in the process hierarchy in SAP Solution
Manager.
The purpose of General Settings and Master Data is a detailed description of design and
maintenance processes for general settings and master data. This includes definition of business
rules and ownership.
General Settings and Master Data Design also addresses cross-application general settings and
master data for e.g. countries, languages, currencies, organizational units, units of measure,
number ranges, product hierarchies, material types and shipment rules.
The purpose of the user role concept is to describe all relevant end-user roles and corresponding
responsibilities from a business point of view. This includes User role concept overview, User role
documents - one per role, Consistent user role name and assignment to defined business
organization model, Corresponding SAP default roles, Mapping rules etc.
The purpose of this task is to define a logical data model for master or transactional data relevant
to the implementation scope across the application landscape, including both legacy and SAP
components.
This will help manage the data relationships and align interfaces correctly.
The purpose of the Detailed Design - Business Scenarios deliverable is the continuation of
process decomposition started in project preparation. This includes documentation of
requirements, solution design for the scenarios and processes. This information is populated in
the business process hierarchy in SAP Solution Manager.
The purpose of this task is to continue collecting input and finalize the Scenario Design Document,
in a format suitable for both communication purpose as well as for formal sign-off purpose. The
documented business scenario provides an understanding of the essential processes at the
scenario level (PL1-2). It also builds the foundation for the business blueprint phase where
process levels 35 are defined.
The purpose of this task is for the Product Owner team to decompose the initial product backlog
EPICS into more granular backlog items that the SCRUM teams can design, develop and deliver
in the sprint. The Product Backlog which consists of the following elements:
Vision and Business Case: Why do we want to do this? What is the value? What are current
pain points?
Detailed Business Process scope: What are the business scenarios and processes (down to
level 3) to be implemented?
Who will work with the processes and what are their primary business requirements? This will
be used as input for the definition of the user stories.
Priority of each backlog item
Estimated size and effort (the effort is estimated by the SCRUM team not the PO team)
Business Value
How to test the backlog item upon completion (e.g. definition of done for the feature)
The purpose of this deliverable is to design, in detail, the to-be business process down to activity
level (PL 3-5) and to describe gaps where the standard solution does not cover all required
functionalities.
The purpose of this task is to continue collecting input and finalize the Business Process Design
Document, in a format suitable for both communication purpose as well as for formal sign-off
purpose. The document provides details of the to-be business process down to activity level (PL 35) and describes the gaps where the standard solution does not cover all required functionalities.
The purpose of this task is to demonstrate standard functionality of the SAP solution to the
Product Owner and Key Users in order to solicit input and gain acceptance for the standard
feature. In case standard functionality needs to be enhanced product owner captures this
requirement in product backlog in the form of user story.
Features that are complex or time consuming to configure in the system can be presented in a
visualization tool like SAP Visualization by iRise to solicit input and gain acceptance of the feature
requirements.
The purpose of this task is to capture all identified delta requirements from the demo / visualization
sessions in the product backlog. The requirements are captured in form of user stories that define
the requirement from end-user perspective, provide details on how to test the feature when it is
completed, priority of the backlog item and business value. It is responsibility of Product Owner
team to maintain the product backlog and detail the user stories so they are understood by the
SCRUM team.
The purpose of Value Realization is to establish the sustainable mechanisms to monitor and
controls the predefined KPI's and PPI's of the to-be process and/or process changes.
The purpose of this task is to design the Value Dashboard by specifying the KPI's and PPI's and
how these are monitored and controlled during project execution and post Go-Live.
The purpose of this deliverable is to specify and detail how to realize the solution, both Core
Configuration and identified gaps and core enhancements needed to complement standard
functionality, in order to fulfill business requirements. These RICEFW objects are based on
process requirements, and they are specified in business process and solution design documents.
The purpose of this task is to complete the documentation for identified core configuration objects
related to business processes.
The purpose of this task is to complete the documentation for additionally identified configuration
objects related to business processes.
The purpose of this task is to complete the documentation for identified RICEFW objects.
These objects are classified as:
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-off for the baseline build (and visualizations)
and product backlog prior to proceeding to the Realization phase.
The purpose of this task is to demo the baseline build functionality and visualizations to the key
users and product owner team along with the product backlog to obtain acceptance of the
baseline build and product backlog.
The results of the demo is either acceptance of standard feature or in exceptional cases new delta
requirement that is captured in the form of user story in the product backlog. This demo is
conducted at the end of the Baseline Build to serve as an input to formal sign-off for the baseline
build.
The purpose of this task is for the key users and product owner team to conduct acceptance test
of the features built in the baseline build. This may also include walk-throughs of the visualizations
for features that have not been fully built in the system.
The purpose of this task is to complete documentation of the baseline build and capture it in SAP
Solution Manager. In particular this pertains to configuration documents, test cases, test scripts,
visualizations, etc. as defined in the project documentation standards defined in previous phase.
The purpose of this task is to formally signoff the baseline build, visualizations and product
backlog. This signals to the project team that they can proceed to the next phase to iteratively
build the features defined in product backlog.
The purpose of the legacy data migration deliverables is to develop the designs, plans, and
procedures to support the migration of legacy data during the implementation of the SAP
applications.
The purpose of this task is to ensure that defined processes and procedures needed to ensure
correct quality and handling of master data are operational in the organization.
This task ensures that provided master data for Assemble to order and/or Industrialized content,
can be utilized by the project.
The purpose of this task is to conduct a detailed analysis of legacy data in order to determine:
The availability and quality of existing data to support the SAP applications to be
implemented
The complexities and risks associated with the data and migration process
The purpose of this task is to design the specific architecture, programs, processes, and tasks
required to support the extraction, validation, harmonization, enrichment, and cleansing of the
legacy data.
The purpose of Manual Data Migration design is to develop the approach for manually bringing
legacy data into the SAP database when automated programs are not available or the data
volume does not justify the investment in developing such programs.
The purpose of the data quality plan is to define the metrics that track and monitor data quality
during the data migration process.
The purpose of data Security Design is to identify and develop the necessary architectural designs
and plans to support the security requirements.
The purpose of legacy data archive is to make legacy master data not considered currently active
available for reference in a format compatible with the master data formats of the SAP solution.
The purpose of this task is to establish the framework for legacy data archiving, meaning the
planning for usage of legacy-data archive objects, the legacy archive specifications, and data
retention rules for master-data archive objects.
The purpose of the Technical Solution Design deliverable is to provide a detailed technical and
integration design of the solution to be implemented, accounting for all decisions made during the
Business Blueprint phase including business process definitions, integration with external
systems, and physical server deployment.
The purpose of this task is to complete the technical infrastructure specification which provides a
technical description of the entire technology landscape from a physical standpoint, showing
where each of the SAP and non-SAP systems are installed, and the physical or virtual servers
assigned to each system along with their specifications
The purpose of this task is to define system environment that will be used for the baseline build. At
minimum the environment needs to have two systems Development and Quality Assurance. It is
recommended to also provide team with Sandbox environment where they can experiment with
the functionality during the baseline build.
The purpose of this deliverable is to ensure proper set up of a Roles and Authorizations procedure
and approach for the project.
The purpose of this task is to document the authorization requirements at the level of business
scenario and process, to evaluate chosen authorizations concepts against SAP standards and to
determine a feasible implementation approach.
The purpose of the development environment deliverable is to install a viable, correctly configured
technical development environment that is available for use by the project team to begin the
realization phase.
The purpose of this task is to install SAP components needed for the realization of project scope.
The purpose of this task is to upgrade SAP components needed for the realization of project
scope.
This task ensures that all solution documentation is made available for the project team.
Preferably the repository for this should be Solution Manager.
This task deals with the installation of 3rd party products needed to realize scope of the project.
The 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.
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.
Ensure that all required deliverables from this phase and the project are complete and
accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to collect knowledge assets and lessons learned at the end of each
phase of the project that can be reused later by other projects. Collecting documents,
experiences, project highlights and lessons learned throughout the duration of the project can help
to facilitate the project by providing quick access and insights into key deliverables from earlier
stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a quality check at critical
stages of the project. Project Quality Gates are an integral part of SAPs Quality Built In approach
for SAP primed, partner or client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been completed in
compliance with recommended practices and to the customers satisfaction
To enable project management to continuously communicate the process and build quality
directly into the project
The purpose of this task is to conduct retrospective meeting with the SCRUM team to identify
potential improvements of the SCRUM process. The objective of this task is to serve as
continuous improvement mechanism for the team to adjust to changing project environment and
needs. The team will select one or two key improvements to implement in the next iteration and
handles them as user stories that are added to the product backlog, prioritized and tracked along
with other user stories.
The purpose of this task is to execute a Project Management Review that provides a proactive
quality assurance review, with an impartial analysis of all aspects of the project across all project
management disciplines, enabling early detection of project issues with actionable
recommendations.
The purpose of this task is to execute a Design Review of SAP Solution service that provides a
proactive quality assurance review of the design of the SAP solution which is being implemented.
It delivers an impartial analysis of all aspects of the solution design across all relevant design
perspectives and leads to an early detection of potential solution risks and offers actionable risk
mitigation recommendations.
The purpose of this task is to ensure that each contract is closed by verifying that all work
specified in the contractual arrangement was completed, and that all defined deliverables were
accepted.
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:
Performance testing
The purpose of the phase initiation deliverable is to formally recognize that a new project phase
starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this task is to ensure the involvement of the team and other key resources and
their commitment to the project schedule. The meeting is also used to examine the approach for
the specific project phase.
The purpose of this deliverable is to initiate sprint in formal Sprint Planning Meeting.
The purpose of this task is to initiate sprint by selecting the set of user stories that will be
implemented in the sprint (scope of the sprint). During the sprint planning meeting the SCRUM
team estimates the stories and clarifies with product owner team any questions that may still
remain open. The team commits to deliver set of highest priority stories from the backlog. This
meeting formally sets the scope for the sprint. This meeting is conducted in the beginning of each
sprint.
The purpose of this deliverable is to execute the project management plan and control and
monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable Project
Management Plan) guide the approach to management, execution, and control of project
activities. The project manager is responsible for ensuring that the management plans are applied
at the appropriate level of control.
The purpose of this task is to update the project management plan and the subsidiary plans
based on the changes agreed during the projects change management process.
The purpose of this task is to ensure consistent planning, execution and monitoring of sprint
activities. This includes:
Team Activities
The team performs their sprint tasks as to the sprint backlog, taking priority and done criteria into
account
The team attends the Daily Standup Meeting. The Daily Standup Meeting serves for
information exchange among the team members. It should not exceed 15 minutes and occurs
same time same place each day. After the meeting, the team updates the sprint backlog (what are
remaining tasks and efforts). For more information please refer to the Scrum Meeting Guidelines.
Scrumof Scrum Meetings are conducted to coordinate the work between different scrum teams.
Scrum of Scrum meetings allow teams to discuss their work, focusing especially on areas of
overlap and integration. For more information please refer to the Scrum Meeting Guidelines
Product Owner Activities
Prepares readystate user stories for the next sprint(s).
Aligns expectations and requirements with his business stakeholders.
Is available for answering questions from the team.
Scrum Master Activities
Makes sure that the Scrum process is followed (organizing and facilitating Daily Scrums, daily
updates of remaining tasks and effort by team, organization of sprint review and retrospective
meetings)
Solves blocks and supports team, including escalation.
Ensures that management or others do not influence team.
The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks and changes related
to those e.g. changes of project scope, timeline, costs etc.
The purpose of this activity to make sure that project stakeholders are aware of status and
progress of the project including potential disturbances due to existing risks and issues.
SCRUM of SCRUMs Meeting is conducted to coordinate the work between different project
SCRUM teams. SCRUM of SCRUMs meetings allow teams to discuss their work, focusing
especially on areas of overlap and integration. The meeting cadence is defined for the entire
project and follows the same structure. Some teams conduct daily SCRUM of SCRUMs meeting
while others consider weekly meeting sufficient. The main driver for the meeting cadence is the
level of collaboration between the individual SCRUM teams and level of dependencies between
the features built in each SCRUM team.
The purpose of Organizational Alignment is to ensure a smooth transition process towards the
new way of working. This includes the alignment of roles and responsibilities and activities to
ensure that all employees are fully aligned to the goals of the project and organization.
The purpose of this task is to use the results from previous change impact analysis and the role
mapping information (mapping of new business user roles to existing roles and organizational
structure) and determine an appropriate transition approach for the business.
The purpose of this task is to get to get complex organizational feedback regarding the progress
and acceptance of the project from the customers view.
The purpose of this task is to communicate the scope and plan for the sprint to the users outside
of the core project team. This may include end users, key stakeholders, people external to the
project that have interest in information about the project plans and progress.
The purpose of this task is to communicate the sprint results to the users outside of the core
project team. This may include end users, key stakeholders, people external to the project that
have interest in information about the progress of the project and accomplishments of the project
team.
The purpose of this task is update communication plan and execute accordingly
The purpose of this deliverable is to determine the potential issues with the SAP education
strategy and solution before they impact the quality of the SAP software deployment.
The purpose of this task is to capture feedback on both the training strategy and approach,
determine issues and propose resolutions for identified issues.
The purpose of the deliverable End User Training Content Enabled is to ensure availability of end
user training material, training environment, logistics infrastructure and skilled instructors.
This task ensures a consistent appearance of the training materials and documentation by
providing the development team with standard templates.
The purpose of this task is to ensure that the training environment is correctly populated with
correct data for training.
The purpose of this task is to provide a detailed outline of presentations and activities that serve to
educate and prepare the trainers scheduled to instruct end-user training classes
The purpose of this task is to prepare the execution of end-user training by mapping end users to
appropriate training courses, developing a training schedule and logistics plan, and inviting end
users to courses
The purpose of the Configured General Settings and Organizational Structure deliverable is to
complete and document the initial configuration of the system on the basis of the decisions made
in the business blueprint phase.
The purpose of this task is to implement the configuration related to general settings, and to
document this in Solution Manager.
The purpose of this task is to implement the configuration related to organizational structure, and
to document this in Solution Manager.
The purpose of the Configured Master Data Objects 1-n deliverable is to configure the master data
in the SAP software system according to the business process requirements specified in the
business blueprint phase.
The purpose of this task is to prepare master data required for all business processes' unit and
string tests in DEV.
The purpose of this task is to complete configuration of master data in the system
The purpose of the Core Configuration and Documentation deliverable is to ensure that the
configuration is implemented, tested and documented.
The purpose of this task is to implement the Core Configuration, write valid test cases and to
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.
The purpose of the Delta Configuration deliverable is to ensure that the configuration is
implemented, tested and documented.
The purpose of this task is to implement the Delta Configuration, write valid test cases and to
document this in Solution Manager.
The objective of this task is to develop process documentation for any changed processes or for
any new processes added to the standard.
The objective of this task is to develop process test cases for any changed processes or for any
new processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration
The objective of this task is to resolve any issues identified during the Unit and String Test. It is
crucial that the issues are re-tested by users that reported them (or designated re-testers) and that
they are confirmed.
The purpose of this deliverable is to develop and test the RICEFW objects. Documentation to be
stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the functional specification,
The purpose of this task is to document the RICEFW object information in a technical specification
and define the appropriate test case(s). Documentation is stored in Solution Manager.
The purpose of this task is to perform unit and string test of the developments.
The objective of this task is to resolve any issues identified during the RICEFW object(s) Test. It is
crucial that the issues are re-tested by users that reported them (or designated re-testers) and that
they are confirmed.
The purpose of this task is to perform final code review of the development objects and confirm
readiness for transport into QAS.
The purpose of the Business Process Procedures deliverable is to provide the basis for end-user
training, end-user training documentation and test case creation. The procedures may also be
used by security to develop roles and authorizations.
The purpose of this task is to validate and complete Business Process Procedures from the
blueprint phase.
The purpose of this task is to validate and complete Business Process Procedures from the
blueprint phase.
The purpose of the value audit deliverable during the realization phase is to monitor and control
the implementation of key process changes and value enablers, as well as to ensure the design
and implementation of the Value Dashboard for KPI tracking purposes.
The purpose of this task is to perform value audit according to defined Value Dashboard, and
provide mitigation strategies for identified risks that could jeopardize the value identified during the
business case development.
The purpose of this deliverable is to provide evidence that the scenarios designed can be
supported by the solution implemented.
The purpose of this task is to identify and document applicable test case(s) for the scenario.
The purpose of this task is to perform scenario test.
The objective of this task is to resolve any issues identified during the scenario testing. It is crucial
that the issues are re-tested by users that reported them (or designated re-testers) and that they
are confirmed.
The purpose of the quality assurance infrastructure and environment design and setup deliverable
is to install a viable, correctly configured technical QA environment that is available for use by the
project team to perform QA testing.
The purpose of this task is to install SAP components needed for the realization of project scope.
The purpose of this task is to upgrade SAP components needed for the realization of project
scope.
The purpose of this task is to build the quality assurance (QA) environment with changes that
have been unit-tested and released from the development environment.
The purpose of this task is to set up users in the Quality Assurance environment.
The purpose of this task is to prepare master data required for all business processes in QAS.
The objective of this task is to perform any remaining manual configuration changes in the Quality
Assurance environment.
This milestone signifies completion of Build activities and transition to Integration Testing, User
Acceptance Testing and Non-Functional Testing
The purpose of this deliverable is to formally close the sprint by conducting the Sprint Review
Meeting with key users, product owner group and key stakeholders; formally sign-off the results
and conduct sprint retrospective.
The purpose of this task is to demonstrate the results of the sprint to product owner team, key
users and key project stakeholders. The results of the demo is either acceptance of backlog item
or in cases the feature is not accepted the user story is amended by the product owner team,
prioritized and remains in the product backlog ready for next sprint planning meeting.
The demo in sprint review meeting serves as an input to formal sign-off for the sprint.
The purpose of this task is to obtain formal acceptance and signoff of the sprint results following
the sprint review meeting. The product owner team is the party that provides the sign-off to the
project team. In case some features are not accepted they are brought back into the product
backlog as requirement, properly prioritized and included in planning for next sprint.
The purpose of this task is to conduct retrospective meeting with the SCRUM team to identify
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 the preliminary cutover plan deliverable is to document the strategy, scope and
timelines for moving from the as-is solution to the to-be solution and the hyper care period
immediately following go-live.
The purpose of this task is to assess to what level the organization is prepared for the cut
over/transition
This purpose of this task is to check to what extent the support organization is operational and
ready for cut over
This task checks that proper governance of master data quality is defined.
The purpose of the preliminary cutover plan task is to document the strategy, scope and timelines
for moving from the as-is solution to the to-be solution and the hyper care period immediately
following go-live. This includes documenting activities such as the transfer of data from the legacy
systems to the SAP software production system, setting up and initializing the production system,
closing the legacy systems, manually entering certain data in the new system, setting up and
verifying interface connections, importing transports and all manual configurations.
The purpose of the review of the preliminary cutover plan is to validate the plan for completeness,
dependencies, timing and other constraints. At the end of the review the project team will have
understanding of necessary adjustments to the preliminary cutover plan.
The purpose of this task is to refine the preliminary cutover plan based on information the project
team learned in the cutover plan review with customer.
The purpose of Approved Integration Test is to ensure functional correctness. It test the
integration of SAP solutions with non-SAP applications and interfaces and can be executed in an
iterative manner.
The purpose of this task is to define and document integration test cases, end-to-end customer
business process scenarios, according to the test plan. Test plans and test case documentation is
stored in Solution Manager.
The purpose of this task is to document the integration test case outlined in the integration test
plan
The objective of this task is to perform the Integration test according to previously defined plan.
During the test all issues must be logged and documented in the system for traceability purpose.
The objective of this task is to resolve any issues identified during the Integration Test. It is crucial
that the issues are re-tested by users that reported them (or designated re-testers) and that they
are confirmed.
The purpose of this task is to obtain customer approval (sign-off) of the integration test.
The purpose of the legacy data migration deliverable is to develop, implement, and test the data
migration programs and processes defined in the business blueprint phase. This activity consists
of iterative development and testing cycles focused on the analysis of data, refinement of business
rules, and deployment of migration programs and processes designed to move, cleanse,
transform, and enrich legacy data required to support the various test cycles and ultimately the
production cutover. The test cycles enable the migration team to improve data quality to an
acceptable production level, develop a detailed cutover sequencing plan, and exercise data
reconciliation and validation processes required to support the production cutover.
The purpose of this task is develop the specific architecture, programs, and processes that
support the extraction, validation, harmonization, enrichment, and cleansing of the legacy data.
The purpose of this task is to execute and validate the manual conversion as described in the
manual data migration approach
The purpose of this task is to visualize the data quality metrics defined in the data quality plan
The purpose of this task is to load the cleansed legacy data into the SAP software target
structures using a standard SAP load utility such as LSMW.
The purpose of this task is to obtain the results of the various test cycles so the team can monitor
the accuracy and efficiency of the data migration solution.
The purpose of this task is to provide one final assessment at the end of the realization phase to
report on the quality of the converted legacy data
The purpose of this deliverable is to execute the User acceptance test (UAT). This is the last test
cycle of an SAP solution implementation and is an essential part of gaining end-user acceptance
of the software system.
The purpose of this task is to define and document UAT test cases according to the test plan. Test
plans and test case documentation is stored in Solution Manager
The purpose of this task is to document the integration test case outlined in the UAT test plan
The objective of this task is to perform the End User Acceptance test according to previously
defined plan. During the test all issues must be logged and documented in the system for
traceability purpose.
The objective of this task is to resolve any issues identified during the User Acceptance Test. It is
crucial that the issues are re-tested by users that reported them (or designated re-testers) and that
they are confirmed.
The purpose of this task is to execute the testing, document the results and obtain customer
approval (sign-off)
The purpose of the SAP data archiving deliverable is to provide a method to check, remove, and
store data that has completed its lifecycle within the solution. Data that meets the check criteria of
data retention rules and is no longer actively used in the system can be archived and deleted.
Storage of the data is a secondary process to enable data that has been archived and deleted to
still be viewed and reported on even though the data is no longer stored on the transactional
system.
The purpose of this task is to identify legal and business retention requirements needed in prier to
establish the baseline for data arched and removal plan.
The purpose of this task is to develop the data archive plan that outlines the planning for data
archiving of the business objects at the customer site.
The purpose of this task is to develop the data archive storage plan needed for the execution of
each data archive run and creates the indexes for each archive execution.
The purpose of this task is to test the data archive implementation execution in QAS.
The purpose of the production infrastructure and environment design and setup deliverable is to
install a viable, correctly configured technical production environment to support productive
operations of the delivered solution.
The purpose of this task is to install and set up the production environment.
The purpose of this task is to build the production (PRD) environment with changes that have
been tested and released from the quality assurance (QA) environment.
The purpose of this task is to ensure that appropriate master data is available for testing in the
production environment (system test).
The purpose of this task is to prepare master data required for all business processes in PRD.
The purpose of this task is to perform any remaining manual configuration changes in the
production environment.
The purpose of this deliverable is to execute the setup of Availability and Continuity Management
(ACM)
The purpose of this task is to define the approach and plan for Availability and Continuity
Management.
The purpose of this task is to set and execute the identified failure scenarios.
The purpose of this task is to obtain the results from the failover scenario execution and determine
the appropriate mitigation actions for the test findings.
The purpose of planned Performance and System Test is to checks the entire system, consisting
of databases, applications servers, front ends, printers etc. The performance test measures the
throughput and response times of the system.
The task defines and documents the identified test cases related to system and performance test.
Outcome is documented in a test plan.
The task defines and documents the identified test cases related to system and performance test.
Outcome is documented in a test plan.
The purpose of this task is to document the test case outlined in the test plan
The purpose of this task is to document the test case outlined in the test plan
The purpose of this task is to execute the performance tests and present the findings for these
tests. The outcome should be formally approved by the customer.
The objective of this task is to resolve issues identified during the performance or load testing.
Upon resolution the issues need to be re-tested and confirmed by responsible testers.
The purpose of this service is to support the start of production of an SAP Solution. During this
service, SAP service engineers check the solution for potential risks and give recommendations
ensuring optimal performance and system availability for core business processes.
The purpose of this task is to perform the first session of the SAP GoingLive Check.
The service consiste of two sessions - Analysis and Verification, and includes:
- Verification of the technical capabilities of the production environment (sizing plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components and Plug-Ins
The purpose of the System User Roles and Authorization Administration deliverable is to establish
an effective operation processes for security
The purpose of this task is to set-up, document and execute the administrative procedure for
Roles and Authorizations.
The purpose of the technical operations and handover strategy deliverable is to update refine two
prior deliverables from the Business Blueprint phase, and prepare a strategy to hand off
operations of the solution landscape to the post-production support organization.
The purpose of this task is to ensure that proper staffing(people and competence) is in place for
the support org/team
The purpose of this task is to ensure that adequate support processes are in place for the Go Live
phase and beyond.
This task describes the considerations that are required to recognize and solve critical situations
during business process operation.
Ensure that all required deliverables from this phase and the project are complete and
accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to collect knowledge assets and lessons learned at the end of each
phase of the project that can be reused later by other projects. Collecting documents,
experiences, project highlights and lessons learned throughout the duration of the project can help
to facilitate the project by providing quick access and insights into key deliverables from earlier
stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a quality check at critical
stages of the project. Project Quality Gates are an integral part of SAPs Quality Built In approach
for SAP primed, partner or client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been completed in
compliance with recommended practices and to the customers satisfaction
To enable project management to continuously communicate the process and build quality
directly into the project
The purpose of Project Management Review is to provide a proactive quality assurance review,
with an impartial analysis of all aspects of the project across all project management disciplines,
enabling early detection of project issues with actionable recommendations.
The purpose of this task is to execute a Design Review of SAP Solution service that provides a
proactive quality assurance review of the design of the SAP solution which is being implemented.
It delivers an impartial analysis of all aspects of the solution design across all relevant design
perspectives and leads to an early detection of potential solution risks and offers actionable risk
mitigation recommendations.
The purpose of this task is to ensure that each contract is closed by verifying that all work
specified in the contractual arrangement was completed, and that all defined deliverables were
accepted.
The purpose of the final preparation phase is to finalize readiness of the solution and its
supporting tools and processes for production go live. This includes, but is not limited to,
system tests, end-user training, system management, and cutover activities (including data
migration). The phase deliverables also serve to enable the resolution of all crucial open
issues. On successful completion of this phase, the business is ready to run the live SAP
software system.
The purpose of the phase initiation deliverable is to formally recognize that a new project phase
starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this task is to ensure the involvement of the team and other key resources and
their commitment to the project schedule. The meeting is also used to examine the approach for
the specific project phase.
The purpose of this deliverable is to execute the project management plan and control and
monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable Project
Management Plan) guide the approach to management, execution, and control of project
activities. The project manager is responsible for ensuring that the management plans are applied
at the appropriate level of control.
The purpose of this task is to update the project management plan and the subsidiary plans
based on the changes agreed during the projects change management process.
The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks and changes related
to those e.g. changes of project scope, timeline, costs etc.
The purpose of this activity to make sure that project stakeholders are aware of status and
progress of the project including potential disturbances due to existing risks and issues.
The purpose of this survey is to take the pulse of the organization, prior to go-live, to determine the
general comfort level with the upcoming changes. If that comfort level is not there, it is critical to
determine where additional OCM work needs to be focused. In addition the check of production
support readiness is to ensure that the resources and processes are in place to support the
solution after cutover.
The purpose of this task is to validate the outcome of the role mapping and change impact
analysis. This is done with the impacted business stakeholders in order to gain sponsors approval.
The purpose of this task is to ensure the customer establishes the means to manage their data in
an integrated environment.
This task provide a single defined support approach for monitoring and measuring the customers
day-to-day support operations. The following four topics needs to be covered:
- Exception Handling and Business Process and Interface Monitoring
- Data Volume Management
- Job Scheduling Management
- Transactional Consistency and Data Integrity
This task describes how all SAP technologies can be administered to run a customer solution
efficiently. The execution is mainly done locally but can be triggered and managed from a central
administration system.
The task ensure that the customer establishes the means to manage security, roles and
authorizations in their productive environment.
The purpose of this task is to extract the knowledge about the scope, customizations, and
business processes of the customers production environment and transfer that knowledge to a
long-term SAP support center
The purpose of the EU training delivery and readiness checklist is to provide a checklist
summarizing end-user training delivery to ensure readiness for adoption of the solution. In the
checklist, items governing training delivery, communications, and future planning clarify the status
of all aspects of the training initiative.
The objective of this task is to deliver end user training to identified end user groups according to
the previously developed training schedule.
The purpose of this task is to capture feedback on both the training session and the trainer
delivering the material
This task checks how prepared the people in the organization are with regards to the identified
changes and received EU training.
The purpose of this deliverable is to present the findings and recommendations from the results of
technical tests such as disaster recovery tests, backup and restore tests, and other required
technical or basis-related tests to the customer or project team for final signoff in order to exit
system testing.
The purpose of this task is to prepare and execute the system tests. The outcome/results should
be approved by the customer.
The objective of this task is to resolve issues identified during the system testing. Upon resolution
the issues need to be re-tested and confirmed by responsible testers.
Purpose of this task is to obtain customer approval (sign-off)
The purpose of production cutover is to perform the cutover to the production software and go live.
At this point, the organizational, business, functional, technical, and system aspects of the project
are ready to be used in production.
The purpose of this task is to rehearse or simulate the cutover activities. During simulation, the
main objective is to validate and document the tasks, sequence, and duration of items on the
cutover plan.
This task verifies that master data support is set up and process is operational
The purpose of this task is to complete the Cut Over plan with results obtained from the Go Live
simulations.
The objective of this task is to perform all the cutover preparation activities remaining to be closed
prior to cutover weekend. The detailed cutover plan contains the complete listing of all pre-cutover
activities, their dependencies, owners, and timing.
This task will confirm that the productive system is ready for Go Live.
The purpose of this task is the loading of production data from legacy systems into the production
environment. Once all preparations and configurations on both the technical and application levels
are completed, the final productive solution can be set up and data loaded. The solution is live in a
production environment
Purpose of this task is to 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 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 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.
Ensure that all required deliverables from this phase and the project are complete and
accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to collect knowledge assets and lessons learned at the end of each
phase of the project that can be reused later by other projects. Collecting documents,
experiences, project highlights and lessons learned throughout the duration of the project can help
to facilitate the project by providing quick access and insights into key deliverables from earlier
stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a quality check at critical
stages of the project. Project Quality Gates are an integral part of SAPs Quality Built In approach
for SAP primed, partner or client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been completed in
compliance with recommended practices and to the customers satisfaction
To enable project management to continuously communicate the process and build quality
directly into the project
The purpose of Project Management Review is to provide a proactive quality assurance review,
with an impartial analysis of all aspects of the project across all project management disciplines,
enabling early detection of project issues with actionable recommendations.
The purpose of this task is to ensure that each contract is closed by verifying that all work
specified in the contractual arrangement was completed, and that all defined deliverables were
accepted.
This milestone signifies formal transition to production environment. Production is up and running,
cutover sustainment activities, end-user on-boarding and support are under way.
The purpose of this phase is to provide support for the solution during the period
immediately following production cutover. Exceptional items such as additional production
support, exceptional business monitoring processes, and extraordinary technical support
are planned and executed in this phase. At the end of the designated extra-care period,
sustaining production support processes planned in final preparation and executed as part
of go-live support become the core support for continuous improvement in the ongoing
solution.
The purpose of the phase initiation deliverable is to formally recognize that a new project phase
starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this task is to ensure the involvement of the team and other key resources and
their commitment to the project schedule. The meeting is also used to examine the approach for
the specific project phase.
The purpose of this deliverable is to execute the project management plan and control and
monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable Project
Management Plan) guide the approach to management, execution, and control of project
activities. The project manager is responsible for ensuring that the management plans are applied
at the appropriate level of control.
The purpose of this task is to update the project management plan and the subsidiary plans
based on the changes agreed during the projects change management process.
The purpose of this activity is to assure that the project is executed according to what was agreed
to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled project
activities (and tasks) and that work is progressing and deliverables are produced as expected.
The purpose of this activity is to capture and manage project issues and risks and changes related
to those e.g. changes of project scope, timeline, costs etc.
The purpose of this activity to make sure that project stakeholders are aware of status and
progress of the project including potential disturbances due to existing risks and issues.
The purpose of EU training during go-live support is to ensure that end users have adopted the
solution, knowledge resources are maintained, and responses to the end-user acceptance survey
are positive.
This purpose of this task is to adapt available training material and make it suitable for End User
training.
This task executes the delivery of EU training as well as capturing feedback on both the training
session and the trainer.
The purpose of this task is to capture feedback on both the training session and the trainer
delivering the material
This task checks how prepared the people in the organization are with regards to the identified
changes and received EU training.
The purpose of the production support and transfer to solution deliverable is to confirm that the
resources and processes are in place to support the ongoing solution and to complete the steps
required to close the project and finish documentation.
The purpose of this task is to verify that the requirements identified in earlier sessions are met.
The purpose of the production support and transfer to solution deliverable is to confirm that the
resources and processes are in place to support the ongoing solution and to complete the steps
required to close the project and finish documentation.
The purpose of this task is to implement ongoing production support to the SAP software system
users and to monitor and optimize system performance.
The purpose of this activity is to achieve a closure of all open project issues which is a prerequisite
for the final project closure.
The objective of this task is to resolve any functional issues identified during the hyper care period
after cutover. It is crucial that the issues are re-tested and confirmed by users that reported them.
The objective of this task is to resolve any technical issues identified during the hyper care period
after cutover. It is crucial that the issues are re-tested and confirmed by users that reported them.
The purpose of this task is to ensure knowledge transfer regarding the scope, customizations, and
business processes in the customers production environments to the longterm SAP support
center team.
Purpose of this task is to hand over the finalized implementation project and it's content, and set
up as a productive solution in SAP Solution Manager. This provides the basis for the follow up
activities in the Operate Phase.
This milestone signifies formal transition from post production sustainment support to long term
support and operation of the new environment
Ensure that all required deliverables from this phase and the project are complete and
accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to collect knowledge assets and lessons learned at the end of each
phase of the project that can be reused later by other projects. Collecting documents,
experiences, project highlights and lessons learned throughout the duration of the project can help
to facilitate the project by providing quick access and insights into key deliverables from earlier
stages of the project.
The purpose of this task is to pass the Project Quality Gate by conducting a quality check at critical
stages of the project. Project Quality Gates are an integral part of SAPs Quality Built In approach
for SAP primed, partner or client led projects. The objectives of the Project Quality Gate are:
To assure that all key deliverables and actions of the gate have been completed in
compliance with recommended practices and to the customers satisfaction
To enable project management to continuously communicate the process and build quality
directly into the project
The purpose of Project Management Review is to provide a proactive quality assurance review,
with an impartial analysis of all aspects of the project across all project management disciplines,
enabling early detection of project issues with actionable recommendations.
The purpose of this task is to ensure that each contract is closed by verifying that all work
specified in the contractual arrangement was completed, and that all defined deliverables were
accepted.
The purpose of this activity is to achieve a closure of all open project issues which is a prerequisite
for the final project closure.
The purpose of this activity is to document the results of the project, both regarding achieved
objectives, deliverables as well as adherence to schedule, costs and delivered value.
The purpose of this activity is to formally close the project by obtaining customer signatures on
dedicated deliverables/documents e.g. Project Quality Gate, Project Closeout Report
Solution operations are initially set up during the implementation project. The primary goal
of this phase is to further optimize and automate the operability of the solution. Operability
is the ability to maintain IT systems in a functioning and operating condition, guaranteeing
systems availability and required performance levels to support the execution of the
enterprises business operations.
The Operations Maturity Assessment evaluates the SAP customer's support operations to
determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements for operations and to
define what aspects of the operations need to be adjusted, enhanced or implemented.
The report should detail assessment results and finding, including proposed actions for how to
bridge identified gaps.
Centrally document and relate business processes and technical information of SAP and non-SAP
Solutions ensuring transparency, efficient maintenance and collaboration
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Solution
Documentations area.
Represents the identification, adaptation and implementation of new and enhanced future-proof
business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical installation from
business innovation
Uses the SAP Solution Manager to implement the innovation in the system landscape
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Solution
Implementation area.
The template management approach allows customers with multi-site SAP installations to
efficiently manage their business processes across geographical distances from initial template
definition to template implementation and template optimization, for example as part of a global
rollout
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Template
Management area.
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Test Management
area.
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Change Control
Management area.
Enables a centralized and common incident and issue message processing in multiple
organization levels
Offers a communication channel with all relevant stakeholders of an incident. The process
includes business user, SAP experts@customer, SAP Service&Support and Partner Support
employees.
Is integrated in all ALM processes of SAP Solution Manager, in any SAP Business Suite solution
and could be connected to an Non-SAP Help Desk application
Includes follow up activities as knowledge research, root cause analysis or Change Management
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Incident Management
area.
Represents all capabilities for monitoring, alerting, analysis and administration of SAP solutions
Allows customers to reduce TCO by predefined content and centralized tools for all aspects of
operations in SAP Solution Manager
Provides End-to-End reporting functionality either out-of-the-box or individually created by
customers
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Technical Operations
area.
SAP Business Process Integration & Automation Management (BPIAM) comprises the most
important application related operations topics necessary to ensure the smooth and reliable flow of
the core business processes to meet a company's business requirements.
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Process Operations
area.
SAP Notes provide a solution for known issues. SAP Notes are usually applied upon request (e.g.
current incident in productive environment, information from SAP about potential issue (Hot News,
Security Notes)).
SAP Notes are collected and released as Support Packages. Support Packages are applied to
SAP solutions to comply with legal requirements or run on latest technology.
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Maintenance
Management area.
Is the identification, adaptation and implementation of new and enhanced business and technical
scenarios
Uses the SAP Solution Manager to manage the upgrade project holistically and effectively end-toend
Allows SAP customers to better understand and manage the major technical risks and challenges
in an upgrade project, and to make the upgrade project a nonevent for the business.
Re-visit result of ALM roadmap workshop from the project preparation, lessons learned findings
from the implementation project and determine if potential gaps exist for the Upgrade
Management area.
Q-Gate
Relevant
Work Stream
Accountable Role
_Phase
PM - Project Management
Mandatory
PM - Project Management
Project Manager
Project Manager
PM - Project Management
Mandatory
Project Charter
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Mandatory
PM - Project Management
Project Manager
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
PM - Project Management
Application Consultant
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Mandatory
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Business Consultant
Optional
Software System
Configuration Standards,
Enhancement and
Modification Standards
Business Consultant
Application Consultant
Optional
Test Management
Consultant
Optional
Application Consultant
Application Consultant
Optional
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Project Manager
Mandatory
Project Manager
Optional
OCM Roadmap
Business Consultant
Training - Training
Optional
Education Consultant
Training - Training
PM - Project Management
Mandatory
Project Manager
Application Consultant
Application Consultant
Optional
Optional
Value Map
Application Consultant
Application Consultant
Application Consultant
Application Consultant
VM - Value Management
VM - Value Management
Business Consultant
PM - Project Management
Application Consultant
VM - Value Management
Business Consultant
Business Consultant
Application Consultant
Application Consultant
Optional
Technology Consultant
Project Manager
DM - Data Migration
DM - Data Migration
Application Consultant
DM - Data Migration
Technology Architect
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Technology Architect
Optional
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Solution Architect
Technology Architect
Technology Architect
Optional
Solution Architect
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
PM - Project Management
Optional
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Mandatory
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Project Manager
Mandatory
Project Manager
Optional
Optional
Optional
Stakeholder Analysis
(Internal)
Organizational Change
Management Plan
Business Readiness
Approach
Business Consultant
Education Consultant
Business Consultant
Business Consultant
Business Consultant
Business Consultant
Mandatory
Optional
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Training - Training
Business Consultant
Training - Training
Instructor
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Application Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Application Consultant
Mandatory
Mandatory
Business Blueprint
Documents(Org Structure)
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Mandatory
Mandatory
Solution Documentation
Solution Documentation
Application Consultant
PM - Project Management
Application Consultant
Application Consultant
Optional
Application Consultant
PM - Project Management
Application Consultant
VM - Value Management
VM - Value Management
Mandatory
Development list(incl.
RICEFW, SOA, Migration)
Business Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Integration Development
Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Application Consultant
PM - Project Management
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Mandatory
Mandatory
Application Consultant
Project Manager
Application Consultant
Project Manager
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DA - Data Archiving
DA - Data Archiving
Technology Architect
Technology Architect
Technology Architect
Mandatory
Authorization Requirements
and Design
Mandatory
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Mandatory
Technology Consultant
Technology Consultant
Technology Consultant
PM - Project Management
PM - Project Management
Application Consultant
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Optional
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Mandatory
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Project Manager
PM - Project Management
Application Consultant
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Project Manager
Mandatory
Project Manager
PM - Project Management
Project Manager
Optional
Business Consultant
Business Consultant
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Business Consultant
Training - Training
Training - Training
Optional
Optional
Training Environment
Population and Testing
Education Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Education Consultant
Optional
Mandatory
Education Coordinator
Application Consultant
Application Consultant
Mandatory
Mandatory
Optional
Optional
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Mandatory
Optional
Mandatory
Optional
Development list(incl.
RICEFW, SOA, Migration)
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Optional
Application Consultant
Application Consultant
VM - Value Management
VM - Value Management
Business Consultant
Optional
Mandatory
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
Application Consultant
_Milestone
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Optional
Business Readiness
Approach
Project Manager
Project Manager
DM - Data Migration
Application Consultant
Mandatory
Mandatory
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Mandatory
DM - Data Migration
Application Consultant
Mandatory
DM - Data Migration
Technology Architect
Mandatory
Mandatory
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Project Manager
DA - Data Archiving
DA - Data Archiving
Technology Architect
Mandatory
Optional
Failover Environment
Design, Setup and Test
Results
DA - Data Archiving
Application Consultant
DA - Data Archiving
Application Consultant
DA - Data Archiving
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Application Consultant
Technology Architect
Mandatory
Optional
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Test Management
Consultant
Application Consultant
Technology Consultant
Technology Consultant
Optional
Optional
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Mandatory
Optional
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Mandatory
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Project Manager
Mandatory
Project Manager
Optional
Functional/Technical
Requirements and
Production Support
Processes Defined
Business Consultant
Optional
DM - Data Migration
Application Consultant
Optional
Technology Consultant
Optional
Technology Consultant
Optional
Technology Consultant
Optional
Transition to Support
Technology Consultant
Training - Training
Training - Training
Education Coordinator
Training - Training
Education Consultant
Optional
Training Evaluations
Training - Training
Education Coordinator
Optional
Education Consultant
Technology Consultant
Application Consultant
Technology Consultant
Mandatory
Mandatory
Mandatory
Application Consultant
Optional
Mandatory
Optional
PM - Project Management
PM - Project Management
Application Consultant
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Optional
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Mandatory
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Mandatory
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Mandatory
Project Manager
Mandatory
Project Manager
Optional
Training - Training
Training - Training
Education Consultant
Training - Training
Education Consultant
Training - Training
Education Coordinator
Education Consultant
Optional
Optional
Transition to Standard
Support Processes, System
Administration and Control
Technology Consultant
Optional
Technology Consultant
PM - Project Management
Project Manager
_Milestone
Mandatory
Optional
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
PM - Project Management
Business Consultant
PM - Project Management
Project Manager
Application Consultant
Technology Consultant
Technology Consultant
Test Management
Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant
Project Preparation
1 1
Project Initiation
1 1
1 1
1 1
1 2
1 2
1 2
1 2
1 3
Project Charter
1 3
1 3
2 Identify Stakeholders
1 3
1 4
Kick-Off Workshop
1 4
1 4
1 5
Scope Statement
1 5
1 5
1 6
1 6
1 6
1 6
1 6
1 6
1 7
1 7
1 8
1 8
1 8
1 8
1 8
1 9
1 9
1 9
1 9
1 9
1 10
1 10 1
1 11
1 13
1 14
1 14 1
1 14 2
1 15
1 16
Interface Inventory
1 18
1 18 1
1 18 5
Install SAP Best Practices solution builder content addon, installation data and solution file
1 18 8
1 18 9
1 19
Demo Environment
1 19 1
1 19 2
1 19 3
Perform post activation tasks related to the PreAssembled Rapid Deployment Solution
1 20
1 21
Scope Validation
2 1
Phase Initiation
2 1
2 2
2 2
2 2
2 2
2 2
2 2
2 2
2 3
Stakeholder Analysis
2 3
2 3
2 4
2 4
2 4
2 5
2 5
2 5
2 6
2 6
2 7
2 7
Scope Validation
2 7
2 7
2 7
2 7
2 8
2 8
2 8
2 9
2 9
2 10
2 10 1
2 11
Testing Strategy
2 11 1
2 12
2 13
Realization
3 1
Phase Initiation
3 1
3 2
3 2
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 4
3 4
Organizational Alignment
3 5
3 5
Knowledge Transfer
1
3 5
3 5
3 6
3 6
3 7
3 7
3 7
3 8
3 8
3 9
3 9
3 10
3 11
3 12
3 13
3 14
3 15
3 15 1
3 15 2
3 17
3 18
3 18 1
3 19
3 20 4
3 21 3
3 21 4
3 22
3 23
3 23 1
3 24
3 25
Final Preparation
4 1
Phase Initiation
4 1
4 2
4 2
4 2
4 2
4 2
4 3
4 3
4 4
4 4
4 5
Production Cutover
4 5
4 5
4 5
4 5
4 5
4 5
4 5
4 6
4 6
4 7
Go Live Support
5 1
Phase Initiation
5 1
5 2
5 2
5 3
5 3
5 3
5 4
5 4
5 5
5 5
5 6
5 7
Improvement Roadmap
Perform Refinement & Improvement Planning
Workshops
5 7
5 7
5 8
5 8
5 8
5 8
5 8
5 8
Operate
6 1
6 1
6 1
6 2
6 2
6 3
6 3
6 4
6 4
6 5
6 5
6 6
6 6
6 7
6 7
6 8
6 8
6 9
6 9
6 10
6 10 1
6 11
Description
Q-Gate Relevant
This phase provides initial planning and preparation for the project. Although
each project has its own unique objectives, scope, and priorities, the
deliverables outlined below assist in completing the initiation and planning
steps in an efficient and effective manner.
The purpose of this project initiation deliverable is to formally recognize that a new
project exists. It supports the decision to accept the project, align stakeholders
such as clients, customers, and SAP management around a project and its scope,
provide updated information for planning, and obtain a commitment to proceed. It
ensures alignment between SAP, the customers strategic direction, and the
satisfaction of operational requirements.
The purpose of phase resources allocation is a confirmation of resource availability
for the particular phase.
The purpose of this activity is to prepare the onboarding package for external
Mandatory
consultants from SAP and partner companies.
The purpose of this task is to communicate the delivery model and ensure that the
appropriate mobility arrangements have been made for the consultants
The purpose of this deliverable is to ensure that an efficient management framework
is in place for successful project execution.
The purpose of this task is to define the organizational structure, roles and
responsibilities of the project team.
Mandatory
The purpose of this task is to identify and select global company and external
resources for the project in accordance with the required roles, skills and
responsibilities specified in the preceding task. The assignment of people to roles
should also take into account their qualifications and availability for the whole project
time frame.
The purpose of this task is to complete the communications management plan. This
document outlines the processes required to ensure timely generation, distribution,
storage, and retrieval of project information.
The purpose of this deliverable is to clearly and explicitly define the objectives of the
proposed project, analyze all possible benefits and quantify benefits in financial
Mandatory
terms. This information and supporting documents align key stakeholders around the
strategic intent of the project.
The purpose of this activity is to collect all input required for the project charter and
document it into a format suitable for both communication purpose as for formal signoff purpose, if possible utilizing the accelerator file(s) provided
The purpose of this activity is to ensure that the correct groupings of stakeholders
have been identified for the project.
The purpose of this activity is to achieve a formal sign-off of the project charter.
The purpose of this deliverable is to kick-off the project/phase and ensure that all
needed information is shared with the resources for a successful project execution.
Mandatory
The purpose of this task is to prepare the kickoff meeting which will helps ensure the
involvement of the team and other key resources and their commitment to the project
schedule.
The purpose of this activity is to gather the whole project team, including all remotely
involved resources, to kick-off the project or project phase. The meeting is also used
to examine the approach for the specific project phase.
The purpose of this deliverable is to facilitate an initial understanding of the project
scope and associated project-related assumptions and constraints. The project
scope statement evolves through the initiation and planning of the project and clearly
Mandatory
and explicitly defines the deliverables of the proposed project. This information and
supporting documents align key stakeholders around what the project is going to
deliver.
The objective of this task is to review the scope statement document with the
customer project manager and key stakeholders in order to confirm the scope and
obtain approval.
The purpose of this activity is to clearly define the acceptance criteria against which
project deliverables and results are measured that have been listed in the Scope
Statement. These should also be updated in the Project Quality Gate Scorecard. In
the context of Agile projects this translates to the definition of Done for the backlog
items that are being delivered in the project.
The purpose of the Project Schedule deliverable is to define the work schedule to be
followed, the resources and associated time commitments required for the project
and the phases of the project. The work breakdown structure (WBS) serves as the
foundation for the schedule, the deliverables to be produced and tasks to be
performed, as part of the project. The project budget, including monitoring and
control, outlines all costs associated with the project, including labor, hardware,
software, contracting fees, and facilities.
At a minimum, the schedule should include:
Deliverables and tasks for the current phase
Estimated effort (work) and duration
Task dependencies (such as predecessors and successors)
Scheduled start and finish dates for each task, based on dependencies
Task constraints (such as must-start-on date and must-finish-on date)
Resources assigned to each task
High-level schedule for subsequent phases
The purpose of this activity is to create the project/phase schedule and assign
resources to the scheduled activities and tasks.
Mandatory
The purpose of this task is to define a high level release plan, determine the length
and number of sprints per release. During this activity the project team needs to take
into accounts business needs, project objectives & goals, available technical
environment, complexity of the solution, geographical and organizational scope of
the project and other aspects (like seasonality of customer's business). The outcome
of this task is high level release plan that includes key features targeted in each
release and number/duration of sprints (note that the sprint duration should be fixed
for all project teams and should not vary).
The purpose of this activity is to extract all planned workshops during the
project/phase into a schedule that facilitates workshop planning
Purpose of this task is to obtain customer approval (sign-off)
The purpose of this activity is to create project schedule and cost baseline against
Mandatory
which tracking, change management and status reporting is done.
The purpose of the project management plan deliverable is to develop the project
management plan and the subsidiary plans on the basis of the project scope defined Mandatory
in the project charter.
The purpose of this activity is to collect input needed for the project management
plan and document it in a format suitable for both communication purpose as for
formal sign-off purpose, if possible utilizing the accelerator file(s) provided
The purpose of the Project and Operational Standards deliverable is to provide
consistent means of executing and governing project work in an efficient and
effective manner. The key objective of Project Standards is to identify, define,
approve, and communicate standards related to project execution.
Where and when applicable, the current customer processes and procedures,
related to the project standards should be taken into account when defining the most
suitable standards for the project.
The purpose of this task is to determine the customers framework to centrally
document and relate business processes and technical information of SAP and nonMandatory
SAP Solutions in Solution Manager, ensuring transparency, efficient maintenance
and collaboration
The purpose of this task, also known as Innovation Management, is to determine the
customers approach for the identification, adaptation and implementation of new and
enhanced business and technical scenarios. It is part of the application lifecycle and
Optional
designed to decouple technical installation from business innovation using SAP
Solution Manager to implement the innovation in the system landscape.
The purpose of this task is to determine the customers approach for managing
functional and performance testing of SAP-centric business processes to ensure
validated system behavior after software change events.
The purpose of this task is to determine the customers approach of handling
business and technology-driven changes, using a standardized process leading to
improved reliability of solution and minimized risk through segregation of duties and
transparency of changes.
Optional
Optional
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable
Project Management Plan) guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the
management plans are applied at the appropriate level of control.
The purpose of this activity is to assure that the project is executed according to what
was agreed to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled
project activities (and tasks) and that work is progressing and deliverables are
produced as expected.
The purpose of this activity is to capture and manage project issues and risks and
changes related to those e.g. changes of project scope, timeline, costs etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
status and progress of the project including potential disturbances due to existing
risks and issues.
Mandatory
Optional
The purpose of this activity is to collect all required input for the OCM roadmap and
document it in a format suitable for communication and inclusion into the project
management plan
The purpose of this deliverable is to develop a comprehensive training strategy that
provides all team members with a phase-based learning path for acquiring the skills
and knowledge needed to complete the project successfully. This learning path leads
to project readiness as well as certification on the specific applications the team
members will be using.
The purpose of this task is to prepare the training strategy and plan.
Optional
The purpose of this task is to complete the Business Process Map with the content
reflecting the process scope of the project
Validate and Complete Business Process Map with pre-defined content depending
on delivery model (Industrialized and/or Assemble to Order process content).
The purpose of the data migration approach and Strategy deliverable is to capture
and communicate the approach and strategy for the legacy data migration. This
deliverable is intended to educate the SAP and customer project team members on
Optional
the SAP data migration framework and methodology used to support the data
migration project. In addition, the scope and requirement for data migration should
also be determined
The purpose of this task is to prepare the data migration scope and requirements
document that captures the overall scope and requirements of the data migration
effort.
The purpose of this activity to collect input needed for the Data Migration Approach
and Strategy document, in a format suitable for both communication purpose as well
as for formal sign-off purpose.
The purpose of the technical requirements and design deliverable is to provide the
project with a specification of the target solution from a software component
standpoint. This document is intended to serve as a reference for the rest of the
project team during the Business Blueprint phase.
Optional
Included in this deliverable is the solution landscape deployment plan, which is a
high level description of the overall system landscape approach to be used for the
implementation project.
The purpose of this task is to outline the software components and the design of the
future solution landscape.
The purpose of this task is to describe the concept of how the solution in scope will
be deployed.
The purpose of the interface inventory deliverable is to preliminarily identify the
external systems, applications, and business objects or transactions that must be
integrated with the SAP solution to realize the objectives of the project
The purpose of this task is to collect necessary information for the interface inventory
document.
The purpose of the initial hardware sizing proposal is to begin the process of
assessing the hardware infrastructure requirements.
The purpose of this task is to completed sizing estimates for the Solution Manager
system and Production and non-Production environments.
The purpose of the project support tools and system setup deliverable is to establish
the basic tools and processes necessary to support the project.
One of the most vital project tools is the SAP Solution Manager, the centerpiece of
SAPs Application Lifecycle Management tools. The SAP Solution Manager provides
a central point of access for a variety of essential project support functions, including:
The purpose of this task is confirm that the access to the Cloud environment is
possible via the customer LAN
The purpose of this task is to validate and ensure a proper Solution Manager setup.
The purpose of this task is to confirm that the Solution Manager can connect to the
SAP application in the Cloud environement (Hybrid approach)
The purpose of this task is to ensure that the business process structure in SolMan
is supporting the solution documentation and all continued project activities in the
coming phases (business process management, value management, configuration &
development, test, training and cut over).
The purpose of this task is to validate that customer has SAP Solution Builder
installed and setup.
The purpose of this task is to install SAP Best Practices solution builder content addon, installation data and solution file
The objective of this task is to setup project logistics, systems and infrastructure that
will support delivery of the project. This may include setup of computers, setup of
project team room, telephony, etc.
The purpose of this task is to prepare authorization roles in the systems for the
project team
The purpose of the demo environment deliverable is to install a technical
development-like system to be used for demonstration and visualization purposes.
The purpose of this task is to installed the virtual Pre-Assembled Rapid Deployment
Solution and make it available in the system landscape of the customer.
The purpose of this task is to perform unit test of the activated pre-assembled RDS
solution and to confirm that relevant solution scope and business processes have
been activated without issues.
The purpose of this task is to check that the SAP system is running correctly and to
ensure that the remote service connection is enabled.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Identify lessons learned during the phase to prepare for formal project closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Mandatory
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable
Project Management Plan) guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the
management plans are applied at the appropriate level of control.
The purpose of this task is to update the project management plan and the
subsidiary plans based on the changes agreed during the projects change
management process.
Mandatory
The purpose of this activity is to assure that the project is executed according to what
was agreed to in project charter, scope statement and project management plan.
The purpose of this task is to plan, setup and conduct various SCRUM meetings in
order to keep the project teams aligned around common vision, share information
amongst the SCRUM teams and align individuals within each team. The purpose of
these standard meetings is to inform others about work that individual team
members do on given day and surface any blockers that team members need help
addressing .
In Agile implementation project the teams conduct following meetings:
1. Daily SCRUM meeting - short (about 15 minutes) session within each SCRUM
team facing the SCRUM board team members report to the team about what they
work on and whether they are encountering any issues that they need help with.
Objective of this session is to inform and align the team work.
2. Regular SCRUM of SCRUMs meeting - session in which SCRUM Masters from
individual SCRUM teams share information about what each SCRUM team works
on, surface any cross team alignment topics and resolve any issues that arise
between the teams. The session is very similar to integration team meetings
conducted in traditional projects. Note: Cadence of these sessions needs to be
calibrated, but they should be done on at least bi-weekly basis. The more often they
are done the shorter they can be.
3. Sprint Demo - the purpose of this meeting is to demonstrate the results of the
sprint to customer and obtain acceptance to release the features developed during
the sprint. The meeting is attended by Product Owner team, End users and SCRUM
team. It is conducted at the end of sprint.
4. Sprint Retrospective - or process improvement meeting is conducted right after
Sprint Demo meeting prior to closing the sprint. The objective of this meeting is for
the SCRUM team to conduct retrospective of the sprint, identify potential
improvements of the process, prioritize and select top improvements to implement in
the next sprint.
The purpose of this activity is to assure that resources are assigned to all scheduled
project activities (and tasks) and that work is progressing and deliverables are
produced as expected.
The purpose of this activity is to capture and manage project issues and risks and
changes related to those e.g. changes of project scope, timeline, costs etc.
Mandatory
The purpose of this task is to ensure that each contract is closed by verifying that all
work specified in the contractual arrangement was completed, and that all defined
Mandatory
deliverables were accepted.
The purpose of the stakeholder analysis deliverable is to detect the level of
acceptance or the general attitude regarding the project on the part of all key
stakeholders, as well as the ways they can influence the project. Execute an analysis Optional
of current state asis and future state tobe business process maps to quantify the
delta transition gap
The purpose of this task is to re-visit the stakeholder identification results, determine
the detailed level of change impacts for the identified stakeholder (groups) in order to
create transparency about the organizational and system changes.
The purpose of this task is to identify key users needed for the different areas
(depending on the scope of this project).
The purpose of the Change impact analysis deliverable is to ensure that the
organizational and technical changes in business processes have been identified
and documented by comparing the as-is and the to-be business processes.
Optional
The purpose of this task is to validate the chosen approach with key stakeholders for
the continued project execution.
The purpose of this task is to define the baseline for where organizational change
management starts and against which progress and success of the OCM-activities
Optional
are measured.
The purpose of the End User Training Strategy and Plan deliverable is to develop a
high level training plan that provides the recommended approach and corresponding Mandatory
activities to prepare the end users for using the new system.
The purpose of this task is to perform an analysis of the end-user population to be
trained and determine where the skills levels, knowledge gaps, and training
requirements are located. This analysis contains the key customer information for
definition of the end-user training and documentation of high-level project plan
recommendations, proposals, and preliminary strategies.
The purpose of this task is to develop a working document to track evolution of
documents and progress of processes for all education aspects of the project
The purpose of the Project Team Training deliverable is to ensure that the project
team is informed about the way of working during the Blueprint Phase including
usage of Solution Manager for Solution Documentation.
The purpose of this task is to clarify deliverables and expectations, methodology, and
tools. Typically two to three days should be reserved for this training. Once the team
members or at minimum the team leads are identified, they will be brought on board
with this ramp-up training before the phase kickoff meeting. The blueprint ramp-up
deliverable:
Optional
Mandatory
The purpose of this deliverable is to create project related test framework, which gets
content input from the existing Test Policy (1.16.), to build a central foundation
around the taken approach (e.g. Test Approach and Methodology, Test Standards
and Guidelines, Test Case Development, Defect Management, Reporting and
Mandatory
Analysis, Roles and Responsibilities)
on functional testing (unit-, string-, integration-, scenario-, user acceptance,
regression testing etc.) and performance testing. The actual test strategy
documentation for functional testing and performance testing have to be separated.
Determine overall test data approach by aligning with the overall data migration
approach. The test data approach will be documented as part of the testing strategy.
The objective of this task is to communicate the testing strategy (functional and
performance) to the customer project team and validate it.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project closure
The purpose of this task is to pass the Project Quality Gate by conducting a quality
check at critical stages of the project. Project Quality Gates are an integral part of
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
Performance testing
The purpose of the phase initiation deliverable is to formally recognize that a new
project phase starts.
The purpose of this task is to confirm resource availability for the particular phase.
The purpose of this deliverable is to initiate sprint in formal Sprint Planning Meeting.
The purpose of this task is to initiate sprint by selecting the set of user stories that
will be implemented in the sprint (scope of the sprint). During the sprint planning
meeting the SCRUM team estimates the stories and clarifies with product owner
team any questions that may still remain open. The team commits to deliver set of
highest priority stories from the backlog. This meeting formally sets the scope for the
sprint. This meeting is conducted in the beginning of each sprint.
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable
Project Management Plan) guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the
management plans are applied at the appropriate level of control.
Mandatory
The purpose of this task is to ensure consistent planning, execution and monitoring
of sprint activities. This includes:
Team Activities
The team performs their sprint tasks as to the sprint backlog, taking priority and
done criteria into account
The team attends the Daily Standup Meeting. The Daily Standup Meeting serves
for information exchange among the team members. It should not exceed 15
minutes and occurs same time same place each day. After the meeting, the team
updates the sprint backlog (what are remaining tasks and efforts). For more
information please refer to the Scrum Meeting Guidelines.
Scrumof Scrum Meetings are conducted to coordinate the work between different
scrum teams. Scrum of Scrum meetings allow teams to discuss their work, focusing
especially on areas of overlap and integration. For more information please refer to
the Scrum Meeting Guidelines
Product Owner Activities
Prepares readystate user stories for the next sprint(s).
Aligns expectations and requirements with his business stakeholders.
Is available for answering questions from the team.
Scrum Master Activities
Makes sure that the Scrum process is followed (organizing and facilitating Daily
Scrums, daily updates of remaining tasks and effort by team, organization of sprint
review and retrospective meetings)
Solves blocks and supports team, including escalation.
Ensures that management or others do not influence team.
The purpose of this activity is to assure that the project is executed according to what
was agreed to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled
project activities (and tasks) and that work is progressing and deliverables are
produced as expected.
The purpose of this activity is to capture and manage project issues and risks and
changes related to those e.g. changes of project scope, timeline, costs etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
status and progress of the project including potential disturbances due to existing
Mandatory
risks and issues.
SCRUM of SCRUMs Meeting is conducted to coordinate the work between different
project SCRUM teams. SCRUM of SCRUMs meetings allow teams to discuss their
work, focusing especially on areas of overlap and integration. The meeting cadence
is defined for the entire project and follows the same structure. Some teams conduct
daily SCRUM of SCRUMs meeting while others consider weekly meeting sufficient.
The main driver for the meeting cadence is the level of collaboration between the
individual SCRUM teams and level of dependencies between the features built in
each SCRUM team.
The purpose of Organizational Alignment is to ensure a smooth transition process
towards the new way of working. This includes the alignment of roles and
responsibilities and activities to ensure that all employees are fully aligned to the
goals of the project and organization.
The purpose of this task is to use the results from previous change impact analysis
and the role mapping information (mapping of new business user roles to existing
Optional
roles and organizational structure) and determine an appropriate transition approach
for the business.
The purpose of the Knowledge Transfer deliverable is to ensure that key users get a
good understanding of the implemented solution.
In this task the SAP project team prepares for training and enablement of the
customer project team to understand the solution and how it is implemented in their
area, as well as trains the key users as defined in the statement of work.
Mandatory
The purpose of this task is to prepare master data required for all business
processes' unit and string tests in DEV.
The purpose of the Core Configuration and Documentation deliverable is to ensure
that the configuration is implemented, tested and documented.
Mandatory
The purpose of this task is to implement the Core Configuration, write valid test
cases and to document this in Solution Manager.
The purpose of the Delta Configuration deliverable is to ensure that the configuration
is implemented, tested and documented.
Mandatory
The purpose of this task is to implement the Delta Configuration, write valid test
cases and to document this in Solution Manager.
The objective of this task is to develop process documentation for any changed
processes or for any new processes added to the standard.
The objective of this task is to develop process test cases for any changed
processes or for any new processes added to the standard solution.
The purpose of this task is to perform unit and string test for the configuration
Optional
The objective of this task is to resolve any issues identified during the Unit and String
Test. It is crucial that the issues are re-tested by users that reported them (or
designated re-testers) and that they are confirmed.
The purpose of this deliverable is to accommodate all RDS or Service Specific
enhancements, coded assets, etc. Each asset will have separate line item in this
structure
Mandatory
The purpose of this service specific <Asset Name> is to <explain purpose of the
extension specific task>.
Note: This task is a place holder for any tasks that are specific to extensions like
reports, interfaces, etc. that are delivered in the service or RDS
The purpose of this deliverable is to develop and test the RICEFW objects.
Documentation to be stored in Solution Manager.
The purpose of this task is to develop the RICEFW object according to the functional
specification,
Mandatory
Optional
The objective of this task is to resolve any issues identified during the RICEFW
object(s) Test. It is crucial that the issues are re-tested by users that reported them
(or designated re-testers) and that they are confirmed.
The purpose of this task is to perform final code review of the development objects
and confirm readiness for transport into QAS.
The purpose of the Business Process Procedures deliverable is to provide the basis
for end-user training, end-user training documentation and test case creation. The
procedures may also be used by security to develop roles and authorizations.
The purpose of this task is to validate and complete Business Process Procedures
from the blueprint phase.
The purpose of this task is to validate and complete Business Process Procedures
from the blueprint phase.
The purpose of this deliverable is to provide evidence that the scenarios designed
can be supported by the solution implemented.
The purpose of this task is to identify and document applicable test case(s) for the
scenario.
The purpose of this task is to perform scenario test.
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.
Optional
The purpose of this task is to refine the preliminary cutover plan based on
information the project team learned in the cutover plan review with customer.
The purpose of Approved Integration Test is to ensure functional correctness. It test
the integration of SAP solutions with non-SAP applications and interfaces and can be
Mandatory
executed in an iterative manner.
The purpose of this task is to define and document integration test cases, end-to-end
customer business process scenarios, according to the test plan. Test plans and test
case documentation is stored in Solution Manager.
The purpose of this task is to document the integration test case outlined in the
integration test plan
The objective of this task is to perform the Integration test according to previously
defined plan. During the test all issues must be logged and documented in the
system for traceability purpose.
The objective of this task is to resolve any issues identified during the Integration
Test. It is crucial that the issues are re-tested by users that reported them (or
designated re-testers) and that they are confirmed.
The purpose of this task is to obtain customer approval (sign-off) of the integration
test.
The purpose of the legacy data migration deliverable is to develop, implement, and
test the data migration programs and processes defined in the business blueprint
phase. This activity consists of iterative development and testing cycles focused on
the analysis of data, refinement of business rules, and deployment of migration
programs and processes designed to move, cleanse, transform, and enrich legacy
Mandatory
data required to support the various test cycles and ultimately the production cutover.
The test cycles enable the migration team to improve data quality to an acceptable
production level, develop a detailed cutover sequencing plan, and exercise data
reconciliation and validation processes required to support the production cutover.
The purpose of this task is to load the cleansed legacy data into the SAP software
target structures using a standard SAP load utility such as LSMW.
The purpose of this deliverable is to execute the User acceptance test (UAT). This is
the last test cycle of an SAP solution implementation and is an essential part of
Mandatory
gaining end-user acceptance of the software system.
The purpose of this task is to define and document UAT test cases according to the
test plan. Test plans and test case documentation is stored in Solution Manager
The purpose of this task is to document the integration test case outlined in the UAT
test plan
The objective of this task is to perform the End User Acceptance test according to
previously defined plan. During the test all issues must be logged and documented in
the system for traceability purpose.
The objective of this task is to resolve any issues identified during the User
Acceptance Test. It is crucial that the issues are re-tested by users that reported
Mandatory
them (or designated re-testers) and that they are confirmed.
The purpose of this task is to execute the testing, document the results and obtain
customer approval (sign-off)
The purpose of the production infrastructure and environment design and setup
deliverable is to install a viable, correctly configured technical production
Mandatory
environment to support productive operations of the delivered solution.
The purpose of this task is to install and set up the production environment.
The purpose of this task is to upgrade the production environment.
The purpose of this task is to build the production (PRD) environment with changes
that have been tested and released from the quality assurance (QA) environment.
The purpose of this task is to set up users in the production environment.
The purpose of this task is to ensure that appropriate master data is available for
testing in the production environment (system test).
The purpose of this task is to prepare master data required for all business
processes in PRD.
The purpose of this task it to perform import of Fast-Track configuration into the
Production environment.
The purpose of this task is to perform any remaining manual configuration changes
in the production environment.
The purpose of planned Performance and System Test is to checks the entire
system, consisting of databases, applications servers, front ends, printers etc. The
performance test measures the throughput and response times of the system.
Mandatory
The task defines and documents the identified test cases related to system and
performance test. Outcome is documented in a test plan.
The purpose of this task is to document the test case outlined in the test plan
The objective of this task is to resolve issues identified during the performance or
load testing. Upon resolution the issues need to be re-tested and confirmed by
responsible testers.
The purpose of this service is to support the start of production of an SAP Solution.
During this service, SAP service engineers check the solution for potential risks and
Optional
give recommendations ensuring optimal performance and system availability for core
business processes.
The purpose of this task is to perform the first session of the SAP GoingLive Check.
The service consiste of two sessions - Analysis and Verification, and includes:
- Verification of the technical capabilities of the production environment (sizing
plausibility)
- Check of system configuration (database, system components)
- Check of version and release compatibility of all involved SAP components and
Plug-Ins
The purpose of the technical operations and handover strategy deliverable is to
update refine two prior deliverables from the Business Blueprint phase, and prepare
Optional
a strategy to hand off operations of the solution landscape to the post-production
support organization.
The purpose of this task is to ensure that proper staffing(people and competence) is
in place for the support org/team
This task describes the considerations that are required to recognize and solve
critical situations during business process operation.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Mandatory
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable
Project Management Plan) guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the
management plans are applied at the appropriate level of control.
The purpose of this activity is to assure that the project is executed according to what
was agreed to in project charter, scope statement and project management plan.
The purpose of this activity is to assure that resources are assigned to all scheduled
project activities (and tasks) and that work is progressing and deliverables are
produced as expected.
The purpose of this activity is to capture and manage project issues and risks and
changes related to those e.g. changes of project scope, timeline, costs etc.
Mandatory
The purpose of this activity to make sure that project stakeholders are aware of
status and progress of the project including potential disturbances due to existing
risks and issues.
Mandatory
Mandatory
The purpose of this task is to complete the Cut Over plan with results obtained from
the Go Live simulations.
Mandatory
The objective of this task is to perform all the cutover preparation activities remaining
to be closed prior to cutover weekend. The detailed cutover plan contains the
complete listing of all pre-cutover activities, their dependencies, owners, and timing.
This task will confirm that the productive system is ready for Go Live.
Optional
The purpose of this task is the loading of production data from legacy systems into
the production environment. Once all preparations and configurations on both the
technical and application levels are completed, the final productive solution can be
set up and data loaded. The solution is live in a production environment
Purpose of this task is to obtain customer approval (sign-off)
Mandatory
Purpose of this task is to hand over the finalized implementation project and it's
content, and set up as a productive solution in SAP Solution Manager. This provides Optional
the basis for the follow up activities in the Run Phase.
The purpose of the phase closure and sign-off deliverable is to:
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Mandatory
The purpose of this deliverable is to execute the project management plan and
control and monitor the work defined in the project scope statement.
Management plans developed during the project preparation phase (see deliverable
Project Management Plan) guide the approach to management, execution, and
control of project activities. The project manager is responsible for ensuring that the
management plans are applied at the appropriate level of control.
The purpose of this activity is to assure that resources are assigned to all scheduled
project activities (and tasks) and that work is progressing and deliverables are
produced as expected.
The purpose of EU training during go-live support is to ensure that end users have
adopted the solution, knowledge resources are maintained, and responses to the
Optional
end-user acceptance survey are positive.
This purpose of this task is to adapt available training material and make it suitable
for End User training.
This task executes the delivery of EU training as well as capturing feedback on both
the training session and the trainer.
Ensure that all required deliverables from this phase and the project are
complete and accurate, and close any outstanding issues
Mandatory
Identify lessons learned during the phase to prepare for formal project closure
To assure that all key deliverables and actions of the gate have been
completed in compliance with recommended practices and to the customers
satisfaction
Optional
Solution operations are initially set up during the implementation project. The
primary goal of this phase is to further optimize and automate the operability of
the solution. Operability is the ability to maintain IT systems in a functioning
and operating condition, guaranteeing systems availability and required
performance levels to support the execution of the enterprises business
operations.
The Operations Maturity Assessment evaluates the SAP customer's support
operations to determine areas in need of optimization
The purpose of this activity is to assess business and technical requirements for
operations and to define what aspects of the operations need to be adjusted,
enhanced or implemented.
The report should detail assessment results and finding, including proposed actions
for how to bridge identified gaps.
Centrally document and relate business processes and technical information of SAP
and non-SAP Solutions ensuring transparency, efficient maintenance and
collaboration
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Solution Documentations area.
Represents the identification, adaptation and implementation of new and enhanced
future-proof business and technical scenarios
Is a part of the application lifecycle and is designed to decouple technical installation
from business innovation
Uses the SAP Solution Manager to implement the innovation in the system
landscape
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Solution Implementation area.
The template management approach allows customers with multi-site SAP
installations to efficiently manage their business processes across geographical
distances from initial template definition to template implementation and template
optimization, for example as part of a global rollout
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Template Management area.
Functional and performance testing of SAP-centric business processes to ensure
validated system behavior after software change events
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Test Management area.
Workflow-based management of business and technology-driven changes, with
integrated project management and synchronized deployment capabilities.
Standardized process leading to improved reliability of solution and minimized risk
through segregation of duties and transparency of changes
Efficient solution management all project and system information is saved in SAP
Solution Manager
Re-visit result of ALM roadmap workshop from the project preparation, lessons
learned findings from the implementation project and determine if potential gaps
exist for the Change Control Management area.
Work Stream
Accountable Role
_Phase
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Steering Committee
Definition, Org-Structure,
Roles
Project Charter
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
OCM - Organizational Change
Management
PM - Project Management
Phase Kick Off Meeting
Scope Statement
Document
Project Manager
Project Manager
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project Budgetplan
(internal & external)
PM - Project Management
Project Manager
Project Management
Plan(s)
PM - Project Management
PM - Project Management
Project Manager
Business Consultant
Software System
Configuration Standards,
Enhancement and
Modification Standards
Business Consultant
Test Management
Standards
Application Consultant
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project (Performance)
Report (internal &
external)
PM - Project Management
Project Manager
OCM Roadmap
Business Consultant
Training - Training
Training - Training
Education Consultant
Training - Training
Training - Training
Education Consultant
Solution Landscape
Design
Application Consultant
Application Consultant
DM - Data Migration
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Solution Architect
Technology Architect
Technology Architect
Solution Architect
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
PM - Project Management
PM - Project Management
Business Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
Project Management
Plan(s)
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project (Performance)
PM - Project Management
Report (internal & external
Project Manager
Stakeholder Analysis
(Internal)
Organizational Change
Management Plan
Business Consultant
Education Consultant
Business Consultant
Business Readiness
Approach
Business Consultant
Training - Training
Training - Training
Education Consultant
Education Consultant
Training - Training
Training - Training
Business Consultant
Application Consultant
Application Consultant
Application Consultant
Integration Development
Consultant
Application Consultant
DM - Data Migration
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Delivery of projects
Results
Delivery Acceptance
Protocol
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
DM - Data Migration
Application Consultant
Technology Consultant
PM - Project Management
PM - Project Management
Business Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Application Consultant
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project (Performance)
PM - Project Management
Report (internal & external
Project Manager
PM - Project Management
Project Manager
Business Consultant
Training - Training
Training - Training
Application Consultant
Training - Training
Application Consultant
Training - Training
Application Consultant
Solution Documentation
(incl. Process list,
Configuration, Interfaces,
Developments)
Application Consultant
Application Consultant
Solution Documentation
(incl. Process list,
Configuration, Interfaces,
Developments)
Application Consultant
Solution Documentation
(incl. Process list,
Configuration, Interfaces,
Developments)
Application Consultant
Solution Documentation
(incl. Process list,
Configuration, Interfaces,
Developments)
Education Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
Development list(incl.
BPM - Business Process
RICEFW, SOA, Migration) Management
BPM - Business Process
Management
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Integration Development
Consultant
Application Consultant
Application Consultant
Solution Landscape
Design
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Application Consultant
_Milestone
Production Cutover Plan
Application Consultant
Project Manager
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Technology Consultant
DM - Data Migration
DM - Data Migration
Application Consultant
Solution Landscape
Design
Technology Consultant
Application Consultant
Application Consultant
Application Consultant
Project Manager
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
DM - Data Migration
Application Consultant
DM - Data Migration
Application Consultant
Technology Architect
Application Consultant
Technology Consultant
Application Consultant
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
PM - Project Management
PM - Project Management
Business Manager
PM - Project Management
Project Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Project (Performance)
PM - Project Management
Report (internal & external
Project Manager
Training - Training
Training - Training
Education Consultant
Technology Consultant
DM - Data Migration
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Application Consultant
Project Manager
Technology Consultant
PM - Project Management
PM - Project Management
Business Manager
_Milestone
_Phase
PM - Project Management
Project Schedule (incl.
milestones)
PM - Project Management
Project Manager
PM - Project Management
PM - Project Management
Project Manager
Education Consultant
Training - Training
Education Consultant
Technology Consultant
Technology Consultant
_Milestone
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Project Manager
Delivery of projects
Results
Delivery Acceptance
Protocol
PM - Project Management
PM - Project Management
Project Manager
PM - Project Management
Business Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
PM - Project Management
Project Manager
_Phase
PM - Project Management
PM - Project Management
Business Consultant
PM - Project Management
Project Manager
Application Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Technology Consultant
Application Consultant
Technology Consultant
Technology Consultant