Describing SAP Activate

Purpose of SAP Activate and the Implementation Approach

SAP Activate is an implementation methodology that is adaptable to a wide range of

project sizes and complexities. It provides excellent guidance to all project streams like
Architecture, Project Management, or Integration through its self-service capabilities,
supporting customers, partners, and consultants to drive business initiatives in the
digital age.

By leveraging the pre-delivered content, customers can jump-start the build using pre-
built solutions as well as engineered services. With that, the SAP Activate framework
provides a significant reduction in project time, reducing the Total Cost of
Implementation (TCI) and Total Cost of Ownership (TCO).

Changed Business Expectations

In this lesson, we will discuss the origin of SAP Activate and the changes that it has
brought about, in the way projects are delivered.

he various advantages that apply to cloud solutions will be highlighted in the following.

SAP Activate is a transformative shift into a newer, more modern, and smarter
implementation approach when compared to the traditional approach to software
deployments. This book details all the capabilities and services through Best Practices,
accelerators, and tools which support this model. The diagram above offers a high-level
comparison between the old and the new.

The purpose of the SAP Activate framework is to expedite and/or fast track any and/or all
deployment options for all SAP products. This is achieved using automated testing
tools, ready-to-run systems, and ready-to use content (available in the SAP Activate
Roadmap Viewer).

This ultimately leads to a lower Total Cost of Implementation:

 1. As documentation effort is significantly reduced using accelerators.

2. As configuration time is significantly reduced using pre-build solutions.

In addition to the reduction to the cost of implementation, SAP provides Application

Life-Cycle management tools for the management of operations activities post go-live,
effectively minimizing the costs of running your solution (that is, Reducing the Total Cost
of Ownership – TCO).

SAP Activate Content

The SAP Activate Content includes accelerators in the form of documentation

templates available to be used in each project phase, as well as pre-configured 'in-
system' business processes, making the systems virtually ready-to-run after activation.

In addition to the accelerators, the SAP Activate framework provides system guidance in
the form of configuration documents, data migration guidance, integration guidance,
presentation materials, and video tutorials to support implementation teams with their
project deployments.

All tools and content allow for an accelerated, guided, and expected outcome. This
fosters customer, partner, and consultant enablement, while significantly lowering
implementation risk.

• SAP Best Practices provide projects with a baseline configuration.

• Ready-to-run systems provide projects with a prototype.

• Project accelerators which include project plans, document templates, and

references to SAP information resources, provide project managers with the
foundations for a project library.

• For integration and migration areas, SAP provides system content and guidance.
Identify the SAP Activate Framework Variants

SAP Activate is a product agnostic framework which caters for all SAP deployment
options and products, whether cloud, on-premise, or private cloud. The framework is
seamlessly adapted to suit any deployment model or product in SAP’s entire portfolio.
In addition, SAP has provided several roadmaps for each deployment type.

In addition to this course material, there are several other information sources where
content on SAP Activate can be found.

They are as follows:

1. SAP Activate Community, refer to the following

link: https://community.sap.com/topics/activate
 2. The SAP Activate Roadmap Viewer, refer to the following link:

https://go.support.sap.com/roadmapviewer/

3. SAP Learning Hub, refer to the following link:

https://learninghub.sap.com/

→ E.g. Search for Course ACT 200.

Describing the 3 Pillars of SAP Activate
The Three SAP Activate Pillars

The SAP Best Practices

SAP Best Practices helps project teams accelerate time to value. They provide content
that helps jump start the implementation with ready-to-run processes and other assets.

The Best Practices contain rich business scenarios and business content. This helps
customers get predictable and repeatable results from the Best Practices. The Best
Practices and some prototyping, for example, personalization, additional configuration,
or enhancements of the pre-delivered content, can be used as a baseline for an
implementation project.

Best Practices can be deployed in the cloud, which further improves flexibility and time
to value.

SAP Best Practices are available in two distinct formats:

 1. Documentation:

The documented format of the SAP Best Practices can be found on the SAP Signavio
Process Navigator, https://me.sap.com/processnavigator/HomePage. From this
platform, best practices content is available for review, download, and use with your
projects.

2. Configuration:

The configuration format of the best practices is found directly inside of the system.
These best practices are preconfigured business processes which lay dormant inside of
the system. Once activated these Best Practice processes are now 'ready to run'.
Configuration best practices allow the user to execute the process inside the system.

