SAP Activate

Thursday, July 16, 2020 6:44 PM
Introduction to SAP Activate
SAP Activate Overview
SAP Activate Elements
Workstream Overview
Transition Paths
ACT10e_EN_Col12 Page 1
Exam
SAP Certified Associate Application Consultant - SAP Activate Project

Manager
Agile Delivery Approach

Workstreams Overview
Agile Project Planning
Fundamentals of SAP Activate Methodology >12%
New Implementation On-Premise >12%
New Implementation in the Cloud >12%
Agile Project Delivery 8% - 12%
SAP Activate Methodology content access 8% - 12%
Agile Project Planning 8% - 12%
System Conversion to SAP S/4HANA <8%
What is SAP Activate <8%
Components of SAP Activate <8%
Landscape Transformation to SAP S/4HANA <8%
General Certification Information
Solution: SAP Activate - Implementation & Administration
Level: Associate
Exam : 80 questions
Cut Score: 68%
Duration: 180 mins
Assessment ACT200
Agile Project Delivery

Welcome to the Assessment for the course Agile Project Delivery.
This assessment is designed to help you check your knowledge of the content
provided in the course.
We recommend you try the assessment before the training to check how relevant
the content of the course is for you and how much you already know about this
topic. Doing so will assist you in learning the content of the course more
effectively. You can also take this assessment after completing the training to
measure your level of understanding.
After each question you will receive feedback on whether your answer was correct
or not and where you can find further information on the correct answer.
This assessment covers the following units:
1. The Basics
2. Starting Agile
3. Backlog
4. Iterative Build
5. Summary of Key Points
6. Appendices
You can always leave the assessment and finish remaining questions at a later
time. Remember, you have to click 'Submit' to finalize your answer. Furthermore,
you can always repeat the whole assessment, however the last submitted score will
be stored as your result. The passing score of this assessment is 80%.You will not
get credits for completing this assessment.
Question 1
Choose the correct answer.
Which of the following statements about Scrum is correct?
In Scrum, as best practices, we have three main roles, and three artifacts or
three ceremonies.
In Scrum, the team is Self-organized, define all task necessary for all project
life cycle.
The three ceremonies are sprint planning, daily scrum, sprint review
(retrospective).
Scrum Master defines and prioritizes features and gathers requirements.
Question 2
Choose the correct answer(s).
In the context of Scrum, which of the following statements are
correct?
Incorrect! Product Backlog is a list of features prioritized by business value, the
items come from diverse sources, including the Scrum team. Sprint backlog is a
subset of product backlog loaded onto the Sprint’s “timebox”, it is the list of
work the team is addressing during the current sprint. Refer to the lesson ‘Agile
and Scrum 101–Understanding Scrum’ for more details.
Product Backlog is a list of features prioritized by business value, the items
come from diverse sources, including the Scrum team.
Sprint backlog is a subset of product backlog loaded onto the Sprint’s
“timebox”, it is the list of work the team is addressing during the current
sprint.
Burndown Chart Provides visibility into the product backlog, illustrate
progress by the team, work is in horizontal and time is in the vertical.
Scope and Goals of
Introduction to SAP Activate Page 9

Factors influencing SAP S/4 HANA implementation
Wednesday, July 22, 2020 11:40 AM
1. Concentration on Value-adding Processes

2. High Business Process Coverage
3. Agile Approach Adoption in Enterprise Environment
4. SAP S/4HANA Deployment Options
5. Project and Solution Management Automation
6. Purpose of SAP Activate Framework
7. Other SAP Frameworks

Concentration on Value-adding Processes
Customers, business partners and shareholders expect from the company:
• Efficient business process operations, which deliver repetitive and

reliable results (products)
• Introduction of new business models leveraging new IT technologies.
Efficient business process operations rely heavily on commodity

