WBS-ul SuccessFactors

Information Type: Working Standard_x000D_Disclosure Range: _x000D_Information Owner: dan.
olovinaru_x000D_Company: NTT DATA

Romania
Title
Purpose
Methodology Version
Methodology Type
Pre-selection Type
Status
Activated at
Deprecated at
WBS Description
Information Type: Working Standard_x000D_Disclosure Range: _x000D_Information Owner: dan.olovinaru_x000D_Company: NTT DATA
Romania
SAP Activate Methodology for SuccessFactors

Road Map Creation
9
SAP Activate
Others
Inactive
<div id="left" style="float:left; width:70%">

This roadmap is intended to guide the implementation team though a SuccessFactors implementation. The
Implementation roadmap is comprised of Phases, Deliverables and Tasks and in accordance with the SAP Activate methodolog
and structure. Implementation deliverables and tasks might vary based on the specific project delivery
scope.

size:medium">Where applicable, accelerators have been linked to the relevant deliverables and
tasks.

size:medium">Deliverables and tasks have been listed in sequential order based on activity start, however parallelization can
be required to expedite the implementation.
<img alt="" src="https://support.sap.com/content/dam/SAAP/SAP_Activate%20Images/IMG_265.png" />

</div>
<div id="right" style="float:right; width:30%">

<ul>
<li>Please login to access additional content. (Top left drop-down)</li>
<li>View the Getting Started presentation in the Prepare Phase accelerators</li>
<li>Download the Project Plan using the Download Project Plan link.</li>
</ul>
</div>
Romania
Sequence Number Title
1 Discover
1.1 Solution Scope Definition
1.1.1 Solution Value and Functionality Demonstrations
1.1.2 Target Solution Model Determination
1.1.3 Solution Architecture Definition
1.1.4 Integration Architecture Definition
1.2 Implementation Scenario and Scope Definition
1.2.1 High Level Implementation Approach and Phasing
1.2.2 Effort Estimations
1.3 Scope Statement
1.3.1 Develop Scope Statement

Romania
2 Prepare
2.1 Customer Team Self-enablement
2.1.1 Ensure Key User Access to the SAP Support Portal and Best Practices
2.1.2 Provide Customer with Links to Learning Materials
2.1.3 Review Self-enablement Materials
2.1.4 Complete self-assesment questionnaires
2.2 Project Initiation and Governance
2.2.1 Conduct Handover Meeting with Sales

Romania
2.2.2 Align Project objectives, benefits and scope
2.2.3 Establish Project Governance
2.2.4 Define Project Communications and Reporting
2.3 Project Plans, Schedule and Budget

Romania
2.3.1 Create Project Schedule and Budget
2.4 Project Standards, Infrastructure, and Solution
2.4.1 Define Project Standards

Romania
2.4.2 Setup Project Team Logistics and Infrastructure
2.4.3 Confirm provisioned systems availability
2.5 Project Kick-Off and On-Boarding
2.5.1 On-board Project Team
2.5.2 Conduct Kickoff Workshop

Romania
2.6 Phase Closure and Sign-Off Phase Deliverables
2.6.1 Conduct Project Quality Gate
2.6.2 Obtain Customer Sign-Off for Phase Completion
3 Explore
3.1 Execution/Monitoring of Project

Romania
3.1.1 Direct and Manage Project Execution
3.1.2 Update Project Management Documents
3.1.3 Manage Project Issues, Risk and Changes

Romania
3.1.4 Communicate Project Status and Progress
3.2 Fit-Gap Analysis/Requirements Capturing
3.3 Configuration Definition
3.3.1 Define Configuration Values
3.4 User Access and Security
3.4.1 Physical access and Security
3.4.2 Authorization and Permission Training
3.4.3 Authorization Roles and Assignments

Romania
3.5 Integration Preparation
3.5.1 Apply Integrated System Prerequisites
3.5.2 Confirm Integration Prerequisites
3.5.3 Set Up Network Connectivity and Security

3.5.4 Confirm Integration Fields and Create Adaptation Specifications
3.6 Solution Extension Preparation
3.6.1 Identify Custom Extensions

3.6.2 Define Key User Extensions
3.7 Data Load Preparation
3.7.1 Perform Data Cleansing Activities
3.7.2 Download Templates for Data Loads
3.7.3 Define Specifications for Data Extraction on Legacy System
3.7.4 Develop Overall Load Plan

3.8 Data privacy and consent
3.8.1 Data privacy requirements
3.8.2 Data security classification
3.8.3 Data storage definition

3.8.4 Data transfer definition
3.8.5 Data privacy consent statement

Romania
4 Realize

Romania

4.2 Solution Configuration
4.2.1 Complete Core Configuration
4.2.2 Determine and Create Sample Master Data
4.2.3 Configure Output Management

4.2.4 Execute Business Process Unit Test
4.2.5 Business Process Playback Demonstration
4.2.6 Capture testing feedback and configuration changes
4.3 Solution Extension Development
4.3.1 Request Custom Content Development
4.4 Reports
4.4.1 Enable Customer on Standard SAP Reports
4.5 Final Solution Walkthrough

Romania
4.5.1 Conduct Solution Walkthrough
4.6 Solution Test Preparation
4.6.1 Prepare Test Cases
4.6.2 Create the Test Plan

4.6.3 Test Preparation Training
4.7 Integration Setup in the Test Environments
4.7.1 Confirm Integration Fields and Create Adaptation Specifications
4.7.2 Create Integration Mappings and Transformation

4.7.3 Perform Integration Set Up on the Cloud System
4.7.4 Perform Integration Set up on the On-premise Test System
4.7.5 Perform integration unit test
4.8 End User Training Strategy and Plan
4.8.1 Conduct Learning Needs Analysis
4.8.2 Develop Detailed End-User Training Plan
4.9 End-User Training Materials and Resources

Romania
4.9.1 Develop Training Materials
4.9.2 Trainer upskilling
4.10 Legacy Data Migration
4.10.1 Execute and Validate Manual Data Migration

4.10.2 Support Data Load Issue Resolution
4.10.3 Conduct Final Data Quality Assessment
4.11 Solution Test Execution
4.11.1 Execute Test Case
4.11.2 Resolve Test Incidents
4.12 System User Roles and Authorization Administration

4.12.1 Set Up Administrative Procedures for Roles and Authorizations
4.13 Technical Operations and Handover Plan
4.13.1 Establish Support Processes
4.13.2 Establish Operational Processes
4.14 Cutover Plan

Romania
4.14.1 Cutover Planning Workshop & Documentation
4.15.2 Obtain Customer Sign-Off for Phase Completion
5 Deploy


Romania
5.2 Production Cutover / Switch to Production
5.2.1 Execute Cutover Tasks per the Cutover Plan

5.2.2 Production System Setup
5.2.3 Set Up User IDs for Project Team Members in Production System
5.2.4 Migrate Configuration To production Environment
5.3 Integration Setup on the Production System
5.3.1 Apply All Integration Prerequisites
5.3.2 Set Up Network Security and Connectivity

5.3.3 Perform Integration Setup
5.4 Execute Initial Integrated Data Load
5.4.1 Validate Migration Datasets and Load Processes
5.4.2 Initial Data Load

5.4.3 Load Validation
5.5 Solution Extension Deployment on Production
5.5.1 Deploy Solution Extensions
5.6 End User Training
5.6.1 Deliver End User Training
Romania
5.6.2 Establish and Communicate Internal Support Process

5.7 Delivery to Support Handover
5.7.1 Conduct the Handover to Support Meeting
5.8 Production Hypercare Support
5.8.1 Provide Hypercare Support
5.9 Project Closure and Sign-Off Project Deliverables / Hand Over Solution
5.9.2 Obtain Sign-off for Project Closure and Results Acceptance
6 Run
6.1 Quarterly Release Management
6.1.1 Quarterly Functionality Evaluation
6.1.2 Release review and Readiness Preparation

Romania
6.1.3 Preview Release Testing
6.1.4 Product update activation
6.1.5 Release Communications

6.2 Operations Monitoring and Management
6.2.1 System Performance Monitoring
6.3 Ongoing Knowledge Sharing and Collaboration
6.3.1 Customer Collaboration and Learning
6.4 Administration Training and Accreditation

6.4.1 SFX Accreditation
6.5 Roadmap and Enhancement Management
6.5.1 Roadmap Review
6.5.2 Suggest Enhancements
6.6 Production Support After Go Live
6.6.1 Provide Post Go Live Support