The Deployment Tools and Structure

The SAP Signavio Process Navigator provides package content specific to the scope of
your solution. It includes all business process scope in documentation format for all
business processes inside the application.

The following information can be found in SAP Signavio Process Navigator:

• Scope item fact sheets: A description of the business process including

business benefits and key process steps covered.

• Process flow: A representation of the standard business process to show how

the software works by default.

• Process flow (BPMN2): A downloadable version of the business process flow that
can be edited in process modeling applications if the standard process flow is
customized. It's important to document any process that no longer follows the
standard process.
 • Test scripts: A procedure for testing the standard Best Practice processes in the
system.

• Set-up instructions: A guide with instructions to set up the prerequisite

requirements (usually an integration) before the test script can be completed.

You can reduce the cost of operations by using the pre-delivered processes, and use the
country-specific content to manage multiple geographies, divisions, subsidiaries, and
ledgers. Best Practice content is updated on the Release to Customer (RTC) date for
your selected solution with the latest enhancements and new features.

The following additional content can be found on the SAP Signavio Process Navigator.

• SAP Signavio Process Navigator Solution Package: contains descriptions and

corresponding content.

• Guidance: helps select best approach, for example, in Analytics or Integration.

• Solution Description: provides high-level structure and description, such as

Partner Solutions.

For cloud solutions tool: SAP S/4HANA Cloud Release Assessment and Scope
Dependency helps to find inter-dependencies between scope items for upgrade
planning.
The diagram above displays the naming structure of the best practices documentation
in the SAP Signavio Process Navigator.

When accessing the SAP Signavio Process Navigator, logging in with an S-User ID is
required to display all of the available content. When browsing via public access, you
will be prompted with a log in screen for the user to log in.
SAP configuration Best Practices is an accelerator, as the standard processes are
already configured, and once activated, make the system 'ready to run'. But Best
Practices may not always provide coverage for every customer around the world. In any
case, should the Best Practice provide good coverage for the business, then creating a
Best Practice client and activating the Best Practice processes is the preferred
approach. When the Best Practices do not provide coverage for the business, the
traditional approach is applied, which entails configuring the system from the beginning
without leveraging the Best Practices.

The configuration Best Practices can be found in the Solution Builder transaction using
transaction code /n/SMB/BBI inside of the SAP S/4HANA system.
From the Solution Builder, all available Solution Packages can be searched for by
country, language, and version. Once found using the Implementation assistant all
project / customer scope, Best Practice can be activated.

The task is performed by the SAP Basis consultant when doing an on-premise
implementation, and is a service performed by SAP when doing a Cloud or Private
Cloud deployment.

The above diagram displays a comparison of the different Best Practices terminologies
between the SAP Signavio Process Navigator, the Solution Builder, and SAP Cloud ALM
using the example of S/4HANA.
Configuration in the public cloud solution is performed via Self-Service Configuration UI
(SSCUI) and the Configuration system.

SAP Central Business Configuration is a tool designed to configure business processes

from one central place. It facilitates leveraging Solution Builder's Best Practice content.
Leading to increased business process flexibility and reduced configuration efforts.

Configuration for on-premise solutions as well as private cloud is performed via the
traditional Implementation Guide (IMG) in Transaction SPRO.

SAP Central Business Configuration is designed to provide guidance for your

implementation project by controlling the completed activities sequence. In the Project
Experience, you can manage your team members, complete activities to set up and
configure your systems, and view the project status. Activities are grouped into phases,
and each phase ends with a milestone.
The configuration activities in SAP Central Business Configuration are designed to
support customers in adapting the preconfigured SAP Best Practices content to their
requirements. The available configuration activities are based on the active scope and
country selections. Configuration activities may vary by country because not all
business scenarios (scope items) are available in all countries. Configuration activities
can be mandatory, recommended, or optional.

The Project Management tasks from SAP Central Business Configuration can also be
transferred to SAP Cloud ALM for Implementation. Then the status can be tracked
centrally in SAP Cloud ALM for Implementation together with all project tasks,
requirements, user stories, testing activities and defects.

All configuration for on-premise and private cloud is performed via the IMG in
transaction SPRO. By starting your build with the activated Best Practices, consultants
only need to perform delta configuration to configure the additional functions or
features requested by the business during the Explore phase workshops.

The SAP Activate Methodology and Benefits