processes (repetitive tasks), which deliver repeatable and reliable results for
customers and business partners. New business models are emerging
from value-adding tasks which focus on improving customer, vendor, and
employee experience, and provide new business capabilities.
Since the 1960s, business applications' coverage of commodity processes
areas has increased significantly. This supplies companies with data and rule-
based processes, which provide real-time insights into operations. This also
creates a foundation for using such innovative concepts as Predictive
Analytics and IoT.
These innovative concepts, in turn, enable employees to perform value-
adding tasks, which were not possible before. With this shift, companies start
taking commodity processes for granted, which should support ongoing
company operations at optimal costs
Growing Market Maturity in Using Business Software
Over the years, market experience with implementing and operating business
solutions delivered two important outcomes:
• Low-value, must-have, and commodity processes should be automated
with lowest efforts and cost, so that company concentrate on implementing
more value-adding processes.
• Custom code is significant driver for Total Cost of Implementation (TCI)
and Total Cost of Operations (TCO) and should be managed to inevitable
minimum.
As a result, companies now expect that commodity processes will be automated
with ready-to-use (also known as Best Practice) configurations with very limited
custom code, which must be justified by profit or cost savings. At the same time,
all resources should must be concentrated on optimization and innovation of
value-adding processes to safeguard and develop competitive advantages.

High Business Process Coverage
SAP S/4HANA business scope is expanded to various business areas, such as:
• Sales and Marketing
• Supply Chain
• Manufacturing
• Procurement
• Research and Development
• Asset Management
• Services
• Finance
• Human Resource
• Cross Topics
• Industries
From <https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-
managed/Learning_Cards/ACT10e_EN_Col12/xml/a_40bc268140821f8bc4178e3bc_0/index.html >
SAP S/4HANA 1809 Industry Enablement*
SAP Country Versions for SAP S/4HANA

SAP Country Versions for SAP S/4HANA Public Cloud
From <https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-
managed/Learning_Cards/ACT10e_EN_Col12/xml/a_40bc268140821f8bc4178e3bc_0/index.html >

Agile Approach Adoption in Enterprise Environment

S

SAP S/4HANA Deployment Options
According to Gartner Magic Quadrant this is the full SaaS (Software as a Service) offering.

Project and Solution Management Automation
Solution Manager supports and Certified for ITIL processes:

• Availability Management
• Capacity Management
• Change Management
• Event Management
• Financial Management
• Incident Management
• IT Services Continuity Management
• Knowledge Management
• Problem Management
• Release and Deployment Management
• Request Fulfilment
• Service Asset and Configuration Management
• Service Catalog Management
• Service Level Management
• Service Portfolio Management.

Purpose of SAP Activate Framework
The SAP S/4HANA Implementation Framework that expedites for all deployment options of
SAP S/4HANA, using automation tools, ready-to-use content and ready-to-run systems to ensure
fast Time-to-Value and optimal TCI and TCO throughout full Application Lifecycle.

Other SAP Frameworks
Companies are turning to SAP to drive innovation and transform their

businesses in today’s data-driven, digital, and service-oriented economy. SAP
is doing its part to lead this transition by adopting a bimodal IT model in its
support of customers. SAP S/4HANA, as the preeminent system of record and
systems of innovation, such as SAP Leonardo, in combination with SAP Cloud
Platform, are mutually reinforcing; the whole is greater than the sum of the
parts. You can connect the entire enterprise with SAP S/4HANA, then tailor,
integrate, and expand the core with SAP Cloud Platform.
This bimodal IT approach, in which SAP S/4HANA core mission critical
applications are decoupled from line of business edge applications that are
developed on the SAP Cloud Platform, allows companies to innovate both the
core and the edge applications but each at their own pace. This decoupling
allows line of business applications to be deployed instantly based on the
constantly evolving requirements of the business unit while upgrades to the
core can be done quickly and effortlessly since it is not bogged down with
customizations and custom objects required to run the edge applications.
For example, if a Chief Marketing Officer (CMO) wishes to deploy a customer loyalty mobile
application to track customer behavior and better tailor marketing content and campaigns that
app could be quickly built on the SAP Cloud Platform, leveraging SAP Leonardo Machine
Learning perhaps, without the need to alter or touch any code in SAP S/4HANA. At the same
time because the SAP Cloud Platform natively supports SAP HANA the CMO can be assured
that the new loyalty app will integrate with his/her backend SAP S/4HANA Core. In addition,
when the time comes for a new SAP S/4HANA update or enhancement the IT department can be
confident that the new loyalty application will not be impacted because it is decoupled from the
core allowing them to complete the SAP S/4HANA update quickly and with less effort.