Romania
Description
The purpose of the discover phase is for the customer to come to understand the breath, depth and functionality of the SAP
SuccessFactors solution. Within this phase the customer and implementation team will discuss the overall HR strategy, busine
drivers and priorities, key success metrics, specifed solution scope and HR Business processes, functionality requirements and
work on a initial implementation scenario. During this phase the customer and the sales team come to a jointly agreed descrip
of the implementation scope, overall project timelines and target solution model.
The pupose of this deliverable is to define the overall solution scope and determine the SuccessFactors products that are inclu
into the project implementation. The deliverable will be completed by conducting a joint review of the customer stategic
objectives, business process scenario's and to map these against the suitable SuccessFactors solutions. the second stage of the
solution scope definition will explore the interrelations between the different SuccessFactors products in scope and the positio
the SuccessFactors solution in the overall system landscape.
The purpose of this task is to show the specific SuccessFactors solution content and demonstrate how SuccessFactors function
can meet customer specific Business scenarios and requirements.
The purpose of this task is to define the end-state solution model. During this activity the to-be system target solution is being
defined. The customer HR business process scenario's and functional requirements are being mapped against the sucessfactor
products. The product scope is being determined, and the initial integration needs are identified.
During the Solution Architecture definition the high level end-to-end business process design will be validated against the
SuccessFactors solution architecture. A high level definition of the connecting process steps and dataflows between the differe
successfactors products will be defined.
In this task, the position of the SuccessFactors solution within the overall customer system landscape is being determined. Hig
level data flows and integration requirements are being scoped and a overall integration strategy and approach is being define
Integration patterns and technology are being agreed and integration strategy and approach will be validated against system
prerequisites and business requirements.
In this deliverable a solution implementation scenario is being developed and initial resource and effort estimations are being
completed
Based on the Solution Scope, Target Solution Model and Business Priorities a high level implementation approach and plan is
being defined. General project phasing is being discussed, Initial implementation efforts are being estimated and project team
roles and responsibilities are being aligned
Based on the solution scope, project implementation approach and phasing the resource requirements and overall
implementation efforts can be estimated.
The Scope Statement deliverable summarizes the solution- and implementation scope, deliverables, high level project approac
phasing and estimations into a overall statement of the project scope and delivery.
The scope statement that is developed during the serviecs sales process provides a jointly agreed and approved decription of
key project outcomes and delivery. The scope statement can be used to communicate the project scope and deliverables to th
project team members. The scope statement will be used as the baseline for the change control process. Refinement and chan
to the project delivery scope can occur throughout the project, and can be managed by the change control process.
Romania
The purpose of this phase is to provide the initial planning and preparation for the project. In this phase, the project is started
plans are finalized, project team is assigned, and work is under way to start the project optimally. Key Prepare Activities: De
project goals, a high-level scope, and a project plan Identify and quantify business value objectives Secure executive
sponsorship Establish project standards, organization and governance Define and secure approval for the
implementation/upgrade strategy Define roles and responsibilities for the project team Validate the project objectives
Establish project management, tracking, and reporting mechanisms for value delivery Develop a project team training strate
and start project team training Document all initiation activities in the project charter Pre-assemble (or establish) the pr
environment, infrastructure, and IT systems including SAP Solution Manager Prepare for the Explore phase
The purpose of this deliverable is for the customer to learn different elements of the SAP system and SAP Activate methodolo
using self-paced enablement materials. Cloud projects are intended to be completed in a shorter time period which requires m
focus on learning tools. It is important that self-enablement begins prior to the project kickoff in order to maximize the time fo
learning and creates efficiencies in later deliverables.
The purpose of this task is to ensure that all key users can access the Support Portal and the best practice documentation. The
support portal can be accessed directly by url: support.sap.com . The Best Practices Explorer can be access via the url:
rapid.sap.com/bp/ New users can be created by the local company Super-administrator. Authorization to create incidents are
provided by the administrator. New SAP customers receive the initial SAP Support Portal credentials via email (UserID format:
Sxxxxxxxxxx). This access is different from the cloud solution credentials. For the Support Portal User access contact your Supe
administrator. You can determine your current administrator and view authorizations as follows: Go to //support.sap.
(SAP Support Portal) Click on your avatar in the top right corner to open your profile menu Click on
“ Display my important contacts ” to find your Super-administrator Click " Display my authoriza
and important functions ” to see you assigned authorizations The Support Portal is required in order to enter and
follow software incidents or requests. Scroll to the bottom of the home page to view the Resources section for more informati
The s-user (Sxxxxxxxxxx) credentials are also required to Log On to the Roadmap Viewer to access additional implementation
accelerators. Always Log On when viewing the roadmaps.
The purpose of this task is to provide the customer with links to learning room(s) and other enablement content. Learning plan
should be set with specific completion dates. Instruction on use of the Learning Hub is given. Project Management will provide
additional project learning enablement and approach where appropriate.
The purpose of this task is to execute the learning plan. It is essential that the materials in the plan are reviewed prior to the s
of the Fit to Standard workshop. The project team should monitor progress on a daily basis. Learning is essential to the projec
success and should not be understated.
The purpose of this task is for the customer to complete the organization assesment questionnaires to provide SAP with an ini
insight in the customer processes, business requirements and use cases.
The purpose of the Project Initiation and Governance deliverable is to formally recognize that a new project exists and to initia
the work on the project. During this time the project sponsor and project manager work to 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. As part of the initiation activities the project manager conducts handover from pre-project phase,
creates a project charter document, scope statement document and establishes the project governance that ensures proper
management process for the project. This ensures alignment between the SAP System Integrator, the customer's project team
company's strategic direction, and the satisfaction of operational requirements.
The purpose of this task is to efficiently transition the project from the sales team to the delivery team. During this task the pr
manager schedules and conducts an internal meeting to transfer key information from pre-project phase (discover or sales) in
the project. Typically, during this call the account team and project team review following areas: project background business
drivers customer goals success metrics for the project solution scope customer expectations
Romania
The purpose of this activity is to create a joint understanding of the objectives, expected benefits and project scope between t
project stakeholders such as Customer project team, SAP management, System implementor and/or SAP Services. The scope
statement that has been developed as part of the sales process within the discover phase will be used to align on project scop
key deliverables, activities and assumptions and constraints. During this activity deep dive discovery and alignment on existing
organizational policies and procedures, communication, data management, security processes and project change control
processes will be done.
Project governance is a management framework setup for the project to ensure the decisions are done in a structured manne
The project governance establishes a policy for the project team, project stakeholders, executives and system integrator that
clearly specifies roles, responsibilities, accountability, and organizational setup. The project governance provides a decision
making framework that is robust and logical in order to ensure the decisions are made timely and on an appropriate level. The
image below shows an example of governance structure for mid-size to large-size projects. The details for each level are outlin
below the image. Level 1 & 2 – Executive Sponsors & Steering Committee Business priorities, goals and objectives
Decision rights and decisions criteria Ownership: change, process & data Economic justification and funding prioritization
Level 3 – Project Management Office On time, On Budget, On Value monitoring Process strategy development Drive Business
Standardization & Best Practices Adoption Prioritization criteria and deployment options IT requirements and dependenc
Communication Level 4 – Project Team Day-to-day execution and delivery of project tasks, identifying, documenting and resol
issues and risk within the framework of their authority. Identification, resolution and communication of issues and risk to PMO
Status reporting and communication to the PM
The project manager defines the project’s communications strategy. The communications strategy involves identifying who ne
to see what information, when, and how, in addition to the intent of each message. Information may need to be distributed to
steering committee, senior management, the project team, subject matter experts, clients, contractors, and other internal or
external personnel. Defining the communications strategy also involves determining which key project deliverables are
communicated (for example, objectives/scope, project schedules, work plans, project status reports, cost information, and so
One of the key elements of the communications strategy and process is to define the frequency and format of the regular stat
reports that the project manager and project teams provide to the key stakeholders. SAP Activate methodology provides a
standard project status report template that the project manager uses in the regular reporting.
The planning activities during the early stages of the project include the development of project plans, preparation of project
WBS,definition of the project schedule and budget development. The project management plan development is critical for
ensuring the project is managed according to structured approach that covers all aspects of project management necessary fo
size and complexity of the project. The project management plan is a comprehensive document (or collection of documents),
including plans for managing the schedule, budget, issues, risk, project changes, etc. The management plans cover all PMI PM
knowledge areas as appropriate. Once the project scope is refined and the work breakdown structure (WBS) developed during
definition of requirements, the project manager and planning team define and sequence required tasks. With dependencies
identified, the project manager adds resources, estimated effort (hours), and estimated duration to create an initial draft of th
project schedule. As requirements are identified, the project schedule and budget are refined.
Romania
The detailed project schedule defines the work to be performed, the resources and associated time commitments required fo
the project, and the individual phases of the project. The work breakdown structure (WBS) serves as the foundation for the
project schedule and deliverables to be produced as part of the project. At a minimum, the project schedule should include:
Deliverables and tasks for the current phase Estimated effort (work) and duration Task dependencies (such as predecessors an
successors) Scheduled start and finish dates for each task,based on dependencies Task constraints (such as must-start-on date
must-finish-on date) Resources assigned to each task High-level schedule for subsequent phases Transport freeze periods rela
to software updates The project manager further elaborates this schedule during subsequent planning activities during the
project, using a “rolling wave” planning approach. The project manager is responsible for creating a project budget, that out
all the costs associated with the project, including labor, hardware, software, cloud provisioning, contracting fees, and facilitie
The project budget is a living document that the project manager maintains. At this stage the project manager sets the budget
baseline and will manage the budget according to the cost management plan that is developed as part of the Project Managem
Plans task.
The purpose of this 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 standa
should be taken into account when defining the most suitable standards for the project. Project team needs to setup tools like
SAP Solution Manager to enable execution of specific project standards. The SAP Solution Manager application management
solution is included in customer’s SAP maintenance agreement, and provides all integrated content, processes, tools, and
methodologies you need to efficiently implement, operate, monitor, and support all your SAP and non-SAP applications. SAP
Solution Manager is also the hub for collaboration within the SAP ecosystem, to ensure delivery of high-quality services and
support for your mission-critical business processes. This enables better operations and faster implementation at lower costs.
Project standards provide a consistent means of executing and governing project work in an efficient and effective manner. Th
key objective of this task is to identify, define, approve, and communicate standards related to project execution. Project
standards are elaborated throughout the Prepare phase (some may be fine-tuned in a later stage of the project). During the
Prepare phase the foundational project standards must be defined, approved,and communicated to the project team.
Communication of project standards should be included in project on-boarding communications for project team members. G
the integrated nature of project standards, changes must be managed in accordance with the integrated change control
procedure. The project team needs to establish at minimum following project standards for following areas: Requirements
Management Business Process Modeling Solution Configuration and Documentation Custom Code / Development
Authorizations / Security Test Planning and Execution Change and Release Management Post-implementation Support and
Operations.
Romania
The objective of this task is to setup a physical project team environment and ensure that the project team members have the
appropriate level of access to the customer facility, project room and the project systems. This activity also involves the setup
project team work stations/computers and/or mobile devices (as necessary for the project support). The project manager
together with the technical team works on setup of the following (the questions in each area are geared to help provide
guidance): Project Experience: Is there a requirement for hardware (e.g. servers,laptops, etc.)? Are there any additional softwa
licenses required? Are the software licenses purchased? Was the software installed for the project team members? Is there an
area planned for the project equipment? Is there project equipment located in different geographical sites? Is there any comp
lab required for the project? Physical Project Environment Has the required work space been arranged at all project sites? Are
there sufficient conference rooms planned for the project team? Has multimedia equipment been planned for all conference
rooms (e.g. video conferencing, projectors, etc.)? Has physical access been granted for all project team members in different
geographical sites? Is there a working area assigned to the project members? IT Infrastructure and Access Is the LAN access
available to the Project Team? Has the LAN access been tested? Do the Project Team Members have the necessary printer dri
installed? Has IT access been granted for the following: E-mail servers Internet access, Intranet access Team collaboration spa
like SAP Jam MS-Office Project team specific applications like modeling tool, test management tools, etc. C ustomer Policies Is
there a specific project policy applicable (communication, confidentiality, back-up, etc.)? Has the project policy been
communicated? Physical Security Has all necessary access been granted indifferent project sites? Have all sites policies been
communicated (e.g.security, safety, emergency exits and etc.)? Telephone/ Voice Mail Is there a telephone number issued to
project team members? Has the Project Team Member been told how to set-up the voice mail? Is there a central phone book
the project team members? Project Team Member Equipment Is the required equipment (computer, laptops, mobile and etc
available to all project team members? Are office supplies available to the project member? Are the required software license
purchased? (if needed)
During this activity the project manager confirms the availability of the development (if applicable), test and production instan
and per the autoprovisioning process and request and requests provisioning access to all systems for the required resources.
The purpose of this deliverable is to kick-off the project and ensure that all needed information is shared with the project team
resources, key stakeholders, and anybody involved in the project. The goal of the kickoff meeting is to ensure that everybody
involved in the project understands the goals and objectives of the project, as well as the schedule that the project team will
follow, which is one of the key ingredients for a successful project execution.
The purpose of this activity is to prepare the on-boarding package for external consultants and new project team members fro
SAP and partner companies coming to the project. The on-boarding package contains the essential information that each new
team member needs to understand the purpose of the project, goals, operating procedures and other key information. The on
boarding package typically contains the following information: Project objectives, scope, and goals including SAP solutions bei
implemented Project schedule including milestones Project governance including key project stakeholders Organizational char
the project- showing both internal and external resources Overview of the existing SAP landscape Outline of regular project
meetings Travel policies, dress code, project location, and other project guidelines as needed.
The purpose of this task is to schedule and prepare the project kickoff meeting. The kickoff meeting includes discussion of pro
objectives, organizational structure, roles and responsibilities, project governance, schedule, scope, communication standards
change request process, and decision making process. The kickoff meeting is attended by the project team, key stakeholders,
project sponsor and company executives. Some resources may attend the kickoff meeting remotely, in such cases it is importa
to ensure good audio and video infrastructure so the remote participants can take full part in the kickoff meeting session. U se
attached accelerator as a template to prepare kickoff meeting materials specific to your project.
Romania
The purpose of this deliverable is to formally close the phase and conduct deliverable sign-off. During this time the project tea
will: Ensure that all required deliverables from this phase and the project are complete and accurate, and close any outstandi
issue Conduct formal Project Quality Gate Identify lessons learned during the phase Capture customer feedback and potentia
Customer References
The purpose of the Quality Gate is to ensure that both compliance and project management standards are being upheld with
projects. A Quality Gate is a checklist milestone at the end of a project phase . Prior to moving into the next phase each projec
manager demonstrates that they have been compliant with the mandatory deliverables associated with a methodology while
ensuring best practice standards have been applied to ensure quality. A Quality Gate looks at the following topics in detail:
Conduct regular quality checks at defined or critical stages of the project lifecycle to assess the health of the project To ensur
that all key deliverables and actions of the gate have been completed in compliance with recommended practices and to the
customer’s satisfaction To enable project management to continuously communicate the process and build quality directly in
the project To provide a tool to effectively manage project expectations and monitor customer satisfaction. The deliverables
assessed at each quality gate will be performed using the quality gate checklist with defined expectations to the maturity of
particular project deliverables. Note: New additional key deliverables need to be added in the quality gate checklist by the Pro
Manager to the different project types.
The purpose of this task is to conduct formal closure of the project phase and sign-off the deliverables completed during the
phase. The main goal of this process is to: Ensure that all required deliverables from this phase and the project are complete a
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 When sign-off is obtained, the project can proceed to the ne
phase. Use the attached sign-off sheet for this task.
The purpose of this phase is to perform a fit/gap analysis to validate the solution functionality included in the project scope an
confirm that the business requirements can be satisfied. Identified gaps and configuration values are added to the backlog for
in the next phase. Explore Activities: Prepare, setup and conduct solution validation workshops Refine business
requirements Identify master data and organizational requirements Confirm to be business processes Define
functional solution design, including a gap analysis in solution design workshops Associate business requirements to the pro
hierarchy and the solution components Obtain business sign-off on delta requirements and design documents Collect
user information, analyzing learning needs, and developing a learning deployment strategy Establish project managemen
tracking, and reporting for value delivery In the Explore phase, industry and solution experts from SAP lead a series of structur
show-and-tell and solution design workshops. The goal of these workshops is to review the best practice functionality of the S
solution, identify delta requirements or gaps and document the conceptual design of the to-be delivered SAP enterprise soluti
For on-premise projects , the team documents all functional and technical requirements, project issues, and gaps in SAP Soluti
Manager.
During the executing/monitoring of the project, the team carries out the planned and approved project work and measures
project performance to identify variances from the plan. Executing manages the scope of the work to be done, while monitori
monitors the execution, identifies variances from the plan, monitors quality results, controls progress against the plan, contro
changes throughout the project, assesses and responds to risks, and communicates project status. The Project Management
Plan developed during the Prepare phase for each of the PM knowledge areas guide the team's approach to management,
execution, monitoring, and control of project activities. This methodology provides steps to be considered when each activity
engaged, supported by the team's monitoring/controlling plans. The project manager is responsible for ensuring that the
monitoring/controlling plans developed in the planning phase are applied at the appropriate level of control. Additional
information for Premium Engagement implementations: The SAP TQM is responsible for oversight activities in projects that ar
run under the SAP Premium Engagement agreement (like Active Embedded or MaxAttention). The roles of SAP TQM and Proje
Manager are distinct with distinct responsibilities during the project delivery.
Romania
In directing and managing project execution , the project manager and the project team will perform actions to execute the
project management plan to accomplish the work defined in the project scope statement. In executing the project work, the
project team will perform the following types of activities: Perform project tasks to reach project objectives Expend effort and
funds to accomplish project objectives Staff, train, and manage the project team members assigned to the project Obtain,
manage, and utilize resources Implement and execute the planned methods and standards Create, control, verify, and validate
project deliverables Manage the scope of the approved work Manage risks and implement risk response activities Manage issu
to closure Adapt approved changes into the scope, plans, and project environment Establish and manage internal and externa
communications Collect project data and report on progress and performance In monitoring/controlling work results, the pro
team performs the following types of activities: Compare actual project performance to the project management plan Assess
performance to determine whether corrective or preventive actions are necessary Monitor and control project risks Provide
metrics to support progress and performance reporting and forecasting Monitor implementation of approved changes Take
corrective action as needed Management plans developed during the Prepare phase guide the team's approach to manageme
execution, and control of project activities. See “Prepare Project Management Plan” task in Prepare phase for details. The pro
manager is responsible for ensuring that the management plans are applied at the appropriate level of control.
The purpose of updating the project management documents task is to ensure that the project manager keeps the key projec
management documents up-to-date. This task includes refinement of the project schedule, refinement of the project budget,
appropriate updates to the management plans, scope document and business case to reflect the detailed scope information
created during the project. The project management document is a comprehensive body of project documents that include th
project schedule, budget/cost information, monitoring/controlling plans for each of the nine knowledge areas of the Project
Management Body of Knowledge (PMBOK), and other information as appropriate. The project management plan document
developed for each of the knowledge areas provide the foundation for the consistent application of project management
practices. This task includes updates to: Project management plan Project WBS Project schedule Project budget Business case
Scope document Backlog document (created in Explore phase)
A consistent, comprehensive approach to managing project issues is a critical component of an effective project management
system. Effective issue management involves the appropriate level of management making decisions on issues and tracking
progress on issue resolution in accordance with the project issue management procedure. Identified issues are maintained in
central environment. In on-premise projects this environment is the SAP Solution Manager, and depending on the type and st
may be directly transferred over to SAP for resolution. In cloud projects, teams are advised to use dedicated issue tracking
document based on the Open Issue List Template in the SAP Activate methodology. The Issue Management handling involves
following steps: An issue is raised and properly classified as it is related to the system conversion, solution implementation, or
solution operations of an SAP solution or technology. It is created in the issue tracking tool, either by SAP, a customer or a syst
integrator. During the issue creation the person raising the issues assigns the priority and the responsible person for resolution
the issue. The Project Manager follows up on issues on a regular basis in addition to the standard issue management process
defined for the project (part of the management plans) Critical issues will be reviewed as an input for each Quality Gate review
meeting. As a result, issues are documented in or in any issue tracking tool or system such as SAP Solution Manager. Open issu
are reviewed and updated on regular basis and communicated to the appropriate stakeholder groups as part of the regular
project reporting and communication. From SAP's perspective, issue tracking allows for better visibility and transparency of op
issues, problems, action items, and associated action plans to the project management team. A central issue tracking system
a support or an incident ticket system) allows stakeholders to manage and maintain lists of issues that require action and
resolution to ensure the success of the project.
Romania
Throughout the project, a number of project performance reports need to be produced for different purposes and audiences,
defined in the project communication plan . The project manager and project team are responsible for clearly communicating
progress of the key activities, completion of the deliverables and status against the schedule and budget. The project teams
typically prepare: Team member status update produced typically weekly and shared with the team lead. It is recommended t
this report is kept very lightweight and provided to the team lead via e-mail or in a team meeting Team status reports on regu
cadence, typically weekly. The team status reports are prepared by the team leads and are delivered to the project manager a
input for the project status report. The team status report may be reviewed in regular team review with Project Manager or
provided in a predefined format. Project status report , using the project status report template. The project status report is
created weekly, based on the input from individual teams and additional information like issues list, risk list, etc. Executive sta
report is typically prepared on monthly or quarterly cadence and is provided to the project executive steering group. Generally
this report re-uses the key information from the weekly project status report, expands on the value and benefits of the progra
and includes discussion of the decisions that are needed from the executive steering group. Additionally, throughout the proje
as more is known, the project communication matrix should be reviewed and updated. The communication matrix documents
project team’s approach to communication (including status reporting). It captures the analysis completed as part of
communications planning and serves as a tool to guide the project team throughout the project.
The purpose of this deliverable is to review the leading practices for fit to the customer's business processes. The review uses
iterative approach to assure that integrated dependencies are addressed. During Solution Validation, the SAP Cloud
implementation team demonstrates the functionality of the SAP Cloud solution and also the functionality of the SAP Best
Practices. The goal of the solution validation workshops are to:
1. Capture the fit of the SAP Cloud solution and the SAP Best Practices to the customer business process;
2. Document any changes from the SAP Best Practices that will be in scope for the project; and
3. Document any enhancement requests for the SAP Cloud solution. At the conclusion of the solution validation, all stakeholde
should be clear as to which business processes are in scope and how the SAP Cloud solution will support the business process.
The purpose of this deliverable is to capture and document the configuration changes to be used to configure the system in th
Realize phase. Configuration decisions will be captured in a workbook document. This deliverable occurs in parallel to the
business scenario workshops. The content is discussed in the workshop, however, the documentation is separate tasks.
The purpose of this task to document the configuration values determined during the Fit-Gap Analysis/Requirements Capturin
workshops. During the Fit to Standard Analysis, the business scenarios are demonstrated and validated. In addition, relevant
configuration settings are explored and possible changes are determined. These changes are documented for use by the proje
team in the Realize phase. Some configuration items may contain a couple items while others will be longer lists. The custom
responsible for providing the values that are appropriate to their business processes.
The purpose of this deliverable is to ensure proper set up of a Roles and Authorizations procedure and approach for the proje
The purpose of this task is to define or confirm on existing policies and procedures for access to physical office locations of the
project teammembers.
The purpose of this task is to provide selected users from the customer project team with training on the system permission a
authorization concepts. The intention is to setup a initial roles and permissions structure for the project and agree on a proced
for the further development of the role and permission structure. Throughout the projects progression the role and permissio
structure will expand and change. Increasing ownership of the role and permission model will be transferred to customer key
resources.
The purpose of this task is to review the available authorization roles and related settings and map them to the business user
roles.
Romania
The purpose of this deliverable is assurance that the systems being integrated to are compatible with the cloud system, setup
network security between the systems and develop specifications for extension fields (if required).
Apply all integration system prerequisites in the quality system. This might require installation of latest release functionality w
the SuccessFactors system, middleware or target/source systems that need to be integrated with.
The purpose of this task is to review system prerequisites for the systems, security and infrastructure and assure that systems
compatible.
The purpose of this task is to set-up network connectivity and security for any system within the overall landscape.
The purpose of this task is to confirm the fields to be integrated. The customer provides data mappings and value lists along w
the specifications for the adaptations.
The purpose of this deliverable is to validate the requirement for any solution extensions. Possible solution extensions could b
build by means of the SAP Cloud Platform, or possibly downloaded as pre-defined extensions from the SAP Marketplace. Inclu
of specific solution extensions might require additional configuration or development efforts and could be a cause for a chang
request. Also a license to SAP Cloud Platform is required for any custom solution development. Custom solution extensions wi
not be required for all implementation projects. SAP best practice advice is to try and keep solution configuration within the
confines of the standard configuration otions in order to retain the benefit of standard suport, quarterly release updates and
possible regression issues when the standard solution changes.
The purpose of this task is to identify a possible need for, and catalog custom extension requirements.
The purpose of this task is to create the specifications for the extensions. All of the field extensions and related logic are catalo
along with required logic. The documentation includes attributes such as screens, locations, data type, and validation logic.
The purpose of this deliverable is to prepare the source data and methods to extract the source data from legacy systems. The
Successfactors solution upload templates can be used as a baseline for the data collection and cleansing. Upload template file
structure and contents are configuration driven, and might change given changes in configuration definition throughout the
iterative process.
The purpose of this task is to perform data cleansing activities on legacy systems data or manual data. Typically, this is a custo
task and takes place in the customer legacy system.
The purpose of this task is to download the templates for data loads via the admin center. The SuccessFactors data upload
templates are configuration driven and will change dependent on specific customer configuration.
The purpose of this task is to define the specifications for data extraction programs/reports out of the legacy systems required
conversion to the new system. This is typically a customer task.
The purpose of this task is to define an overall load plan including sequence, expected data volumes and expected load times.
The purpose of this deliverable is to define the data privacy and security requirements related to the data stored within the
application. Local and regional rules and legislation should be taken into consideration in the definition of the data collection,
permissioning and storage.
The purpose of this task is understand and confirm on the different local and regional data privacy requirements. Local rules a
legislation could result in a need for technical processes, access restrictions and/or business processes activities in order to me
local policies.
The purpose of this task is to review data security classification of the impacted business data objects in order to identify
confidentiality, integrity, availability and access to the data.
The purpose of this task is define the policy around data storage and retention
The purpose of this taks is to consider and define different options and implications in regards to transferring data into and
outside of the solution.
The purpose of this task is to define and configure data privacy consent statement based on the classification of the data
elements, local legislation and company processes and policies.
Romania
will: Ensure that all required deliverables from this phase and the project are complete and accurate, and close any outstandi
issue Conduct formal Project Quality Gate Identify lessons learned during the phase Capture customer feedback and potentia
Customer References
Conduct regular quality checks at defined or critical stages of the project lifecycle to assess the health of the project To ensur
The purpose of this phase is to use a series of iterations to incrementally build and test an integrated business and system
environment that is based on the business scenarios and process requirements identified in the previous phase. During this ph
data is loaded, adoption activities occur, and operations are planned. Realize Activities: Establish the solution landscape
Implement the solution in the development environment using incremental build in time-boxed iterations Conduct overall end
end testing of the solution within the QA environment, Prepare for data migration and data archiving, Finalize end user trainin
materials and documentation Track and report on value delivery During Realize phase, the project team uses a series of iterati
to incrementally configure, test, confirm, and document the entire end-to-end solution and to create legacy data conversion
programs. The project team actively works with business representatives to ensure good fit of the built solution to the
requirements from the backlog. Project Team releases results of multiple iterations to the business users to accelerate time to
value and provide early access to finalized functionality. Each release is thoroughly tested in end-to-end integration test and u
acceptance test.
see 3.1.
communications Collect project data and report on progress and performance In monitoring/controlling work results, the proj
execution, and control of project activities. See “Prepare Project Management Plan ”task in Prepare phase for details. The pro
see 3.1.2 - Update project Management Documents

Romania
see 3.1.3 - Manage Project Issues, Risk and Changes
see 3.1.4 - Communicate Project Status and Progress

The purpose of this deliverable is to configure the system using the values determined in the Explore phase. As the solution is
configured, the functionality is demonstrated for confirmation from the implementation team. Additional learning takes place
during this process which may result in more adjustments.
The purpose of this task is to complete the configuration for customer options/changes identified in the scope validation
workshops, or throughout the iterative testing and feedback process. The solution will be configured based on the customer
based on the solution requirements as captured in the application design.
The purpose of this task is to determine and create the sample master data necessary for unit testing the configuration. The
sample data should be jointly determined so that it can be used for end-to-end scenarios. The data should be indicative of the
customers data and can be used in the solution walkthrough.
Purpose of this task is to define the output management strategy and configure the necessary settings in the Test system.
The purpose of this task is to unit test the configured solution by the person who entered the configuration. If an issue is foun
should be resolved immediately. This includes both configuration and master data.
The purpose of this activity is to demonstrate the configured solution to the project team. Thoughout the iterative process a
number of system demonstrations will be held to demonstrate current state configuration and to prepare the project team fo
testing and feedback collection process.
The purpose of this task is to capture any requested changes to the configuration based on the feedback provided by the proje
team. Changes to the configuration will be updated in the relevant configuration design (workbook) and will be fed into the
following cycle of configuration.
The purpose of this deliverable is to realize the development of the solution extensions as per the specifications that have bee
defined.
The purpose of this task is to request the development of solution extensions. This action might be required in the case that
offshore solution extension development is part of the project.
The purpose of this deliverable is to educate the customer project team on the standard reports and reporting functionality an
options that are available in the SAP system.
The purpose of this task is to introduce to the customer project team on the standard reports are available in the SAP system,
identify which particular ones are especially applicable to the customer per their requirements. Also general training on the
different reporting options and functionality will be provided to selected members within the customer organization.
The purpose of this deliverable is to demonstrate the configured solution to the customer project team for solution acceptanc
before customer testing will commence.
Romania
The purpose of the final solution walk through is to demonstrate the configured solution to the customer project stakeholders
gain first approval that the solution satisfies the business needs. The approval is also the trigger for the beginning of a more
comprehensive testing stream.
1. Schedule the walk through meeting
2. Decide on the scenarios to demonstrate on a live system. The scenarios should cover the critical business processes at a
minimum
3. Select data for use in the scenarios. It is best to connect the scenarios into a complete story with consistent data
4. Setup the scenarios. If integration or enhancements are required but not completed, a conceptual walk through can be crea
to explain how the process will work
5. Demonstrate the scenarios to the customers. Typically, the customer project team leads the meeting and demonstrates how
the solution will fulfill the business requirements. Some slides maybe necessary to help explain difficult topics, but the focus is
always on the system actions
6. Document and resolve issues
7. Obtain acceptance to proceed into testing
The purpose of this deliverable is to prepare for testing the business processes configured in the solution and to verify that the
meet the business needs.
The purpose of this task is to define the test cases, test scripts, and supporting test data to be used for customer solution testi
in accordance with the test plan. The test cases that are provided as part of the solution can be used as templates.
The purpose of this task is to create the test plan including resources and dates.
The purpose of this task is to provide the selected team of testers with sufficient training in regards to the testing process and
content and solution setup. This should provide the testers with required knowledge and skills to efficiently perform the testin
The purpose of this deliverable is to setup the integration(s) in the test system. Initial connectivity between systems needs to
setup, fields mapping needs to be performed and possible data transformations need to be configured.
The purpose of this task is to confirm the fields to be integrated. The customer provides data mappings and value lists along w
the specifications for the adaptations. Any delta changes to the integrations due to changes to the configuration that are trigg
by the iterative process need to be included into the integration fieldset documentation.
The purpose of this task is to create integration mappings and define transformations.
The purpose of this task is to set up integration on the cloud system.
The purpose of this task is to setup integration on the on-premise system.
The purpose of this task is to perform initial testing of the integration data tranfer, processsing logic and possible transformati
The purpose of this 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 skill level
knowledge gaps, and training requirements are located. This analysis contains the key customer information for definition of t
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 training material development and delivery plans and for a
education aspects of the project.
The purpose of this deliverable is to develop all end-user training materials and to provide all the end-user trainers with the
knowledge and assests that are required for effective knowledge transfer to the end-users
Romania
The purpose of this task is to develop all required training materials to enable training rollout for the project go-live. Materials
could consist out of items like training guides, instructional videos and workinstructions.
The purpose of this task is to upskill the end-user training team in order to provide them with sufficient knowledge, skill and
experience to be able to effectively roll out the training to the end users
The purpose of this deliverable is to develop, implement, and test the data migration programs and processes defined in the
Explore 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 te
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. This involves populating the data migratio
templates, uploading the data into the staging area of the migration tool, validating the data, simulating the load and executin
the data migration.
The purpose of this task is to execute and validate the manual data load and overall load process for testing.
The purpose of this task is to support with issue identification by the customer during the data load process.
The purpose of this task is to provide one final assessment at the end of the realize phase to report on the quality of the loade
data. Once all tests and queries have been conducted, the data migration team compiles the results and requests a preliminar
review by the data owners and subject matter experts (SMEs). Once the data owners and SMEs have provided feedback, the t
prepares the final findings as a written report or verbal presentations to be delivered to key stakeholders. Depending on the
requirements, the final data quality report includes topics such as:
• Updated data mappings and business rules
• Summary of data quality metrics for all the business objects
• Data profiling results of selected data
• Any outstanding data quality issues that need to be resolved At the end of this task, the data migration team can move into
next phase with the confidence that the vast majority of data quality issues and migration issues have been resolved and
mitigated.
The purpose of this deliverable is to perform the customer solution, business process and integration testing according to the
defined plan.
The purpose of this task is to test the solution and business processes according to the previously defined plan. During the tes
incidents must be logged and documented for traceability purpose.
The purpose of this task is to resolve any incidents identified during testing. It is crucial that the issues are re-tested by users t
reported them (or designated re-testers) and that they are confirmed.
The purpose of this 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 this deliverable is to establish technical operations monitoring and support processes and to ensure that the p
production support organization has its strategy in place. The handover plan can contain policies for operational and technical
solution support, enhancement and change management.
The purpose of this task is for the customer to setup or validate that the proper support processes (Help Desk) are in place for
post go live. The customer organization must be able to: Communicate problems internally Troubleshoot data issues or impro
setup of object Research issues Escalate to SAP support if no solution/cause can be found
The purpose of this activity is to define, align and communicate the operational business process that will be appliable after G
Live
The purpose of this deliverable is to document the strategy, scope and timelines for moving from the as-is solution to the to-b
solution and the hyper care period immediately following go-live.
Romania
The purpose of this task is to determine and document the strategy, scope and timeliness for moving from the as-is solution to
to-be solution and the hyper care period immediately following go-live. This includes a workshop introducing SAP's Best Practi
and documenting activities such as the transfer of data from the legacy systems to the SAP software production system, settin
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 accelerators include a sample
document for cutover strategy. It is a high-level plan. You can add details such as execution logistics, detailed plan for cutover
kickoff. Similarly, you can begin with a high-level cutover schedule, then add details from each team's cutover plans, and end w
the final cutover schedule. The cutover schedule is tested and improved during the simulated cutovers. However, if the sched
is prepared early enough, it may also be tested when building the QA or training environment.
will: Ensure that all required deliverables from this phase and the project are complete and accurate, and close any outstandin
issue Conduct formal Project Quality Gate Identify lessons learned during the phase Capture customer feedback and potential
Customer References
Conduct regular quality checks at defined or critical stages of the project lifecycle to assess the health of the project To assure
The purpose of this task is to conduct formal closure of the project phase and sign-off the deliverables completed during the
phase. The main goal of this process is to: Ensure that all required deliverables from this phase and the project are complete a
accurate, and close any outstanding issues Identify lessons learned during the phase to prepare for formal project closure Cap
customer feedback and potential customer references When sign-off is obtained, the project can proceed to the next phase.
the attached sign-off sheet for this task.
The purpose of this phase is to setup the production system, confirm customer organization readiness, and to switch business
operations to the new system. Deploy Activities:
Resolve all crucial open issues: Conduct system tests Check that system management is in place
Proceed with cut-over activities, including data migration Execute transition and cutover plans including organizati
change management (OCM) plans Complete all scheduled end user training Identify and document all issues encounter
in the transition to the new solution Monitor business process results and the production environment Establish OCC**
“extra-care” center of excellence for support that provides: Production support processes
Exceptional business monitoring processes Extraordinary technical support System enhancements
Track and report on value delivery
see 3.1.
see 3.1.2 - Update project Management Documents

see 3.1.3 - Manage Project Issues, Risk and Changes
see 3.1.4 - Communicate Project Status and Progress

Romania
communications Collect project data and report on progress and performance In monitoring/controlling work results, the proj
execution, and control of project activities. See “Prepare Project Management Plan” task in Prepare phase for details. The pro
The purpose of this deliverable is to perform the cutover to the production software and go live. At the finalization of the
production cutover the organizational, business, functional, technical, and system aspects of the project are ready to be used
production.
The purpose of this task is to execute the steps identified and tested in the cutover plan.
The purpose of this task is to ensure the production system is available and ready to execute the cutover activities.
The purpose of this task is to setup and confirm availability of user IDs for project team members in production system. This
includes the setup of required useraccounts and access of the implementation team as well as the requirexd access to custom
project team members to be able to perform the final production validation.
The purpose of this task is to migrate all required configuration from the Quality environment to the production environment.
includes any manual system generic settings as well as any solution specific cofigurations.
The purpose of this deliverable is to setup all integrations in the production system. This includes the possible installation,
configuration and setup of any of the integrated systems. The testing and validation of the connectivity and data transfers
between related systems.
The purpose of this task is to apply all integration prerequisites to all integrated systems. This might mean the installation of la
support packs, software upgrades and add-ons.
The purpose of this task is to set up network security and connectivity to all integrated systems.
The purpose of this task is to configure integration between the cloud system and related systems.
The purpose of this deliverable is to execute initial integrated data load into the production system. This includes any manual
loading activities and automated load processes. Resolution of any load errors as well as validation of data quality, completen
and accuracy are included in this deliverable.
The purpose of this activity is to validate all datasets that need to be migrated. Final checks of the finalized upload templates.
Confirmation on the availability of the required configuration and field settings. Confirmation on data load permissions, load
sequence and/or integration load schedule and system availability.
The purpose of this task is to perform the initial dataload
The purpose of this task is to validate the data load results. Confirm on data completeness, accuracy and consistency.
The purpose of this deliverable is to deploy and validate any solution extensions into the customer landscape.
The purpose of this task is to deploy solution extensions in the production system.
The purpose of this deliverables is to execute end user training and finalize communication to the end users prior to go-live.
The purpose of this task is to deliver end user training according to the previously developed training schedule.
Romania
The purpose of this task is to establish and communicate the internal support process to the users.
The purpose of this deliverable is to transfer from a project support environment to a production support environment. A clo
system requires extra coordination with support to provide assurance to the customer that support is monitoring and readily
accessible in the event of an issue.
The purpose of this task is for support services to introduce themselves and take ownership of the support and monitoring of
productive system. Since the system is a cloud system, it is important that the customer knows who will be supporting the sys
from SAP and the proper methods of engaging with them when concerns, questions or problems arise. The support organizati
will schedule and conduct the meeting prior to go live.
The purpose of this deliverable is to provide sufficient and timely support of the transition to production process to ensure
stabilization of the solution and related business processes. During the production hypercare support period the operational
processes will be embedded into the organization.
The purpose of this activity is to provide a pre-defined period of hypercare in order to stabilize the solution, business processe
and to ensure timely and adequate response in case of urgent go-live issues
The purpose of this deliverable is to formally close theproject and conduct deliverable sign-off. During this time the project
teamwill: Ensure that all required deliverables from thisthe project are complete and accurate, and close any outstanding issu
Conduct formal Project Quality Gate Identify lessons learned during the phase Capture customer feedback and potential
CustomerReferences
The purpose of the Quality Gate ia to ensure that both compliance and project management standards are being upheld with
our projects. A Quality Gate is a checklist milestone at the end of a project phase. Prior to moving into the next phase each pro
manager must demonstrate that they have complied with the mandatory deliverables associated with a methodology while
ensuring best practice standards have been applied to ensure quality. In detail: To assure that all key deliverables and actions
the gate have been completed in compliance with recommended practices and to the customer’s satisfaction To enable proje
management to continuously communicate the process and build quality directly into the project To provide a tool to effective
manage project expectations and monitor customer satisfaction. The deliverables assessed at each quality gate will be perform
using the quality gate checklist with defined expectations to the maturity of particular project deliverables. Note: New additio
key deliverables need to be added in the quality gate checklist by the Project Manager to the different project types.
The purpose of this task is to conduct formal closure of theproject execution and sign-off the deliverables completed during th
project.The main goal of this process is to: Ensure that all required deliverables from theproject are complete and accurate, an
close any outstanding issues Identify lessons learned during the project(collection of all lessons learned from the project) Capt
customer feedback and potential customerreferences When sign-off is obtained, the project can be formallyclosed.
The purpose of this phase is to further optimize and automate the operability of the solution. Operability is the ability to main
IT systems in a functioning and operating condition, guaranteeing systems availability and required performance levels to supp
the execution of the enterprise’s business operations.
The Purpose of the Functionality release management deliverable is a quartery assesment, validation and activation of the
product updates and new features/functionality that are included in the quarterly release process.
The purpose of this task is to evaluate the new system features and enhancements that are being released on a quarterly basi
Customers can make use of the release information summaries and product update webinars sessions made available in adva
of the quarterly release.
SuccessFactors preferred care customers will have a quarterly release readiness meeting with their respective Customer Succe
Manager (CSM). During this meeting the Customer and the CSM will review and discuss release functionality and will analyze
opportunities and impacts to include this in the current configuration.
Romania
New release functionality will be available on the preview release environments one month in advance of the production relea
This will give customers the opportunity to test any new functionality and evaluate if the new functionality would provide a
valuable improvement within the companies current operational processes. Customers should perform preview release testin
any product updates that they intend to activate. Preview release testing should capture any regression effects on existing
functionality, processes and integrations.
New release functionality can be activated into the customer production system and included into operational processes. Syst
administration roles can activate functionality by use of the successfactors upgrade center within the SuccessFactors solution.
parallel to the update of the customer production instance, system admin role will have to ensure appropriate permissioning o
the new functionality through the SuccessFactors permissioning model.
Any new functionality or process changes will have to be communicated to impacted users
Within the operations monitoring and management deliverable, customers will monitor the performance, response times and
availability of their SuccessFactors solution. Also management of outage and planned maintenance windows will need to be
monitored and managed.
SuccessFactors customers have the opportunity to do detailed monitoring of SLA's and system availability throughout the diffe
datacenters. SuccessFactors customers are able to retrieve reporting on system availability and performance in the cloud
availability center within their support launchpad and in the cloud support portal.
Customers have possibilities for ongoing knowledge management and learning throughout their customer lifecycle. There are
possibilities to share experiences and information by means of peer matching learning, community user groups and value and
innovation in practice evenents (VIP). For specific operational or how-to questions, customers can use the SuccessFactors
knowledge base, wiki pages and community discussion forums In-depth learning and training opportunities are available on th
Cloud Learning Hub.
SuccessFactors customers can use the peer matching program to connect with peers for extended learning and knowledge
sharing. The peer matching programme allows customers to find similar SuccessFactors customers in repespect of functionalit
scope, company size, industry and business activities. The community usergroups within the customer community give custom
the opportunity to connect and collaborate with other SuccessFactors customers within the same region. The community prov
a dedicated scope for usergroup to communicate, share information and raise questions.
This purpose of this deliverable is to gain in-depth knowledge of the solution and its administration and configuration options
SAP provides extensive training programmes and accreditation learning paths to provide customers with in depth knowledge o
solution configuration administration options. Customer SuccessFactors administrators can follow several learning Solution
accreditation will ensure ongoing awareness and knowledge of system functionality and administration tasks
The purpose of the Roadmap and enhancement deliverable is to perform long term planning of the overall solution direction,
SuccessFactors functionality roadmap and system enhancements
The purpose of this activity is to do a recurring review of the product solution roadmap. Up to date Product Solution roadmap
posted on the SuccessFactors community.
The purpose of this activity is to suggest any functionality enhancements that would add any value to the overal solution scop
SuccessFactors community members will be able to suggest roadmap ideas through the customer community roadmapping to
Befor suggestnig new ideas a search need to be performed to confirm that the idea has not been suggested previously. In case
already suggested ideas, there is a possibility to vote and increase the popularity of a certain suggested functionality
enhancement.
The purpose of this deliverable is to confirm that the resources and processes are in place to support the ongoing solution and
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.
Romania
Access Level Workstream Tags Activity Group
phase Public
deliverable Public Application: Design & Configuration
task Public Application: Design & Configuration
Public Application: Design & Configuration
task Public Application: Integration
deliverable SAP Employee Project Management
Public Project Management
deliverable Public Project Management

Romania
phase Public
deliverable Public Application: Customer Team Enablement
task Public Application: Customer Team Enablement
task Public Project Management

Romania
activity Public Project Management

Romania

Romania

Romania
q-gate Public Project Management
phase Public
Execution Public Project Management

/Monitoring
Romania
task - pm docs Public Project Management
task - risk, issue, Public Project Management

changes
Romania
task - progress Public Project Management

Romania
deliverable Public Application: Integration
Public Application: Integration

deliverable Public Custom Code Extensions
task Public Custom Code Extensions

deliverable Public System & Data Migration
task Public System & Data Migration



Romania
phase Public

/Monitoring

Romania

changes

activity Public Application: Design & Configuration

Romania
Public Application: Design & Configuration
deliverable Public Application: Testing
task Public Application: Testing


deliverable Public Application: Solution Adoption
task Public Application: Solution Adoption

Romania

task SAP Partner System & Data Migration
task SAP Partner System & Data Migration
deliverable Public Application: Testing
deliverable Public Transition to Operations

task Public Transition to Operations
activity Public Transition to Operations

Romania
phase Public

/Monitoring
changes
Romania


activity Public System & Data Migration

Romania

activity Public Transition to Operations
phase Public
Public Application: Solution Adoption

Romania

Public Transition to Operations
Public Transition to Operations


Romania
Q-Gate Relevance
Romania
Optional
Romania
Mandatory
Romania
Mandatory
Romania
Mandatory
Optional
Romania
Mandatory
Mandatory
Optional
Optional
Mandatory
Romania
Mandatory
Romania
Mandatory
Romania
Q-Gate Key Deliverable

Romania
Authorization Requirements and Design

Romania
Delivery of projects ResultsDelivery Acceptance Protocol

Romania
Training Project Plan
End User Training and Documentation Developed

Romania
Data Migration Design / Plan
Test cases & Results
System User Roles and Authorization AdministrationandSystem Authentication Management
Technical Operations and Handover Strategy
Production Cutover Plan

Romania

Romania

Romania
Effort Days Day Number Duration Days Customer Accountability Accountable Delivery mode
1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
Romania
1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000 Remote
0 1.000 0.000 X
0 1.000 0.000
1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
Romania
0 1.000 0.000
1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000 On-Site
1.000 0.000
1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000 On-Site

Romania
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000 X
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
1.000 0.000
0 1.000 0.000 On-Site
1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
Romania
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000 Remote
1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000 On-Site

0 1.000 0.000
0 1.000 0.000 On-Site
1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000 On-Site
1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000
1.000 0.000
Romania
0 1.000 0.000 Remote
1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000 On-Site
1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000 X
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000 On-Site
0 1.000 0.000 Remote
1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
Romania
0 1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
0 1.000 0.000
1.000 0.000
0 1.000 0.000
Romania
Accountable Deployment mode Assembly Category Unique ID Accelerators Assigned
3221
3222
3223
3224
3225
3226 S4H_357
3227
3228
3229
3230
Romania
33
780
Non-core (N) 775 ALM.21,S4H.0541,S4H_358
Local Core (C) 955 S4H_348
Non-core (N) 781 S4H_161,S4H_163,S4H_162
3382
2028
Non-core (N) 770 S4H_359

Romania
3383
2030 AG.03,PM.04
2031 PM.21,PM.98,PM.99,S4H_360
2032
Romania
2033 AG.17,S4H_383
2036
2037 ALM.26
Romania
2039
3384
2033
2034 PM.10
2035 PM.13,S4H_362
Romania
142
Local Non-core (N) 144 PM.205,PM.84,PM.206
Local Non-core (N) 146 PM.94,S4H_349,S4H_363
148
2045
Romania
2046
2047
2048
Romania
2049
176
786
Core (C) 881
214
3389
3390
Nearshore Non-core (N) 215

Romania
788
Core (C) 792
Core (C) 790
Core (C) 791

Core (C) 793
795
Core (C) 796

Core (C) 797
815
Non-core (N) 816
Non-core (N) 817
Non-core (N) 818 S4H_132,S4H_133,S4H_134,S4H_135,S4H_136
3473
3400
3401
3402
3403
3404
3405
Romania
230 S4H_364
Local Non-core (N) 232 PM.205,PM.84,PM.206
237
2054
2055
2056
Romania
2058 S4H_371
2059
805
Core (C) 806
Local Core (C) 1000
Core (C) 808

Core (C) 809
3477
3406
810
Core (C) 812
749
Non-core (N) 750
743
Romania
Core (C) 745
819
820
821
3407
822
3409
Core (C) 823

Core (C) 825
Core (C) 826
3408
167
Local Non-core (N) 168 BB.59,BB.58
Local Non-core (N) 169 BB.62
3410
Romania
3411
3412
343
Nearshore None (NONE) 345

884
Nearshore None (NONE) 349 S4H_138
831
Non-core (N) 832
Non-core (N) 835
383
385
3413
253 S4H_365
Romania
Nearshore Non-core (N) 257 R.169,R.168
391
Local Non-core (N) 393 PM.84
Local Non-core (N) 396 PM.94,S4H_365
398
2060
2061
2062
2063
Romania
5061
424
Core (C) 883

3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
Romania
3429
865
Non-core (N) 867
3430
3431
472
Local Non-core (N) 474 PM.84
Nearshore Non-core (N) 479 GL.27,GL.28,S4H_365
481
3432
3433 S4H_350
3434
Romania
3435
3436
3437
3438
3439 S4H_351
3440
3441 S4H_352,S4H_353
3442
3443 S4H_354
3444
3445 S4H_355
3446
3447
3448
Romania
Role Id Role Type Effort(Onsite) Effort(Remote) Effort(Customer) Role Id Role Type Effort(Onsite)
1 Accountable 0.000 0.000 0.000
1 Accountable 0.000 0.000 0.000
1 Accountable 0.000 0.000 0.000
1 Accountable 0.000 0.000 0.000
2 Accountable 0.000 0.000 0.000
2 Accountable 0.000 0.000 0.000
2 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
5 Accountable 0.000 0.000 0.000
4 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000

6 Accountable 0.000 0.000 0.000
8 Accountable 0.000 0.000 0.000

Romania
5 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
9 Accountable 0.000 0.000 0.000 3 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
10 Accountable 0.000 0.000 0.000
10 Accountable 0.000 0.000 0.000

Romania
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
12 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
11 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000
7 Accountable 0.000 0.000 0.000

Romania
12 Accountable 0.000 0.000 0.000
5 Accountable 0.000 0.000 0.000
4 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

Romania
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000

3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
13 Accountable 0.000 0.000 0.000

13 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000

6 Accountable 0.000 0.000 0.000
13 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000

Romania
6 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
2 Accountable 0.000 0.000 0.000
5 Accountable 0.000 0.000 0.000
3 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000

Romania
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000
6 Accountable 0.000 0.000 0.000

Romania
Effort(Remote) Effort(Customer) Role Id Role Type Effort(Onsite) Effort(Remote) Effort(Customer) Role Id

Romania
0.000 0.000
Romania
Role Type Effort(Onsite) Effort(Remote) Effort(Customer) Role Id Role Type Effort(Onsite) Effort(Remote)
Romania
Effort(Customer) Role Id Role Type Effort(Onsite) Effort(Remote) Effort(Customer) Role Id Role Type
Romania
Effort(Onsite) Effort(Remote) Effort(Customer) Role Id Role Type Effort(Onsite) Effort(Remote)

Romania
Romania

Romania
Romania

Romania
Effort(Customer)
Romania
WBS Role ID Description Service Provider or Customer Job Profile

1 Service Provider Principal Business Consultant
2 Service Provider Project Manager
3 Service Provider Project Manager
4 Service Provider Project Management Specialist
5 Service Provider Business Process Architect
6 Service Provider Customer Business Lead
7 Service Provider Senior Technology Consultant
8 Service Provider Business Process Consultant
9 Service Provider Business Process Consultant
10 Service Provider Education Senior Consultant
11 Service Provider Senior Technology Architect
12 Service Provider Senior Business Process Consultant
13 Service Provider Senior Technology Consultant
Romania
IPP Object ID Career Level Deployment mode Solution Profile Group Consulting Solution Profile
30000251 Expert Local
30000006 Senior Local
30000006 Senior Nearshore
30000278 Specialist Local
Local
30000257 Specialist Offshore
Romania
IPP Sol. Pro. ID Consulting Industry Focus IPP Ind. F. ID Service Element
Strategy,Architecture and Expert Services
Project Management
Project Management Support
Project Management
Design Services
Strategy,Architecture and Expert Services
Execution Services
Design Services
Execution Support Services
Design Services
Execution Services
Execution Services
Design Services
Romania
Price Rate Effort(Onsite) Effort(Remote) Effort(SAP) Effort(Customer)

G1 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
G3 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
G1 0.000 0.000 0.000 0.000
G3 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
G4 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
G3 0.000 0.000 0.000 0.000
G3 0.000 0.000 0.000 0.000
G2 0.000 0.000 0.000 0.000
TOTAL 0.000 0.000 0.000 0.000
Romania
WBS Accelerator ID Title
AG.03 Agile Project Team Roles and Responsibilities
AG.17 Agile Release Planning

ALM.21 SAP Support Portal
ALM.26 SAP Solution Manager and tools
BB.58 OCM Learning Needs Analysis Guide
BB.59 Learning Needs Analysis for ECO Ltd Sample
BB.62 Training Project Plan Sample

Project Closeout Report Presentation
GL.27 Template
Project Closeout Report Template - NO

GL.28 LONGER VALID
Project Organization Roles and
PM.04 Responsibilities Template
On-Boarding Document Template - NO
PM.10 LONGER VALID
PM.13 Project Kick-off Template

Project RDS Quality Gate Scorecard
PM.205 Template
PM.206 A2O Quality Gates
PM.21 Communication Plan Overview Template

Project Quality Gates in PtD -Training - NO
PM.84 LONGER VALID
PM.94 Phase SignOff Template
PM.98 OCM Stakeholder Identification Guide
PM.99 OCM Stakeholder Identification Template
R.168 MS Project Cutover Schedule Sample

Preliminary Cutover Strategy Presentation
R.169 Template
S4H.0541 SAP Best Practice Explorer
Functional and Implementation
S4H_132 Design_Template
Romania
S4H_133 Technical Design_Template
S4H_134 Manual Data Migration Design_Template
S4H_135 Test Data Management Overview
S4H_136 Testing Strategy_v07
S4H_138 Data Quality Assessment Whitepaper
S4H_161 SAP S/4HANA Overview Learning Room

SAP S/4HANA Implementation Learning
S4H_162 Room
S4H_163 Activate Learning Room for SAP S/4HANA
S4H_348 SuccessFactors Community Services
S4H_349 Preparation Quality Gate
S4H_350 Road to the Release: Overview Diagram
S4H_351 SuccessFactors Cloud Availability Center
S4H_352 Peer Match Search
S4H_353 SuccessFactors Community Groups
S4H_354 SuccessFactors Community Training
S4H_355 New Roadmapping Tool
S4H_357 RACI Matrix
S4H_358 Customer Cloud Admin - Request for S Users
S4H_359 SS to PS Internal Transition

Romania
S4H_360 Project Status Template
S4H_362 Project Kickoff Deck
S4H_363 Preperation Quality Gate
S4H_364 Explore Quality Gate
S4H_365 Final Preparation Quality Gate
S4H_371 Project Log/Action Tracker.xlsx
S4H_383 SuccessFactors Project Plan

Romania
Description
Presentation explaining Agile project team roles and
responsibilities. Focusing on new roles and responsibilities
introduced by Agile approach.
Presentation explaining approach to release and sprint planning in
Agile project.
SAP Support Portal
SAP Solution Manager and tools
A guide on the importance of a LNA and why this is needed.
A sample document of a Learning Needs Analysis
A sample of a training plan schdeule.
A template presentation for the project closeout report.

The Project Closeout Report documents that the project has met
all requirements for the final product/deliverable and that the
Customer accepts the product/deliverable.
A template presentation outlining the project organization and
related roles.
Template used to outline and document the on-boarding
procedures on the project.
A template for the presentation that is used in the kick-off
workshop to align on activities and responsibilities, and present the
scope of the project.
The Project Quality Scorecard for RDS records the results of the
Quality Assements for the Phase Start & Phase Deploy & Run
The Project Quality Documents for A2O

A template used to provide an overview of the communication
plan of te project.
A guide on quality gates and quality processes using PtD .
Template used to capture the sign off of phase deliverables.
A guide on how to perform stakeholder identification.
A template used for stakeholder identification.
Sample of an MS Project Cutover Schedule
Template used for the prelimenary cutover strategy presentation.

SAP Best Practice Explorer
Functional and Implementation Design_Template

Romania
Technical Design_Template
Manual Data Migration Design_Template
Data Security Design_v07
Testing Strategy_v07
Data Quality Assessment Whitepaper
SAP S/4HANA Learning Room by SAP Education

SAP S/4HANA Implementation and Configuration Learning Room
by SAP Education
SAP Activate Learning Room for SAP S/4HANA by SAP Education

SuccessFactors Community Services
Preparation Quality Gate
Road to the Release: Overview Diagram
SuccessFactors Cloud Availability Center
Peer Match Search
SuccessFactors Community Groups
SuccessFactors Community Training
New Roadmapping Tool
RACI Matrix
Customer Cloud Admin - Request for S Users
SS to PS Internal Transition
Romania
Project Status Template
Project Kickoff Deck
Preperation Quality Gate
Explore Quality Gate
Final Preparation Quality Gate
Action Tracker.xlsx
SuccessFactors Project Plan

Romania
Filename Accelerator Type Access Level
Agile-ProjectTeamRolesandResponsibilities.ppt Reference material SAP Customer
AgileReleasePlanning.ppt Reference material SAP Customer

Reference material SAP Customer
LearningNeedsAnalysis_Guide_2009.doc Reference material SAP Customer

LearningNeedsAnalysisforECOLtd_Sample_2009_v07.do
c Sample SAP Customer
TrainingProjectPlan_Sample_2009_v07.xls Sample SAP Customer
ProjectCloseoutReportPresentationTemplate.ppt Template SAP Customer
NProjectCloseoutReport_template_2009.doc Template SAP Customer
Project_Organization_Roles_and_Responsibilities.pptx Template SAP Customer
On-BoardingDocument_Template.ppt Template SAP Customer
ProjectKick-offProject.xxX_Template.ppt Template SAP Customer
ProjectRDSQualityGateScorecardTemplate Template SAP Customer
A2OQualityGates Template SAP Customer
CommunicationPlanOverview_Template_2009.ppt Template SAP Customer
ProjectQualityGatesinPtD_Presentation Reference material SAP Employee
PhaseSignOff_Template.doc Template SAP Customer
ASAP_Prep_OCM_StakeholderIdentification_guide.ppt Reference material SAP Customer

ASAP_Prep_OCM_StakeholderIdentification_template.x
ls Template SAP Customer
5.6.1SAPMSProjectCutoverSample.mpp Sample SAP Customer
4.7.1PreliminaryCutoverStrategy.ppt Template Public

How-to Guide Public
Reference material Public

Romania
How-to Guide SAP Customer
Reference material SAP Employee
Reference material SAP Employee
Template SAP Employee

Romania
Template Public

Romania
Workstream Source URL
Agile https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_03.pptx
Agile https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_17.ppt
Application: Solution Adoption http://support.sap.com
Application: Solution Adoption http://service.sap.com/alm-tools
https://service.sap.com/~sapidb/
011000358700001272462012E/
Application: Solution Adoption LearningNeedsAnalysis.doc
https://service.sap.com/~sapidb/
011000358700001264792012E/
Application: Solution Adoption LearnNeedsAnalysisECO_Ltd.doc
Application: Solution Adoption https://support.sap.com/content/dam/SAAP/SAP_Activate/BB_62.xls

https://support.sap.com/content/dam/SAAP/
Project Management SAP_Activate/GL_27.ppt
Project Management SAP_Activate/GL_28.doc
Project Management https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_03.pptx

Project Management SAP_Activate/PM_10.ppt
Project Management SAP_Activate/PM_13.pptx
Project Management SAP_Activate/PM_205.xlsx
Project Management https://service.sap.com/~sapidb/011000358700000592402013E/A2OQual

Application: Solution Adoption SAP_Activate/PM_21.ppt
Project Management https://portal.wdf.sap.corp/go/svu
Project Management https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_94.doc

Application: Solution Adoption SAP_Activate/PM_98.ppt
Application: Solution Adoption SAP_Activate/PM_99.xls
System & Data Migration SAP_Activate/R_168.mpp
System & Data Migration SAP_Activate/R_169.ppt
Application: Design & Configuration https://rapid.sap.com/bp/
System & Data Migration SAP_Activate/S4H_132.docx
Romania
System & Data Migration https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_136.doc

System & Data Migration SAP_Activate/S4H_138.pdf
https://jam2.sapjam.com/groups/about_page/
Training - Training MDC2ZYZbpZMMK7U0U3VVfK
Training - Training 5gwxDPWQPRtOvMO8Xnd32Q
Training - Training fHaQLt0HVw1NHeKIaGu0MG
https://community.successfactors.com/t5/Services/ct-
Application: Customer Team Enablement p/services
https://jam4.sapjam.com/groups/
HD0HLqmfrcLi2xx3z8AnG9/documents/
Project Management K5Tfr3cdfnCfc1Myu6zCc8/slide_viewer?_lightbox=true
https://community.successfactors.com/t5/Road-to-the-
Release/Road-to-the-Release-Overview-Diagram/ba-
Application: Solution Adoption p/158645
Transition to Operations https://launchpad.support.sap.com/#/cac

https://community.successfactors.com/t5/user/
Application: Solution Adoption myprofilepage/tab/personal-profile%3Apeer-advisor
https://community.successfactors.com/t5/Groups/ct-
Application: Solution Adoption p/Groups
https://community.successfactors.com/t5/Training/ct-
Application: Solution Adoption p/Training
https://community.successfactors.com/t5/Resources-
Application: Design & Configuration and-Updates/New-Roadmapping-Tool/ba-p/146612
Project Management https://documents.wdf.sap.corp/share/page/site/sap-activate/document-d
https://documents.wdf.sap.corp/share/page/site/sap-
activate/document-details?nodeRef=workspace://
Application: Customer Team Enablement SpacesStore/dfc81f64-9f2b-4f02-9851-c9afa395a7fa
Project Management SpacesStore/ba1474e7-556f-420c-8a49-7c1d88b41ef7
Romania
Project Management SpacesStore/d190c32d-8a0b-4396-a10a-f10a747606d4
Project Management SpacesStore/e838a578-aae5-43ab-ae48-fa9a3a87c194
Project Management SpacesStore/2a389395-8907-4558-869a-095b3ed67c06
Project Management SpacesStore/60380fd1-659f-459d-bf59-e1fab0e006f9
Project Management SpacesStore/5a00f231-4dcb-4e48-845b-028e0c046de4
PM - Project Management https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_371%20A

SAP_Activate/S4H_383%20SuccessFactors%20SAP
Project Management %20ACTIVATE%20Project%20Plan%20Template.mpp
Romania
Is Accelerator generic
X
X
X
X
Romania
File Mime Type File Extension
application/vnd.ms-powerpoint PPT
text/html HTM
text/html HTM
application/msword DOC
application/vnd.ms-excel XLS
application/x-zip-compressed ZIP
application/x-zip-compressed ZIP
text/html HTM
application/vnd.ms-excel XLS
application/vnd.ms-project MPP
text/html HTM
application/vnd.openxmlformats-officedocument.wordprocessingml.document DOCX
Romania
application/pdf PDF
text/html html
text/html html
text/html html
text/html HTML
text/html HTML
text/html HTML
text/html HTML
text/html HTML
text/html HTML
text/html HTML
text/html HTML
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet XLSX
application/octet-stream MSG
Romania
application/vnd.openxmlformats-officedocument.presentationml.presentation PPTX
application/vnd.openxmlformats-officedocument.presentationml.presentation PPTX
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet XLSX
application/vnd.ms-project MPP
Romania
Publishing Indicator Tags

WBS-ul SuccessFactors

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WBS-ul SuccessFactors

Uploaded by

Copyright:

Available Formats

Information Type: Working Standard_x000D_Disclosure Range: _x000D_Information Owner: dan.

olovinaru_x000D_Company: NTT DATA

SAP Activate Methodology for SuccessFactors

<div id="left" style="float:left; width:70%">

<p style="margin-left:0in; margin-right:0in"><span style="color:#000000"><span style="font-family:Calibri"><span style="font

<p style="margin-left:0in; margin-right:0in"><span style="color:#000000"><span style="font-family:Calibri"><span style="font

<p><img alt="" src="https://support.sap.com/content/dam/SAAP/SAP_Activate%20Images/IMG_265.png" /></p>

<div id="right" style="float:right; width:30%">

Sequence Number Title

1.1 Solution Scope Definition

1.1.1 Solution Value and Functionality Demonstrations

1.1.2 Target Solution Model Determination

1.1.3 Solution Architecture Definition

1.1.4 Integration Architecture Definition

1.2 Implementation Scenario and Scope Definition

1.2.1 High Level Implementation Approach and Phasing

1.2.2 Effort Estimations

1.3 Scope Statement

1.3.1 Develop Scope Statement

2.1 Customer Team Self-enablement

2.1.2 Provide Customer with Links to Learning Materials

2.1.3 Review Self-enablement Materials

2.1.4 Complete self-assesment questionnaires

2.2 Project Initiation and Governance

2.2.1 Conduct Handover Meeting with Sales

2.2.2 Align Project objectives, benefits and scope

2.2.3 Establish Project Governance

2.2.4 Define Project Communications and Reporting

2.3 Project Plans, Schedule and Budget

2.3.1 Create Project Schedule and Budget

2.4 Project Standards, Infrastructure, and Solution

2.4.1 Define Project Standards

2.4.2 Setup Project Team Logistics and Infrastructure

2.4.3 Confirm provisioned systems availability

2.5 Project Kick-Off and On-Boarding

2.5.1 On-board Project Team

2.5.2 Conduct Kickoff Workshop

2.6 Phase Closure and Sign-Off Phase Deliverables

2.6.1 Conduct Project Quality Gate

2.6.2 Obtain Customer Sign-Off for Phase Completion

3.1 Execution/Monitoring of Project

3.1.1 Direct and Manage Project Execution

3.1.2 Update Project Management Documents

3.1.3 Manage Project Issues, Risk and Changes

3.1.4 Communicate Project Status and Progress

3.2 Fit-Gap Analysis/Requirements Capturing

3.3 Configuration Definition

3.3.1 Define Configuration Values

3.4 User Access and Security

3.4.1 Physical access and Security

3.4.2 Authorization and Permission Training

3.4.3 Authorization Roles and Assignments

3.5 Integration Preparation

3.5.1 Apply Integrated System Prerequisites

3.5.2 Confirm Integration Prerequisites

3.5.3 Set Up Network Connectivity and Security

3.6 Solution Extension Preparation

3.6.1 Identify Custom Extensions

3.7 Data Load Preparation

3.7.1 Perform Data Cleansing Activities

3.7.2 Download Templates for Data Loads

3.7.3 Define Specifications for Data Extraction on Legacy System

3.7.4 Develop Overall Load Plan