The third component/pillar of the SAP Activate framework is the SAP Activate
Methodology.

The SAP Activate Methodology provides one simple, modular, and agile methodology,
and is the successor of ASAP and SAP Launch methodologies.

SAP Activate Methodology provides full support for initial deployment and continuous
business innovation with a harmonized implementation approach for cloud, on-
premise, and hybrid deployments.

SAP Activate Methodology is designed to support all SAP solutions.

The methodology also enables co-innovation with customers, and is accessible for
partners.

The methodology uses, as default, agile project delivery principles. It builds on the
ready-to-run business processes and the SAP Best Practices documentation. It uses
the configuration tools to adjust the baseline solution to customer needs based on the
results of the fit-standard workshops, which is conducted in the Explore phase.

The SAP Activate Methodology provides project teams with structured approaches to
implement the solution and the solution and product specific content for
implementation or transition to SAP S/4HANA and other SAP products.

The SAP ecosystem is familiar with the ASAP methodology. there are some differences
between SAP Activate and ASAP that you should be aware of for an on-premise
implementation:

In SAP Activate Methodology, we are leveraging the SAP Best Practices as a default way
to build the baseline system for fit-to-standard.

There are four core project phases in SAP Activate that we do not have separate phases
for the final preparation and go-live support, but instead execute them in one phase
called 'DEPLOY'.

In the SAP community page, you can learn about SAP Activate, which describes the
deliverables per phase. This helps those accessing the SAP Activate materials to review
content and to understand the key goals of a phase.
The blueprint activities that were represented in ASAP, have been replaced with fit-to-
standard analysis workshops. The project team uses the SAP Best Practices based
system to validate the customer's requirement against a working baseline solution.
Then, the team captures the delta requirements and/or user stories in the backlog. This
information is then used for implementation of requirements during the Realize phase.

SAP Activate Methodology supports not only the on-premise deployment, but also
cloud deployment, with one consistent approach. SAP Activate brings together the
approach for on-premise and cloud. It harmonizes the approach across these different
deployment models which also helps to support hybrid deployment projects.

SAP Activate supports not only SAP S/4HANA, but also other solutions like SAP
SuccessFactors, SAP Sales Cloud, SAP Service Cloud and SAP Ariba. SAP offers
content for these solutions in the SAP Activate Methodology, which can be found in the
SAP Activate Roadmap Viewer.

The SAP Activate Methodology six phase descriptions will vary slightly for each
implementation scenario (for example, SAP Activate Methodology for SAP Cloud for
Sustainable Enterprises) but will have the same phase name. In the example in the
figure SAP Activate Methodology for RISE with SAP S/4HANA Cloud, private edition will
have the following high-level phase descriptions:

Discover phase

In the Discover phase customer’s core team is enabled to understand breadth, depth,
and functionality of RISE with SAP S/4HANA Cloud, private edition. The team would
learn the benefits and value the solution can bring to customers’ business.

Prepare phase

The Prepare phase is where the project is jump-started. The project environment gets
set up, the project manager needs to set up the project governance, clarifying the
project team roles and responsibilities, and provide the team with project standards.
Project is kicked off and the team starts answering the Business-Driven Configuration
questionnaire. Towards the end of this phase the team will be setting up the initial
system for fit-to-standard workshops.
Note

In today's fast-paced and ever-changing business environment, disruption across

global supply chains, customer preferences, and the workforce has become a common
occurrence. Businesses must quickly adapt to these changing requirements in order to
remain relevant and thrive. To succeed in the digital age, organizations need to embrace
new capabilities. This includes accelerating innovation, optimizing and automating
processes, and fostering agility in order to gain a competitive edge. Companies must
have a flexible infrastructure that allows them to quickly adapt their business models as
needed. This means being able to rapidly adjust key applications to meet changing
market demands and customer needs.

Clean core is a mind set and philosophy supported with governance and guidelines that
lays a foundation for flexible future proof solution.

It describes a modern approach to extend functionality in a stable, upgrade safe and

transparent manner. Along with separate platform to innovate for additional
differentiation. A clean core allows faster software deployment as well as easier
adoption of both. SAP innovations and the regulatory changes to software. It provides
new ways to address business needs while avoiding excess technical debt, thus
preparing organizations to maximize strategic benefits and limit cost of transformation.
You’ll learn more about the clean core and how it is embedded into the implementation
methodology in Unit 3 Lesson 1.