Explore SAP Activate Elements
Tools
Solution Manager
Content
Methodology
SAP Activate Elements Page 25

Tools

Process Automation
• Process Automation tools provide solution platforms for the execution of project-
related processes allowing the project team to create and manage project
related data in such tools.
• Major SAP Solutions, which provide Process Automation tools, are
○ SAP Solution Manager, and
○ SAP S/4HANA.
• SAP Solution Manager is the core Application Lifecycle Management solution
for SAP Solutions.
• Usage of Process Automation tools is defined within Project Management Plan
and dedicated strategies and standards (for example, Test Strategy, Training
Strategy, Custom Code Management Standard, Business Process Modeling
Standard, and so on) within Workstreams.

Content Provisioning tools provide access to content used by Project Team

for configuration and operations of solutions, conducting training, and so on. the
project team may not change or create project information in such tools.
Most of the Content Provisioning tools are online portals.
The most important tools in this category are:
• SAP Roadmap Viewer, and
• SAP Best Practices Explorer.
SAP Roadmap Viewer is the central location for SAP Activate Methodology. It
provides detailed information on project activities and Project Library
Accelerators.
SAP Best Practices Explorer is the central place for Solution Documentation.
It hosts information on Business Process flows and SAP S/4HANA configuration
guidelines.
There are numerous Content Provisioning online portals, which provide
advanced learning capabilities, for example, SAP’s Massive Open Online
Courses platform called openSAP.

Solution Manager
The components of Solution Manager are:

• Value Chains
• Processes

• Processes
• Integration Model
SAP Solution Manager 7.2 delivers four key value chains:

• Portfolio to Project
• Requirement to Deploy
• Detect to Correct
• Request to Fulfill
SAP Solution Manager supports ITIL processes and is certified for these processes.

Focused Build allows you to manage requirements and software development
for large, agile innovation projects.
With Focused Insights you can build and distribute powerful customer-specific
dashboards in minutes.
Focused Run is a powerful solution for Service Providers and larger customers
who want to manage all their systems in a central, scalable, and automated
environment:
• End User Monitoring based on single end user requests
• Integration monitoring on single message level and End-to-End correlation
• System anomaly analysis and metric forecasting

Who is a user?
Licensing is based on named users per year
Only users who actually work with the solution need to be licensed.
• Users in Focused Build are all active project members. Tester is not
counted as active users (Details)
• Users in Focused Insights are all viewers of the dashboards. (Details)
Named users who execute functions of focused solutions are counted with the
standard license auditing processes of SAP.
ALM Processes and tools shall be implemented as part of Project Infrastructure before the
Explore phase to ensure efficient project operations.

Content
Business Process content for SAP S/4HANA is combined from Solution

Documentation and Solution Configuration:
Documentation and Solution Configuration:
• Solution Documentation is provided through SAP Best Practices Explorer
online tool. It delivers:
○ Process descriptions and flows
○ Configuration guidance, and so on.
• Solution Configuration is a function of the SAP S/4HANA system which
contain system objects. These objects are deployed when Solution
Package is activated.
To explore SAP S/4HANA Cloud customers and partners can use the SAP
S/4HANA Cloud Trial web site.
• For On Premise deployments SAP provides Ready-to-run systems on the
following media:
○ On Blu-ray Disks, and
○ Through SAP Cloud Appliance Library
• There are two types of Ready-to-run systems:
○ Fully Activated Appliance: a pre-packaged software bundle that
contains an SAP S/4HANA system with pre-configured SAP Best
Practices and demo scenarios
○ Model Company: part of Consulting Service, a pre-configured ready-
to-run reference solution with business content, accelerators, and
Engineered Services for multiple industries or lines of business

