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