Explore phase

In this Explore phase the project team will conduct fit-to-standard workshops, verify,
and confirm the to-be business processes with process models. Meanwhile master
data and organizational requirements get identified. Organizational learning needs are
identified and documented. After sign-off on delta requirements, design documents,
and implementation plan the Q-gate from Explore to realize gets closed.

Realize phase

Project management joint with workstreams will plan sprints. Project team focuses on
implementing defined solution using incremental build iterations. It will configure,
extend, integrate, test, confirm, and document the entire end-to-end solution and
prepare for legacy data conversion. The project team actively works with business
representatives to ensure a good fit of the built solution to the requirements from the
backlog.

The team executes build cycles called ‘Sprints’ to build and test the functionality. The
team will conduct walkthroughs with the business users within each sprint to provide
frequent checkpoints that the build is meeting the requirements. And will go through
multiple iterations to develop functionality that is then ready to be released to
production. For each release, the team conducts full end-to-end testing. The project
team releases results of multiple iterations to the business users to accelerate time to
value and provide early access to finalized functionality. Each sprint release is
thoroughly tested in the end-to-end integration test and the user acceptance test.

The Realize phase is completed with the Realize-to-Deploy Q-Gate

Deploy phase

In the Deploy phase, the team makes sure that the business is ready to perform the
cutover activities. The complexity of these activities will depend on various factors
including the number of users that are impacted by the solution and the business scope
of the deployment. Teams may need to conduct multiple cutover simulations as part of
the preparation for go-live. Once the solution is live, the project team provides a defined
period of post go-live support (sometimes called the hyper-care period). The project is
then formally closed, and the solution is now in a separate PRODUCTIVE OPERATIONS
or RUN phase

Run phase

Customer is live, with this begins the continuous learning process, that includes
validation of newly released features and value assessment of business relevant
innovations against current solution.

Behind this high-level phase descriptions, SAP Activate Methodology provides helpful
details for deliverables and tasks as well as more sources to relevant information.

Summary of the Benefits of the SAP Activate Methodology

• Enables consistent project delivery, reduces complexity and increases quality by

providing common framework and language for all SAP projects.

• Broad product knowledge, including support for all transition scenarios for SAP
S/4HANA, SAP S/4HANA Cloud, and all other applicable solutions.

• Scalable, supports all sizes of projects, from small fast cloud deployments to
comprehensive global deployments in on-premise or hybrid environments.

• Prescriptive and comprehensive – provides guided work for phases, deliverables,

tasks, and accelerators.

• Accelerates project delivery through the use of SAP Best Practices, fit-to-
standard analysis, agile project management, application visualization, and use
of cloud technology.

• Methodology foundation fully aligned with proven project management practices

such as the Project Management Institute, like formal quality, risk, and issues
management.
Outlining SAP Activate Methodology Foundation
Describing the Methodology Structure

Methodology Structure

Methodology Breakdown

The figure, SAP Activate Phases, outlines the phases of SAP Activate Methodology.

The core of the project delivery happens between the Prepare and the Deploy phases. These are
referred to as the four core phases.

Discover and Run are additional phases that are described in more detail later.

In the Prepare phase, we define the scope of work, project governance, prepare the sandbox /
starters systems, start the project, identify and define the resources, define the roles and
responsibilities for the project team, and detail the management plans for running the project
among other activities.

In the Explore phase, we run the fit-to-standard workshops using the SAP Best Practice content
and demonstrate standard processes using the sandbox or starter systems. The objective of the
Explore phase is to identify the fit of the Best Practices-based solution to the business, capture
delta configuration requirements, and identify gaps and configuration values. All these are
captured by the project team in the product backlog.

During the Realize phase, the project team adopts an agile approach to iteratively and
incrementally build the functionality from the backlog. This build follows the prioritization given
by the product owner (for example, the business users) that continue to be involved with the
project team during the sprints. During the build, the team adds the configuration and
development on top of the Best Practices content (Deltas). Additionally, the team performs unit
and (at times) 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 set up the production environment and confirm
readiness to switch into business operations with the new solution. The team also performs
sustainment and hypercare activities in the Deploy phase once the system goes live.

Once the customer has switched over into the new environment, the project team helps the
customer's IT and Business departments to adopt and use the functionality. The team stays on-
site for a predetermined period of time, which is usually defined in the contract or agreed as
part of the plan to transition to operations.