For the user interface of SAP business process content:
• SAP provides several Content Provisioning tools which provide access to
galleries of ready-to-use applications based on SAP Fiori and Screen
Personas.
• Developers may copy published application and change them to meet
business requirements.
• SAP Build provides advanced features for creating clickable prototypes and
user collaboration for feedback collection.

Structure of Data Migration Content:
• Data Migration Content for SAP S/4HANA is available in the format of:
○ Data Migration Templates: Available within Migration Cockpit for
SAP S/4HANA On-Premise and Cloud editions
• Best Practice Rapid Data Migration to SAP S/4HANA provides:
○ In Software Downloads Center:
▪ Data Services 4.2 content
▪ Alternative files containing the definition of Data Stores, Migration
Project and Jobs, Web reports, Migration Service, and so on
• In SAP Best Practices Explorer:
○ Solution Documentation for Rapid Data Migration to SAP S/4HANA
(On-Premise)
• In SAP Support Launchpad:
○ SAP Note on installing content from SAP Software Downloads Center

Methodology
Methodology: Phases
Phase: A synchronized collection of deliverables which require formal
acceptance by project governance bodies. Projects go through phases
sequentially:
• The company should discover business benefits it will gain through the
project
• The project team should be assembled and prepared to undertake the
project
• The functionality of the SAP solution should be explored by the project
team to identify gaps
• Required changes in systems, data and organization should be
implemented or realized
• All changes should be deployed, switching the organization to new or up-
dated business processes based on new or modified systems
• Support and optimization of deployed changes is necessary to ensure
smooth running of new or updated business processes.
There are number of contracting strategies and Partner-Customer collaboration

models for SAP implementation projects. Here is an example of a simplified
model:
• In the Discover phase, the customer works on developing
requirements towards future implementation partner in all aspects of the
future project

future project
• In the Prepare phase, when the contract with the implementation
partner is signed , the project team begins preparing for efficient
collaboration within the project based on Customer requirements
developed in Discover phase. Based on Customer requirements developed
in Discover phase, the project team develops Strategies (approaches)
Level 1.
• There is additional information on contracting strategies in the Appendix
The core of the project delivery happens between the Prepare and the Deploy
phase. Let's review the work that happens in each phase:
• In the Prepare phase, we define project governance, start the project,
define/identify the resources, define the roles and responsibilities for the

define/identify the resources, define the roles and responsibilities for the
project team, and detail the management plans for running the project.
• In the Explore phase, we run the Fit/Gap analysis on the working system
with the best practices content up and running. The objective of the Explore
phase is to identify the fit of the best practices based solution, capture delta
configuration requirements, identify gaps, and configuration values. All
these are captured by the project team in the backlog and later, in Realize
phase the backlog items are implemented in the system. The best practices
content is used as a jump-start for the project.
• During the Realize phase the project team will use agile approach to
iteratively and incrementally build the functionality from the backlog. This
build follows the prioritization given by the product owner (e.g. the business
users) that continue to be involved with the project team during the sprints.
• During the build the team completes the remaining configuration and
development on top of the best practices content. Additionally, the team
performs the unit and string testing during the sprints. In the Realize phase
the team also works on the integration of the overall solution to meet
customer needs.
• The Realize phase covers all the build and test activities required to
prepare a release of functionality into production. This includes a full
Integration test and user acceptance test before the team can continue into
the Deploy phase.
• The objective of the Deploy phase is to launch the production environment
and confirm readiness to switch into business operations with the new
solution. The team also performs sustainment and hyper-care activities in
the Deploy phase once the system goes live.
• Once the customer has switched over into the new environment, the project
team supports the customer IT and business. The team stay on-site for a
pre-determined period of time, which is usually defined in the contract or
agreed as part of the plan to transition to operations.
The Run phase then represents key steps in running and improving the
operations of the environment. This includes end user support, system
monitoring and other activities including continuous improvements to the
solution.
SAP Activate and Project Management Methodologies
Note
SAP Activate expands Product-oriented Processes group mentioned in
PMI and re-uses PMBoK guidance in the Project Management Workstream
Project Management Processes:
• Project Integration Management
• Project Scope Management
• Project Time Management
• Project Cost Management
• Project Quality Management
• Project Resource Management
• Project Communication Management
• Project Risk Management
• Project Procurement Management
• Project Stakeholder Management
Product-oriented Processes
Term introduced by Project Management Institute Inc., Project Management
Institute, Inc. A Guide to the Project Management Body of Knowledge PMBOK