The figure, Additional Phases, shows two additional phases of SAP Activate.

The Discover phase is a non-committal phase where customers can discover and research all
offerings available within the SAP portfolio, and determine which innovations are most
applicable and suitable for their organization. SAP provides several discovery resources to
existing and prospective customers, ranging from white papers and presentations, to trial
systems and games.

Discover phase deliverables include:

Overall Innovation Strategy and Roadmap Creation:

In the first deliverable, customers create an overall company strategy for their digital
transformation. This may include SAP S/4HANA as the digital core, but contains a broader
perspective. Key topics like Internet of things, Big Data, Smart Data, Omni-channel, or Business
Networks can also be captured in the strategy.

Value and Impact Analysis:

Customers should become more familiar with the value of other SAP products in general (that
is, the new and simplified functionality in e.g. SAP S/4HANA, the new User Interface based on
SAP FIORI, agile customer innovations using SAP BTP, and so on). A trial system in the Cloud can
further support this.
Implementation Strategy:

A decision on the implementation scenario and comprehensive implementation strategy for any
SAP Product implementation will be created.

In case of system conversion, the conversion readiness of the existing SAP ERP system will also
be checked.

A learning needs analysis for the project team is important as this can impact other activities in
the program. E.g. the completion of learning should be finalized prior to participating in project
workshops.

Technical Architecture and Infrastructure:

The Technical Architecture and Infrastructure requirements should be clarified to support the
innovation strategy and the proposed implementation.

The Run phase

Run is referred to as a phase in Activate but has a methodology of its own. Run is effectively the
support or management of the productive solution post go-live.

SAP has several standards for running a solution optimally, which range from incident and
change management, system and application monitoring, to upgrade management. There are
16 standards in total.

There are also different models that can be applied when running or supporting SAP solutions,
some which are the setting up a Customer Center of Expertise (CCoE) or run SAP like a factory
or premium engagement. Each of these are models and approaches related to the maintaining
and supporting of the SAP solution once live, and tailored to customer size and needs.
Additional information can be found on the SAP support portal.

https://support.sap.com

Workstream Description
Across the following three diagrams, we detail the SAP Activate Methodology workstreams and
their related descriptions. Those familiar with ASAP and SAP Launch should review the
workstream descriptions as they have changed significantly from the previous roadmaps.

The workstreams are optimized and aligned with various implementation scenarios. They are
also adjusted based on feedback from initial projects that used SAP Activate Methodology
content.

The first workstream is Project Management, which covers all the aspects of setting up the
project, running it, and delivering on the project objectives. The Project Management
workstream is structured around the fundamentals of agile project delivery, and is aligned with
Project Management Institute standard, the PM Body of Knowledge (PMBOK).

There are a set of Application workstreams that deal with different aspects of the application
itself. These include design, configuration, testing, and integration. These workstreams cover
the core of the work done on the solution to adjust it to fit customer needs. This includes the
design and configuration activities, such as running the fit-to-standard workshops or
configuring the system. It also covers the development of extensions, testing including
integration, performance, system tests, regression testing, as well as User Acceptance Testing
(UAT).

The Solution Adoption workstream deals with what was previously covered in the Organizational
Change Management (OCM) stream and training stream in ASAP. The adoption activities enable
the organization and end users to use the solution in their daily work. The deliverables and tasks
guide the project team in ensuring a smooth transition to operations, post go-live support, and
change management.

The Analytics workstream covers the analytics aspects of an SAP implementation project.
Extensibility

The Extensibility workstream addresses all custom modifications to the solution from
specification to custom development. Developers / Programmers fall within, and deliver custom
programming activities in this workstream.

Data Management

All Data Management activities within a project are covered under the Data Management
workstream.

Technical Architecture and Infrastructure

This workstream address all activities required for the technical end of the application. From
operating systems, databases, installation, upgrades, and maintenance, all these activities fall
within and are covered by the technical team 'Basis' in this workstream.

Operations and Support

Under this workstream, all deliverables relating to the support of the solution, upgrade,
incident, and change management when the solution is live, are covered.

Analyzing each phase of SAP Activate

Details by Phase

The above diagram displays a high-level view of some of the core activities performed across
each phase of SAP Activate.

We are going to look at the following:

• SAP Activate Phases detailed activities

• SAP Activate Prepare Phase approach

• SAP Activate Explore Phase approach

• SAP Activate Realize Phase approach

• SAP Activate Deploy Phase activities

This slide provides a description of the Prepare phase along with related key activities to be
performed.
This figure shows some examples of accelerators that are available for use when delivering a
project using SAP Activate. Accelerators are documents, templates, or links to tools and other
assets that can help a project team complete their work faster by providing clear guidance or a
starting point for producing an outcome like a deliverable.

In the Prepare phase, we have different accelerators:

• Delivery supplement

• Solution scope document

• Software and delivery requirements for the Best Practices Work Breakdown Structure

• Project management plans and governance documents

This slide provides a description of the Explore phase along with related key activities to be
performed.

This diagram provides a description of the purpose of the fit-to-standard process.

The above diagram details in six steps, how to approach the fit-to-standard workshops.
These are the intended outputs of the fit-to-standard workshops.

Following are the principles to be applied in the fit-to-standard workshops:

• Fit-to-standard: Adopting a Fit-to-standard approach and SAP standard functionality,

will minimize delivery risk and ultimately lower the total cost of the implementation and
operation.

• Value Justification: SAP applications are built on industry best practices and any
proposed customizations should be motivated against business value.

• Show and Tell: Leading design activities through showing rather than telling, contributes
significantly to business adoption, enablement and acceptance

• Active Participation: Active participation by the business users in the design and
acceptance activities fosters collaboration and is key to delivering a successful
solution.

• Focus on simplicity: When designing the solution, focus on simplicity and ease of use
while minimizing unnecessary complex functionality as far as possible.
 • Design Acceptance: Applying these principles in Fit-to-Standard workshops facilitates
adoption and leads to design acceptance by the business.

The following seven high-level activities are performed during the fit-to-standard workshops.

1. Set Reference Value:

Agree fit-to-standard guiding principles.

Prepare organizational structure, master data, and process diagrams. Bind processes to value
drivers.

2. Validation of SAP Solution:

Show and tell SAP standard key design elements.

3. Collect Delta Requirements:

Identify gaps to SAP standard.

Log or create additional scope items.

4. Create Initial Backlog:

Set priorities and efforts estimates. Identify dependencies.

Plan sprints for the Explore phase.

5. Enhance Solution Documentation:

Update process diagrams and process design. Visualize UX.

6. Verify and Accept:

Verify process and solution documentation. Drive acceptance.

7. Plan Sprints and Releases

A major consideration before executing the fit-to-standard workshops is to enable business
users on key topics that will be covered in the workshops. These include enablement on master
data concepts, SAP terminology, workshops' approach, and the SAP Activate Methodology,
among other activities.

Enablement sessions should be aligned to project scope to better prepare the business
audience for active participation in the workshops.
Here is an example of an accelerator on how to run your fit-to-standard workshops, which is
available for download from the SAP Activate Roadmap Viewer and for use in your projects.

There are many other accelerators available for use for each phase, workstream and roadmap
available for activities throughout the project.

Applying a full agile approach by running sprints in the explore phase is also possible when
using SAP Activate.

The above diagram details activities on how to initialize scrum activities, as well as how to
conduct the requirements gathering sessions using sprints in the explore phase workshops.
Continuing with running applying scrum in the explore phase, the above diagram shows how to
perform design updates, verification, and sign-off, using a sprint in the explore phase
workshops.

This slide provides a description of the Realize phase along with related key activities to be
performed.
Project teams in SAP projects can be structured in different ways. The above example shows the
structuring of scrum teams by modular or end to end process, as well as by supporting teams.

• Scrum teams include 5 to 9 members with assigned SAP Project Roles.

• Scrum teams may be organized by workstream and/or by Application Area.

• Scrum Master and Product Owner work with scrum team.

• Work across several scrum teams is coordinated through the Scrum of Scrums
Ceremony, where each scrum team delegates its representative.

• Project Managers, Agile Coaches, Architects, and other roles may also join the Scrum of
Scrums Ceremony.
 • The Scrum of Scrums ceremony is used to discuss topics of overlap or integration.

The diagram, Transparent Requirements to Deploy, illustrates the terminology structure and
relationship metrics in SAP agile projects.

Sprints