Institute, Inc. A Guide to the Project Management Body of Knowledge PMBOK
Guide. Fifth edition. 2013.
• Customer Team Enablement
• Application Design & Configurationthroughout the course Application
Design & Configuration might be shortened to Design & Configuration
• Solution Adoption
• Testing
• Integration
• Extensibility
• Data Management
• Technical Architecture and Infrastructure
• Operations and Support
A Workstream is a grouping attribute for Activities, Roles, Deliverables
and Artifacts. Workstreams include:
• Project Management: All project activities should be executed efficiently.
• Customer Team Enablement: Project teams should possess all
knowledge and skills to efficiently work within project.
• Solution Adoption: The people and organization should be ready to use
new system.
• Design and Configuration: Application configuration should be done
efficiently.
• Extensibility: Development of system extensions should be done
efficiently.
• Data Management: Data from Legacy Systems should be transferred to
new system without losses.
• Integration: New systems should be properly integrated into company’ IT
landscapes.
• Testing: Everything should be tested to ensure robust operations.
• Analytics: The best (transparent, cost effective, scalable, and so on)
analytics option should be implemented.
• Technical Architecture and Infrastructure: IT systems should be
installed and configured.
• Operations and Support: Customer IT and Business organizations should
be ready to efficiently support new system and business processes after
Go-Live.

Workstream states are as follows:

Planning:
Preliminary strategy and tools selection
Preparation:
Setup tools, establish frameworks
Execution:
Create results, deliverables, and artifacts
Operations Preparation:
Tools, procedures, roles for operations
Deliverable:
Measurable result of the project team work showing project progress.
Deliverable can be tangible or intangible. Deliverables may, or may not
require formal approval from stakeholders. Deliverables may be assigned
to one or more Workstreams.
Task:
Work to be performed by a project team to create one or more deliverables.
Project Plan:
Structured collection of tasks with dependencies, used to plan and monitor
project team work.

Deliverable:
Measurable result of the project team work showing project progress.
Deliverable can be tangible or intangible. Deliverables may, or may not
require formal approval from stakeholders. Deliverables may be assigned
to one or more Workstreams.
Task:
Work to be performed by a project team to create one or more deliverables.
Project Plan:
Structured collection of tasks with dependencies, used to plan and monitor
project team work.

Artifacts: Information Assets
Examples of Artifacts:
Note
Project team is consuming and producing information (Information
Assets). Information is used for managing project activities and shows
project progress (Results). All forms of information used or generated by
project team are considered altogether as Artifacts.
• Paper documents
• Scrum artifacts (information radiators)
• Solution Manager objects
• Third party or custom ALM and project management software objects or
documents
• Third party BPM software objects
• Document management system software objects
• Word processors' documents, electronic tables, spreadsheets,
presentations, and so on.
Information Assets:
• Represent information (text, graphics, documents, system changes, and so
on)
• Are managed on media (digital or paper)
• Can be approved
• Generate obligations
• Contain Evidence
• Provide tracking or audit capabilities

Substances Changed by the Project

SAP Activate Methodology - Methodology Elements
Dependencies


Topics
Introducing the Project Management Workstream

Introducing the Design and Configuration Workstream
Introducing the Analytics Workstream
Introducing the Customer Team Enablement Workstream
Introducing the Solution Adoption Workstream
Introducing the Extensibility Workstream
Introducing the Testing Workstream
Introducing the Integration Workstream
Introducing the Operations and Support Workstream
Introducing the Data Management Workstream
Introducing the Technical Architecture and Infrastructure Workstream
Workstream Overview Page 52

Introducing the Project Management Workstream
• Scrum in SAP Activate Methodology