Sprints are a unit of measure or a period or time between two to four weeks long, where
incremental building of the solution takes place. Generally ending with a show and tell session
back to the business audience that raised the requirement in the workshop.

Waves

Waves are a unit of measure, and larger period with many sprints assigned to a one Wave.
Waves are generally one to three months in duration.

Phases

The Realize phase is the build phase and consists of one or more waves depending on the size
of the project.

Release

A release is all functionalities built ending with a go-live. Projects can have one or several
releases, depending on project scope and time.
This diagram provides a good illustration of what a typical Realize phase looks like in an agile
context. In the example, there are several sprints from the start of the phase, ending with a user
acceptance testing. Included in this example is i firm-up sprint where string testing is
performed. Sting testing tests the integration or overlap aspects of the functionality built in the
prior sprints.

Integration testing can also be delivered via sprints. Integration testing covers the testing of all
functionalities built. This is the final testing performed by the consulting team before the
business team tests the system in User Acceptance Testing.
Accessing Content
Access to Content

Access to Content

When starting your SAP project journey, these are the enablers to ensure project
efficiency and success. The SAP Activate Community, SAP Activate Roadmap Viewer,
and SAP Signavio Process Navigator provide all the major reference content required in
all deployment types. These three content provisioning tools are primary enablers for
your digital transformation journey and can be accessed via the following links:

• SAP Activate Community

• SAP Activate Roadmap Viewer

• SAP Signavio Process Navigator

What is the purpose of the SAP Activate Roadmap Viewer?

The purpose of SAP Activate Roadmap Viewer is to provide access to the SAP Activate
Methodology implementation roadmaps. Implementation roadmaps offer a
comprehensive view of your project teams' associated activities, deliverables, and
tasks, with accompanying accelerator assets in document and hyperlink format.

SAP Activate implementation roadmaps are organized by logical categories or by

solution and provides a prescriptive guidance for project tasks and deliverables
required to ensure a successful project implementation.

Access all your enterprise project management resources and project phases for many
SAP solutions in this easy to consume format.

The structure of the SAP Activate Roadmap Viewer includes:

• Phases: Stages of the project. At the end of each phase, a quality gate exists to
verify the completion of the deliverables.

• Deliverables: Outcomes that are delivered during the course of the project.
Several deliverables are included within a phase.

• Tasks: Work to be performed. One or several tasks comprise a deliverable.

• Workstreams: A collection of related deliverables that show time relationships

within a project and among other workstreams. Workstreams can span phases,
and are not necessarily dependent on phase starts and ends.

• Accelerators: Provide assistance in the form of How-to guides, best practice

recommendations, prescriptive templates, and links to learning materials.
Accelerators are linked in tasks.

SAP Activate Roadmap Viewer provides a structured approach to the software

implementation process. Activities are split into distinct phases with deliverables and
tasks that help project teams to better plan, execute, and manage their implementation
project.

SAP solution implementation roadmaps aim to assist by providing implementation

project teams with recommended lists of the following:

• Deliverables (the 'what') in each phase.

• A process description in the form of details and tasks (the 'how').

• Accelerators (such as templates, examples, guides, and web links) are assets to
support the tasks and key milestones of the implementation.

You can search for content on the SAP Activate Roadmap Viewer by Phase, Workstream,
or Accelerator, and combine these to narrow down your results.

The above diagram displays some of accelerators available for download on the SAP
Activate Roadmap Viewer. These accelerators are available to be downloaded and used
in your project.
This Onboarding Guide is an actual example of an accelerator available on the SAP
Activate Roadmap Viewer.

This Business Driven Configuration Questionnaire is an actual example of an

accelerator available on the SAP Activate Roadmap Viewer.
This How to Approach Fit to Standard Analysis document is an actual example of an
accelerator available on the SAP Activate Roadmap Viewer.

There are four major implementation roadmap types:

• Cloud Specific Methodology (1): Provides prescriptive guidance on the SAP cloud
specific offerings.

• On-Premise Specific Methodology (2): Provides prescriptive guidance on SAP on-

premise specific offerings.

• Upgrade Methodology (3): Provides prescriptive guidance on upgrades for

specific solutions.
• General (4): Provides framework and approach for running a project across a
range of solutions.

• On the top level of roadmap structure:

1. Overview provides high-level information by phase and contains the

deliverables by workstream images and overview details per phase.

2. Content leads to main Structure of the roadmap which starts with the
phase, followed by the deliverables and tasks.

3. Project teams have the option to narrow down content with the use of
filters. Filters are available for phases, workstreams, products, and
additional tags.

4. Accelerators are documents and assets which come in the form of

templates, documents, and web-resources.

5. Project Plans are available for downloading for the project team to use.

• Content Structure (2) is structured by:

o Phases

o Deliverables

o Tasks

• Content Filters (3) are available by:

o Phase

o Workstream
 o Product

o More tags

The following accelerators in SAP Signavio Process Navigator:

• Scope item fact sheets: A description of the business process including

business benefits and key process steps covered.

• Process flow: A representation of the standard business process to show how

the software works by default.

• Solution Process flow (BPMN2): A downloadable version of the business process

flow that can be edited in process modeling applications if the standard process
flow is customized. It's important to document any process that no longer
follows the standard process.

• Test scripts: A procedure for testing the activated system according to the
defined business process.

• Set-up instructions: A guide with instructions to set up the prerequisite

requirements (usually an integration) before the test script can be completed.

• Task tutorials: A guided tutorial for the scenario.

The above diagram displays the structure of the SAP Signavio Process Navigator and the
related content available within the structure.

The Solution Packages are structured as follows:

• Scope Item Groups

Scope Item Groups represent a department (Line of Business [LOB]) or Software

Module.

• Business Area

The Business area represents a business scenario.

• Scope Items

Scope Items are Business Processes.

• Building Blocks

Building Blocks are configuration documents which support consultants in configuring

the related business processes and related business process steps.
There are several Best Practices solution packages available for the different products
on the SAP Signavio Process Navigator. Each of these Solution packages consists of
solution specific content including:

• Customer Scope Presentations

• SAP Notes

• Processes Steps, Business Roles, and related SAP Fiori apps

• A list of all prerequisites

• Forms

• What's New

• Task Tutorials

These are in addition to the other content available including, process diagrams, test
cases, and configuration guides.
This is an example of a test case for a business process available on the SAP Signavio
Process Navigator. There are individual business process test cases available to
download for related processes. This is a significant accelerator as consultants don't
need to create test cases, and only need to adjust those found on the SAP Signavio
Process Navigator to suit business processes which have been updated with delta
requirements.

This is an example of a business process flow diagram for a business process available
on the SAP Signavio Process Navigator. There are individual business process diagrams
available to download per business process. This is a significant accelerator as
consultants don't need to design processes from scratch, and only need to adjust those
found on the SAP Signavio Process Navigator to suit business processes which have
been updated with delta requirements.

Business process diagrams are available in BPMN format and can be updated or edited
using SAP Cloud ALM, or Signavio.

This is an example of a task tutorial for a business process available on the SAP Signavio
Process Navigator. There are multiple tutorials for individual business processes
available. This supports project teams with training or demonstration activities within
the project.
When we enter the SAP Activate Community, you will be provided with many resources
and content to help guide you through your SAP Activate project implementation (latest
SAP Activate updates, blogs, Q&A, and expert insights):

1. Enter the SAP Activate Community by clicking the

link: https://community.sap.com/topics/activate

Follow the SAP Activate Community by clicking 'Follow' to stay on top of the latest
content and SAP Activate topics.

The site is structured to allow users to collaborate, by providing an easy to access place
to ask questions, share experiences, and get the latest information about SAP Activate.

You can interact with, and provide insights to the SAP Activate Community by clicking
'Ask a Question', 'Write a Blog Post' (make sure to tag 'SAP Activate' prior to publishing
your blog), reviewing the latest content and resources that are available, review the
'Featured Content', and consume the additional SAP Activate content that is available
within the community.
Purpose:

Access the latest SAP delivery methodologies that support SAP Project Teams in
delivery of solution implementation, upgrade or migration projects, and customer
engagements.

Benefits:

• Direct connection to SAP Activate experts

• Questions and answers in the context of SAP Activate Content Structure

• Submit your feedback and ideas on SAP Activate Framework to SAP Activate
content owners

• Create and search blogs related to SAP Activate topics

• Register and listen to SAP Activate experts in community calls

• Subscribe to forums, feeds, and content updates

Structure:

SAP Activate Community main page

• Topic Resources

• Community Content

• Getting Started with SAP Activate Resources

• Implementation and Deployment sub-page

• SAP Activate Blogs and Q&A Forum