• Project Governance
• Cutover
• Scrum Teams Resource Planning
• Risk Management – Major Risks
• Tools in Project Management
• Roadmap Viewer
• Jam
• Project Management with SAP Solution Manager
• Cloud Implementation Portal
• Accelerators
• Artifacts Flow

Introducing the Design and Configuration Workstream

Introducing the Analytics Workstream

Introducing the Customer Team Enablement Workstream

Introducing the Solution Adoption Workstream

Introducing the Extensibility Workstream

Introducing the Testing Workstream

Introducing the Integration Workstream

Introducing the Operations and Support Workstream

Introducing the Data Management Workstream

Introducing the Technical Architecture and Infrastructure
Workstream

Transition Paths
• Understanding New Implementation S/4HANA Cloud Multi-Tenant Edition

• Understanding New Implementation S/4HANA On Premise
• Understanding New Implementation S/4HANA Cloud Single-Tenant Edition
• Understanding System Conversion
• Understanding Selective Data Transition
Transition Paths Page 64

• In the SAP S/4HANA Cloud Multi-Tenant Edition landscape, a Starter System contains
configuration and master data for targeted enablement of the Project team on SAP standard
processes and is used as the host environment for the Fit-to-Standard workshops.
• SAP Solution Manager is the default ALM solution for SAP S/4HANA On-Premise
implementation scenarios. If it is used in the project then artifact "Solution Manager Design
Document" shall be developed during Prepare phase.



For solutions with limited in-App extensibility Solution Validation (Workshop A) is named Fit-
to-Standard Workshop and Delta Design (Workshop B) is called Solution Definition.

Agile and Scrum 101
The Basics Page 69

The Basics Page 70

SAP Activate

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

SAP Activate

Uploaded by

Copyright:

Available Formats

Thursday, July 16, 2020 6:44 PM

Introduction to SAP Activate

SAP Activate Overview

SAP Activate Elements

SAP Certified Associate Application Consultant - SAP Activate Project

Agile Delivery Approach

General Certification Information

Solution: SAP Activate - Implementation & Administration

Cut Score: 68%

Duration: 180 mins

Agile Project Delivery

Introduction to SAP Activate Page 9

1. Concentration on Value-adding Processes

Introduction to SAP Activate Page 11

Customers, business partners and shareholders expect from the company:

• Efficient business process operations, which deliver repetitive and

Efficient business process operations rely heavily on commodity

Introduction to SAP Activate Page 12

SAP Country Versions for SAP S/4HANA

Introduction to SAP Activate Page 13

Introduction to SAP Activate Page 14

Agile Approach Adoption in Enterprise Environment

Introduction to SAP Activate Page 15

Introduction to SAP Activate Page 16

Solution Manager supports and Certified for ITIL processes:

Introduction to SAP Activate Page 20

Introduction to SAP Activate Page 22

Companies are turning to SAP to drive innovation and transform their

Introduction to SAP Activate Page 23

SAP Activate Elements Page 25

SAP Activate Elements Page 26

SAP Activate Elements Page 27

Content Provisioning tools provide access to content used by Project Team

SAP Activate Elements Page 28

The components of Solution Manager are:

SAP Activate Elements Page 29

SAP Solution Manager 7.2 delivers four key value chains:

SAP Activate Elements Page 30

SAP Activate Elements Page 34

SAP Activate Elements Page 35

Business Process content for SAP S/4HANA is combined from Solution

SAP Activate Elements Page 38

SAP Activate Elements Page 39

SAP Activate Elements Page 40

There are number of contracting strategies and Partner-Customer collaboration

SAP Activate Elements Page 42

SAP Activate Elements Page 43

SAP Activate Elements Page 44

SAP Activate Elements Page 45

Workstream states are as follows:

SAP Activate Elements Page 46

SAP Activate Elements Page 47

SAP Activate Elements Page 48

SAP Activate Elements Page 49

SAP Activate Elements Page 50

SAP Activate Elements Page 51

Introducing the Project Management Workstream

Workstream Overview Page 52

• Scrum in SAP Activate Methodology

Workstream Overview Page 53

Workstream Overview Page 54

Workstream Overview Page 55

Workstream Overview Page 56