2595 Reading Sample

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 40

Contents

Preface ....................................................................................................................................................... 19

1 Introduction to SAP Cloud ALM and SAP Activate 25

1.1 Introduction to SAP Cloud ALM ....................................................................................... 26


1.1.1 Features of SAP Cloud ALM ................................................................................. 27
1.1.2 Differentiating Between SAP Cloud ALM from Other ALM Tools ........... 29
1.2 SAP Cloud ALM Areas ........................................................................................................... 31
1.2.1 SAP Cloud ALM for Implementation ................................................................ 33
1.2.2 SAP Cloud ALM for Operations ........................................................................... 34
1.2.3 SAP Cloud ALM for Service ................................................................................... 34
1.3 SAP Activate ............................................................................................................................. 35
1.3.1 SAP Activate as a Framework ............................................................................. 35
1.3.2 SAP Activate Methodology .................................................................................. 36
1.3.3 SAP Best Practices Explorer and SAP Signavio Process Navigator .......... 38
1.3.4 SAP Central Business Configuration ................................................................ 40
1.3.5 SAP Activate in Connection with SAP Cloud ALM ........................................ 44
1.4 Our Practical Example ......................................................................................................... 44

1.5 Summary ................................................................................................................................... 46

Part I Prepare

2 Provisioning of the SAP Cloud ALM Tenant 49

2.1 Prerequisites ............................................................................................................................ 50


2.1.1 Scope of Usage Rights ........................................................................................... 51
2.1.2 Authorizations for the Cloud Administrator ................................................. 51
2.2 Provisioning Process ............................................................................................................. 52

2.3 Further Preparation Steps ................................................................................................. 55


2.3.1 Customize Logon Title and Logo ....................................................................... 55
2.3.2 Create Cloud and Project Administrators ...................................................... 57
2.3.3 Planning the Onboarding and Training Concept ......................................... 59

7
Contents Contents

2.4 Additional Costs ..................................................................................................................... 60

2.5 Summary ................................................................................................................................... 61

3 Management of the Project Landscape 63

3.1 Project Landscape Management .................................................................................... 64


3.1.1 Example: SAP Integration Suite ......................................................................... 65
3.1.2 Example: SAP S/4HANA ....................................................................................... 66
3.2 Managed Landscape Groups ............................................................................................ 67
3.2.1 Services ...................................................................................................................... 68
3.2.2 Systems ...................................................................................................................... 72
3.3 Manageable Information ................................................................................................... 76
3.3.1 Lifecycle Status ........................................................................................................ 77
3.3.2 Use Cases .................................................................................................................. 79
3.3.3 Endpoints .................................................................................................................. 81
3.4 Service Key Enabling and Maintenance ...................................................................... 82

3.5 Scenario with Multiple SAP Customer Numbers ..................................................... 85

3.6 Summary ................................................................................................................................... 86

4 Transport Tools of SAP Cloud ALM 87

4.1 SAP Cloud Transport Management ............................................................................... 89


4.1.1 Prerequisites ............................................................................................................ 91
4.1.2 Setting up Transport Management for Cloud Integration ....................... 92
4.2 Change and Transport System ......................................................................................... 98
4.2.1 Prerequisites ............................................................................................................ 98
4.2.2 Setting up Transport Management for SAP S/4HANA .............................. 100
4.3 Adaptation Transport Organizer .................................................................................... 105

4.4 Summary ................................................................................................................................... 107

5 Project Approach with Agile Methodology 109

5.1 Basics of Agile Methodology with Scrum ................................................................... 111


5.1.1 Before the Start ....................................................................................................... 111

8 8
Contents

5.1.2 Stakeholders and Requirements ....................................................................... 112


5.1.3 Product Owner and Product Backlog ............................................................... 113
5.1.4 Sprint Planning and Sprint Backlog .................................................................. 113
5.1.5 Sprint Execution and Daily Scrum .................................................................... 115
5.1.6 Sprint End: Sprint Review, Product Increment, and Sprint
Retrospective ........................................................................................................... 116
5.1.7 Product Backlog Refinement .............................................................................. 117
5.2 Support for Scrum in SAP Cloud ALM ........................................................................... 118
5.2.1 Agile Approach in the SAP Activate Method ................................................. 120
5.2.2 Requirements, User Stories, and Features ..................................................... 122
5.2.3 Roles and Responsibilities ................................................................................... 122
5.2.4 Timeboxing ............................................................................................................... 123
5.3 Project Approaches for SAP Implementation Projects .......................................... 127
5.3.1 On-Premise Scenario/Hybrid Scenario ............................................................ 128
5.3.2 Cloud-Centric Scenario ......................................................................................... 128
5.3.3 Single Deployment ................................................................................................. 128
5.3.4 Template, Rollout, and Further Deployments .............................................. 129
5.4 Specifications and Conventions for the Project Setup ......................................... 130
5.4.1 Project Setup for the Example Scenario ......................................................... 130
5.4.2 Hybrid Scenario: Initial Template Development ......................................... 132
5.4.3 Hybrid Scenario: Further Template Development ...................................... 135
5.4.4 Hybrid Scenario: Rollouts ..................................................................................... 137
5.4.5 Hybrid Scenario: Further Deployments .......................................................... 141
5.5 Summary ................................................................................................................................... 141

6 Project Setup 143

6.1 General Information ............................................................................................................ 144


6.1.1 SAP Activate Templates (Task Templates) ..................................................... 146
6.1.2 Status and Planning .............................................................................................. 147
6.2 Timeboxes ................................................................................................................................. 147
6.2.1 Phases ......................................................................................................................... 148
6.2.2 Sprints and Milestones ......................................................................................... 148
6.2.3 Quality Gates ........................................................................................................... 150
6.3 Teams .......................................................................................................................................... 156
6.3.1 Creating Teams ....................................................................................................... 156
6.3.2 Create Your Own Roles ......................................................................................... 158

9
Contents Contents

6.4 Scopes ......................................................................................................................................... 160

6.5 Deployment Landscape and Deployment Plan ........................................................ 161


6.6 Tag Management .................................................................................................................. 162

6.7 Summary ................................................................................................................................... 167

7 Define Project Scope 169

7.1 Create Scope ............................................................................................................................ 171

7.2 Preparation for a Fit-to-Standard Workshop ............................................................ 176

7.3 Define Tasks ............................................................................................................................. 181

7.4 Define Solution Process ...................................................................................................... 183

7.5 Tools for Scope Definition of the Project .................................................................... 188


7.5.1 SAP Readiness Check ............................................................................................. 188
7.5.2 SAP Business Transformation Center and Digital Blueprints .................. 194
7.6 Summary ................................................................................................................................... 201

8 User Management and Project Reporting 203

8.1 Project Onboarding ............................................................................................................... 204


8.1.1 Identity Authentication Service ......................................................................... 204
8.1.2 Add Users to SAP Cloud ALM .............................................................................. 207
8.1.3 Create and Authorize Users ................................................................................ 221
8.1.4 Create Your Own Role Collections .................................................................... 222
8.1.5 Manage Users and Assign Roles ........................................................................ 223
8.1.6 Approve User Requests ......................................................................................... 226
8.1.7 Define Project Access Permissions ................................................................... 227
8.2 Project Progress and Project Reporting ....................................................................... 229
8.2.1 Project Overview ..................................................................................................... 230
8.2.2 Tasks ........................................................................................................................... 232
8.2.3 Analytics .................................................................................................................... 234
8.2.4 Cross-Project Analysis ........................................................................................... 238
8.3 Summary ................................................................................................................................... 239

10 10
Contents

Part II Explore

9 Process and Document Management 243

9.1 Processes in SAP Cloud ALM ............................................................................................. 245

9.2 Documents ............................................................................................................................... 246

9.3 Solution Value Flow ............................................................................................................. 251

9.4 Solution Process Flow .......................................................................................................... 252


9.5 Process Authoring ................................................................................................................. 257

9.6 Process Hierarchy .................................................................................................................. 260

9.7 Outlook on the Integration with SAP Signavio ........................................................ 266

9.8 Summary ................................................................................................................................... 267

10 Requirements Management 269

10.1 Overview of Requirements ............................................................................................... 270

10.2 Creation of Requirements ................................................................................................. 273


10.2.1 Creation via the Solution Process ..................................................................... 275
10.2.2 Creation as a Standalone Requirement .......................................................... 277
10.3 Specification of Requirements ........................................................................................ 278
10.3.1 Best Practices for Requirements Specification ............................................. 278
10.3.2 Text Example for Requirements ........................................................................ 280
10.3.3 Further Information on Requirements ............................................................ 281
10.4 Handover of Requirements for Implementation .................................................... 284
10.4.1 Preparation for Handover to Implementation ............................................. 284
10.4.2 Requirement Approval .......................................................................................... 285
10.4.3 Possible Follow-Up Elements ............................................................................. 286
10.4.4 Outlook on User Stories ....................................................................................... 288
10.5 Enrichment of Requirements during Implementation ......................................... 289

10.6 Summary ................................................................................................................................... 291

11
11
Contents Contents

11 Fit-to-Standard and Fit-Gap Workshops 293

11.1 Differences Between Fit-to-Standard and Fit-Gap Workshops ........................ 294

11.2 Fit-to-Standard Workshops .............................................................................................. 296


11.2.1 Definitions and Basics .......................................................................................... 297
11.2.2 Project Tasks ............................................................................................................. 298
11.2.3 Steps 1 to 3: View, Demonstrate, and Compare Processes ...................... 300
11.2.4 Step 4: Identify Requirements ........................................................................... 302
11.2.5 Step 5: Define Configurations ............................................................................ 303
11.2.6 Step 6: Empower the Customer ........................................................................ 303
11.3 Fit-Gap Workshops and Rollouts .................................................................................... 303

11.4 Summary ................................................................................................................................... 305

12 Test Management 307

12.1 Test Management in SAP Cloud ALM ........................................................................... 308

12.2 Planning the Test Preparation ......................................................................................... 310


12.2.1 SAP Activate and Test Management ............................................................... 310
12.2.2 Determining Test Scope ....................................................................................... 311
12.2.3 Dashboards for Test Preparation ...................................................................... 311
12.2.4 Tagging Function in Test Management .......................................................... 312
12.3 Test Automation in SAP Cloud ALM .............................................................................. 313
12.3.1 Test Automation Tool for SAP S/4HANA Cloud ............................................ 314
12.3.2 SAP Test Automation by Tricentis with SAP Cloud ALM ........................... 315
12.4 Summary ................................................................................................................................... 319

Part III Realize

13 Agile Implementation of User Stories 323

13.1 Creation of Sprints ................................................................................................................ 324

13.2 From the Requirements Backlog to the Product Backlog .................................... 328

13.3 Overview of User Stories .................................................................................................... 330


13.3.1 Create a User Story from a Requirement ....................................................... 331
13.3.2 Specify User Story ................................................................................................... 336

12 12
Contents

13.4 Sprint Planning ....................................................................................................................... 338


13.4.1 Structure of a Product Backlog .......................................................................... 338
13.4.2 Assigning the User Story Selection to the Sprint ......................................... 339
13.4.3 Structure of a Sprint Backlog .............................................................................. 340
13.4.4 Review of the User Story Selection ................................................................... 340
13.4.5 Set Requirements to In Realization .................................................................. 344
13.4.6 Creating Features ................................................................................................... 345
13.5 Processing User Stories during Sprint Execution .................................................... 346
13.5.1 Processing the User Story by the Developers in the Sprint ...................... 346
13.5.2 Creating Transports for Implementation ....................................................... 347
13.5.3 Assigning Test Cases to a User Story ............................................................... 351
13.6 Daily Scrum: Daily Meetings ............................................................................................ 351

13.7 Sprint Review Meeting ........................................................................................................ 355

13.8 Sprint Retrospective ............................................................................................................. 357

13.9 Summary ................................................................................................................................... 358

14 Test Preparation 359

14.1 Solution Walkthrough and Test Cycles ........................................................................ 360

14.2 Test Case Creation ................................................................................................................. 361


14.2.1 Create and Edit Manual Test Cases .................................................................. 362
14.2.2 SAP Best Practice Content for Test Cases ....................................................... 366
14.2.3 Uploading Test Cases ............................................................................................ 366
14.2.4 Create and Import Automated Test Cases ..................................................... 368
14.2.5 Releasing Test Cases .............................................................................................. 372
14.3 Test Case Assignment to User Story and Requirement ........................................ 372

14.4 Test Plan .................................................................................................................................... 374


14.4.1 Create and Prepare Test Plans ........................................................................... 374
14.4.2 Handover Test Plans to Execution .................................................................... 378
14.5 Summary ................................................................................................................................... 379

15 Test Execution 381

15.1 Run Test Cycle ......................................................................................................................... 382


15.1.1 Execution of Manual Test Cases ....................................................................... 384
15.1.2 Execution of Automated Test Cases ................................................................ 388

13
13
Contents Contents

15.2 Defect Management ............................................................................................................ 389


15.2.1 Defect Dispatching ................................................................................................ 391
15.2.2 Defect Processing ................................................................................................... 393
15.2.3 Defect Closing .......................................................................................................... 397
15.3 Test Progress and Defect Monitoring ........................................................................... 397
15.3.1 Test Execution Analysis ........................................................................................ 398
15.3.2 Defects Reporting ................................................................................................... 401
15.3.3 Traceability of Solution Processes, Requirements, and User Stories .... 402
15.3.4 Project Overview ..................................................................................................... 404
15.4 Documentation of Results and Handover for Deployment ................................ 405

15.5 Summary ................................................................................................................................... 405

Part IV Deploy

16 Change Enablement 409

16.1 Record, Manage, Control, and Deploy Changes ...................................................... 410

16.2 Release Management in Theory ..................................................................................... 411

16.3 Importance of Release Management in Software Development .................... 411

16.4 Release Management with SAP Cloud ALM .............................................................. 412


16.4.1 Developing a Sprint Concept .............................................................................. 412
16.4.2 Defining User Stories and Features .................................................................. 414
16.4.3 Planning Sprints and Resources ........................................................................ 414
16.4.4 Carrying Out Sprints and Monitoring Progress ............................................ 415
16.5 Release Management in Hybrid System Landscapes ............................................ 416
16.5.1 Template Rollout Approach ................................................................................ 419
16.5.2 Infrastructure and Components in a Template Release ........................... 422
16.5.3 Planning and Implementation of Template Rollouts ................................. 422
16.5.4 Process Example for a Template Rollout Approach .................................... 423
16.6 Release Management in Cloud System Landscapes .............................................. 432

16.7 Corrections during Operation .......................................................................................... 435

16.8 Summary ................................................................................................................................... 435

14 14
Contents

17 Deployment with SAP Cloud ALM 437

17.1 Technical Preparations ........................................................................................................ 438


17.1.1 Consolidation of Systems into System Groups ............................................ 438
17.1.2 Planning the Deployment ................................................................................... 440
17.1.3 Linking the Deployment Plan and Project ...................................................... 442
17.2 Features Overview ................................................................................................................ 443
17.2.1 Status Overview ...................................................................................................... 444
17.2.2 Create Features ....................................................................................................... 447
17.3 Change Control with the Help of Features ................................................................ 451
17.3.1 Transportation Creation ...................................................................................... 452
17.3.2 Start Feature Implementation ........................................................................... 455
17.3.3 Transport of Copy ................................................................................................... 456
17.3.4 Release Transport ................................................................................................... 458
17.3.5 Import Transport into the Test System ........................................................... 459
17.3.6 Handover for Testing ............................................................................................ 461
17.3.7 Approve for Production ........................................................................................ 461
17.3.8 Import Transport into the Production System ............................................. 461
17.3.9 Confirm and Complete Feature Import .......................................................... 462
17.4 Mass Deployment of Features into Production ....................................................... 463

17.5 Transport Protocols .............................................................................................................. 464

17.6 Milestone for Handover to Operations ....................................................................... 465

17.7 Summary ................................................................................................................................... 468

Part V Operate

18 Overview of SAP Cloud ALM for Operations 471

18.1 Business Service Management ........................................................................................ 472

18.2 Monitoring and Event Management ............................................................................ 473


18.2.1 Recognize Events .................................................................................................... 473
18.2.2 Forwarding and Resolving Events ..................................................................... 490
18.3 Summary ................................................................................................................................... 497

15
15
Contents Contents

19 Implementation 499

19.1 Business Service Management ........................................................................................ 500

19.2 Business Process Monitoring ............................................................................................ 507


19.2.1 Checking the Prerequisites .................................................................................. 507
19.2.2 Initial Configuration .............................................................................................. 508
19.2.3 Specific Configuration .......................................................................................... 510
19.3 Integration and Exception Monitoring ........................................................................ 514
19.3.1 Checking the Prerequisites .................................................................................. 514
19.3.2 Initial Configuration .............................................................................................. 515
19.3.3 Specific Configuration .......................................................................................... 519
19.4 Real User Monitoring ........................................................................................................... 527
19.4.1 Checking the Prerequisites .................................................................................. 528
19.4.2 Initial Configuration .............................................................................................. 528
19.5 Synthetic User Monitoring ................................................................................................ 531
19.5.1 Initial Configuration .............................................................................................. 532
19.5.2 Specific Configuration .......................................................................................... 534
19.6 Job and Automation Monitoring .................................................................................... 540
19.6.1 Checking the Prerequisites .................................................................................. 540
19.6.2 Initial Configuration .............................................................................................. 541
19.6.3 Specific Configuration .......................................................................................... 543
19.7 Health Monitoring ................................................................................................................ 546
19.7.1 Checking the Prerequisites .................................................................................. 547
19.7.2 Initial Configuration .............................................................................................. 548
19.7.3 Specific Configuration .......................................................................................... 552
19.8 Email Notifications and Ticket Creation ..................................................................... 555
19.8.1 Set Up Email Event Action ................................................................................... 555
19.8.2 Set Up Ticket Event Action .................................................................................. 558
19.9 Notes for the Operating Phase ........................................................................................ 559
19.9.1 Optimization the Configuration ....................................................................... 559
19.9.2 SAP Focused Run Reverse Proxy ........................................................................ 561
19.9.3 Next Generation Data Collection Infrastructure with
OpenTelemetry ....................................................................................................... 562
19.10 Summary ................................................................................................................................... 563

16 16
Contents

Part VI Extend and Integrate

20 Extension Basics 567

20.1 Extension Types ...................................................................................................................... 567


20.1.1 SAP BTP Services ..................................................................................................... 568
20.1.2 SAP Cloud ALM APIs ............................................................................................... 568
20.1.3 SAP Solution Extensions ....................................................................................... 569
20.1.4 Your Applications ................................................................................................... 569
20.2 Introduction to SAP Business Accelerator Hub ........................................................ 570
20.2.1 Testing with the API Sandbox ............................................................................ 572
20.2.2 Testing with Cloud Integration .......................................................................... 576
20.3 SAP Integration Suite ........................................................................................................... 579
20.3.1 Cloud Integration ................................................................................................... 579
20.3.2 Other Tools ............................................................................................................... 581
20.3.3 Versions ..................................................................................................................... 583
20.4 External API Management ................................................................................................ 584
20.5 Basic Use of APIs .................................................................................................................... 592
20.5.1 Pull APIs ..................................................................................................................... 593
20.5.2 Push APIs ................................................................................................................... 600
20.6 Best Practices ........................................................................................................................... 601
20.7 Summary ................................................................................................................................... 605

21 Overview of APIs 607

21.1 APIs in the Implementation Area: Build ...................................................................... 609


21.1.1 Analytics API ............................................................................................................. 609
21.1.2 Project API ................................................................................................................. 613
21.1.3 Task API ...................................................................................................................... 614
21.1.4 Custom Process API ................................................................................................ 616
21.1.5 Process Scopes API ................................................................................................. 619
21.2 APIs in the Operation Area: Run ..................................................................................... 621
21.2.1 Analytics API ............................................................................................................. 621
21.2.2 Status Event API ...................................................................................................... 622
21.2.3 Event Situations API .............................................................................................. 624
21.2.4 Resource Changes API ........................................................................................... 624
21.2.5 Raw Data Outbound Metrics API ...................................................................... 625
21.3 Summary ................................................................................................................................... 627

17
17
Contents Contents

22 Practical Examples 629

22.1 Creating GitHub Issues for Alarms in Integration Monitoring .......................... 629
22.1.1 GitHub API for Issues ............................................................................................. 630
22.1.2 External API Management .................................................................................. 633
22.1.3 Intelligent Event Processing ............................................................................... 638
22.1.4 Practical Application .............................................................................................. 640
22.2 Integration of Microsoft To Do ........................................................................................ 642
22.2.1 Technical Aspects of the Integration of Microsoft To Do ......................... 643
22.2.2 Implementation of the Microsoft Graph API for Microsoft To Do ......... 645
22.2.3 Implementation of the SAP Cloud ALM API ................................................... 658
22.2.4 Practical Application .............................................................................................. 661
22.3 Summary ................................................................................................................................... 663

The Authors ............................................................................................................................................. 665


Index .......................................................................................................................................................... 669

18 18
Chapter 6
Project Setup
In this chapter, you will learn how to create projects in SAP Cloud ALM.
In addition to selecting SAP Activate templates, you will be able to add
your own content to existing timeboxes, project members, and project
6
roles.

Prepare Explore Realize Deploy Run

Prepare

2 3 4 5 6 7 8

Provisioning Landscape Transport Tools Agile Methodology Project Setup Project Scope Project
Administration
• Tenant for • Administration • SAP Cloud • Basics • SAP Activate Roadmap • Tools
SAP Cloud ALM • Services Transport • Scrum • Timeboxes • Scopes • User
• Systems Management • Teams and Roles • Preparation of • Authorization
• CTS Project Approach • Scope Fit-to-Standard • Project Progress
• System Groups • Scoping
• SAP Implementation • Deployment Plans • Solution
Projects • Workstreams Processes
• Specifications and
Conventions

In the previous chapters, in addition to the introduction to SAP Cloud ALM and SAP
Activate, you were also able to familiarize yourself with provisioning a tenant for SAP
Cloud ALM. We also explained how you can set up the project landscape and the
required transport tools, which will also play a role in this chapter. The last chapter
focused on the agile project methodology as a central core element of the realize phase.
We discussed the various project approaches and explained our recommendations for
the specifications and conventions for implementing a hybrid scenario using our
example scenario. We will return to these approaches in this chapter to illustrate the
setup of a project on the system.
The project is a central entity in SAP Cloud ALM and a mandatory prerequisite for sup-
porting the implementation of SAP products with SAP Cloud ALM. This chapter will
deal in detail with the creation of a project and all the parameters to be defined for a
project.

143
143
6 Project Setup 6 Project Setup

After successfully logging in to your SAP Cloud ALM tenant, navigate to the app group
SAP Cloud ALM for Implementation and open the Projects and Setup app, as shown in
Figure 6.1.

Figure 6.1 Projects and Setup App

6.1 General Information


Before we create a new project, let's first clarify the term “project” in the context of SAP
Cloud ALM. A project is the container that contains all relevant information (i.e., enti-
ties and content). The following information is required in the first step:
 Name  Scope
 Dates (time periods)  System landscape
 Team (project members)

Once you have opened the Projects and Setup app, you will see all existing SAP Cloud
ALM projects in the Manage Projects area on the left-hand side. To create a new project
in your role as a project manager, select the project name as shown in Figure 6.2 select
the Create button.

144 144
6.1 6 Project
General Setup
Information

6
Figure 6.2 Create a New Project

If the button is not visible, you can use the menu with the three-dot symbol (Addi-
tional Options menu) to access the Create button (see Figure 6.3). You can also see in
the illustration how the New Project area and the General Information tab opens after
clicking the Create button on the right.

Figure 6.3 New Project: General Information

The first step is to assign a project name, which is also defined as a mandatory field. The
project name used in this book has already been described in detail in Chapter 5, Sec-
tion 5.4.2.

Show History Button


In case you want to see what was changed within your project: Press the Show History
button and see all the information that was changed together with corresponding
user and date/time information (see Figure 6.4).

145
145
6 Project Setup 6 Project Setup

Figure 6.4 Show History

6.1.1 SAP Activate Templates (Task Templates)


Since you learned about the SAP Activate methodology in Chapter 1, Section 1.3, you
can use the SAP Activate Roadmap selection list to select the SAP Activate content you
will use for your project. In this example, SAP S/4HANA (on-premise) – New Implemen-
tation is selected. The selection of SAP Activate templates is strongly recommended,
because if you do not select a template, only basic tasks for setting up and using SAP
Cloud ALM are available.
You can select between Single Roadmaps and Combinable Roadmaps. With combinable
roadmaps, you can combine several roadmaps in a single project. You can see the list of
currently available SAP Activate roadmaps in Figure 6.5.

Figure 6.5 SAP Activate Roadmaps

146 146
6 Project
6.2 Setup
Timeboxes

The SAP Activate content provided is continuously expanded and is available in SAP
Cloud ALM shortly afterwards. In your role as project manager, you should select the
SAP Activate template for the SAP product that plays a leading role in your implemen-
tation project.
Below the list of roadmaps, you will see the Access Level selection list. The options are:
 Public
 Restricted 6
 Private

You have the option of restricting access to your project via the access level. This option
has only been available, however, since December 2022. If you created projects before
then, they are automatically defined as Public. Below this, in the section Integration
Scenario, you will find the option to activate the integration of SAP Cloud ALM projects
with multiple SAP Central Business Configuration projects (see Figure 6.3).

6.1.2 Status and Planning


In the right part of Figure 6.3, you can see the Status and Planning area in the project
view. The SAP Cloud ALM project can have one of the following statuses:
 On Track
 Needs Attention
 Critical

By selecting the project status, you as the project manager can see in the project over-
view which projects you need to pay attention to. This is helpful if you are working on
several projects at the same time. Below the Status section, you can see the Current
Phase. You can change the phase by selecting a different phase in the selection list and
then saving. The project manager is displayed to the right of Status and Planning in the
Object area.
In this section, you have created an SAP Cloud ALM project and maintained general
information. In the following, we will guide you through the most important settings
and specifications.

6.2 Timeboxes
Every project needs a defined start and a defined end. All data (defined points in time
or time periods in the SAP Cloud ALM project) is defined by timeboxes. These time-
boxes can be assigned to tasks, phases, sprints, and milestones and are explained in
this section.

147
147
6 Project Setup 6 Project Setup

6.2.1 Phases
Phases are defined by the SAP Activate methodology. The phases already delivered by
SAP Cloud ALM are:
 Prepare  Deploy
 Explore  Run
 Realize

You can also add your own phases to the list using the plus symbol (Add Custom
Phase) to the right of the last phase. The new phase can also be deleted by clicking on
the cross symbol (Remove Custom Phase). The human symbol to the left of the
phase name indicates that this phase was created individually and was not predefined
by the SAP Activate roadmap or template. To define the period for the respective phase,
select the calendar symbol on the right in the Enter Date Range... line. . With the first
click, you define the start date, and with the second click, you define the end date of the
phase. This results in the implementation period of the phase. You can also deactivate
phases by clicking on the slider symbol to the right of the calendar symbol. This is
useful if not all delivered phases are relevant for your project. In Figure 6.6 you can see
the implementation of the template approach for our example scenario, AriHana 2024.

Figure 6.6 Timeboxes: Phases

6.2.2 Sprints and Milestones


Below the phases, you can define the sprints and store your sprint planning in SAP
Cloud ALM. If your way of working is predetermined by stakeholders or similar outside

148 148
6 Project
6.2 Setup
Timeboxes

decision-makers, you might not need a sprint plan and can just use the time periods of
the phases. This is usually the case if the scope of the project is already defined at the
start. If the scope of the project has not yet been finalized or if it is about the continuous
improvement of an existing functionality, you may follow the agile project methodol-
ogy approach. Experience shows that both approaches are mixed. This means that
sprint planning is agreed for the implementation phase and the sprints do not exist at
the hierarchy level of the phases. It is therefore not necessary to synchronize sprints
with phases, but it is advisable—and recommended—to determine the appropriate 6
phase based on the sprint period. If you don’t link the sprint planning to the associated
phases, you will need to use more effort to create the various filter settings. If you
delete a sprint, the appropriate phase and its due date are used as a fallback solution.
Figure 6.7 shows an example of sprint planning for the AriHana template project.

Figure 6.7 Timeboxes: Sprints

149
149
6 Project Setup 6 Project Setup

In contrast to phases and sprints, only the end date is set for milestones. Here you can
add additional milestones by clicking on the (Add Milestone) button to add addi-
tional milestones and the (Remove Milestone) button to delete added milestones, as
shown in Figure 6.8. The sorting here is chronological. If you assign a timebox (phase,
sprint, or milestone) to a task, the end of the timebox is automatically defined as the
due date of the task. This makes it easy for you as the project manager to adjust the
time periods and due dates in the event of any project delays. If you change the due
date of a task manually, it no longer updates automatically if a timebox changes.

Figure 6.8 Timeboxes: Milestones

6.2.3 Quality Gates


Quality gates in projects are critical checkpoints or even milestones that are necessary
to fulfill to move on to the next step. With these predefined quality standards, you can
ensure to meet all mandatory prerequisites before you enter next phase in your proj-
ect. Besides early issue detection, risk mitigation and quick project transparency as well
as the governance aspect are reasons for planning quality gates within your project.
Our recommendation for our newly created AriHANA-2024-TPL-R1 project is to have at
least one quality gate per phase. But according to your defined timeboxes, it could be
necessary to have more quality gates defined for your project. Therefore, you need to
go to the Tasks app and select the Quality Gate task Type as shown in Figure 6.9 and
Figure 6.10.

150 150
6 Project
6.2 Setup
Timeboxes

Figure 6.9 Tasks App

Figure 6.10 Select “Quality Gate” as Type

151
151
6 Project Setup 6 Project Setup

After that, you can create a new quality gate by selecting Quality Gate in the Create
dropdown list as shown in Figure 6.11.

Figure 6.11 Create New Task from Quality Gate Type

In Figure 6.12, you can see the initial screen of a quality gate creation. You are required
to give it a title, but a description is optional.

Figure 6.12 Create New Quality Gate: Title and Description

The measurable criteria for this specific quality gate are noted via checklist items. All
necessary factors that need to be fulfilled before we can pass this quality gate are listed
in the quality gate’s Checklist area. There are two ways to create checklist items:
 Create them manually via the Create button in the Checklist area (as shown in Figure
6.13)
 Use the upload and download function (as shown in Figure 6.14)

152 152
6 Project
6.2 Setup
Timeboxes

Figure 6.13 Create Checklist Item: Manual

Figure 6.14 Create Checklist Item: Upload and Download Function

The following elements are part of a good checklist and the corresponding questions
that can be answered there:

153
153
6 Project Setup 6 Project Setup

 Title: What is checked?


 Status: What is the result of this check?
 Planned Completion: When will it be checked?
 User Type: Who is checking? (Employee, SAP, Partner, Other)
 Description: What additional information is necessary for this check?
 Comments: What comments have been made by the people following this checklist?

In Figure 6.15, you can see how it looks in the system for our quality gate for the explore
phase.

Figure 6.15 Create Checklist Item: Elements

In Figure 6.15, you can also see the Project Tasks area below the checklist area. Project
tasks are tasks that you created on your own, in comparison to Roadmap tasks, and that
you identified as mandatory for your project. In this area, you can link quality gates to
your project tasks via the Assign button.
As explained in Section 6.2.2, it is also possible to link milestones to quality gates. To do
this, switch to the Additional Information tab. If you like the Gantt view, you can also
see quality gate milestones visualized that way. You can assign a status that corre-
sponds to the outcome of your check result for each of your defined checklist items.
The following statuses are available:
 Not Checked  Not Accepted
 Accepted  Not Relevant
 Conditionally Accepted

154 154
6 Project
6.2 Setup
Timeboxes

As all mandatory tasks for this quality gate are fulfilled in this case, the status is now
Conditionally Accepted.
If follow-up activities are necessary, you can create them via the Create Follow-up Task
button. With this button you can create a project task that is then automatically
assigned to this quality gate. In our example, we created a new project task to check
optional tasks related to the explore phase. Once this project task is completed (status
Done), you can switch the quality gate status to Accepted.
6
Usually, you will have some kind of team for reviewing such imported quality gates
when moving from one phase to each other. Participants on this review team can be
part of the following user groups or their representatives:
 Relevant project stakeholder
 Subject-matter experts or functional experts
 Project leads and members

It is their responsibility to examine the completeness, accuracy, and compliance of


deliverables for the checklist elements of this quality gate. Therefore, it is important to
set an appropriate status for each checklist item based on result of the check. If you
identify potential risks or deviations within the check of a quality gate, you should also
create a project task as follow-up to document and track it. After your analysis of the
quality gate checks, you can set the status based on the result as shown in Figure 6.16.

Figure 6.16 Create Checklist Item: Result Status

155
155
6 Project Setup 6 Project Setup

6.3 Teams
In the previous chapters, you have been introduced to the topic of roles and responsi-
bilities. This section is about assigning project roles to the responsible persons. First, we
will show you how to create your own teams and project roles.

6.3.1 Creating Teams


In the left-hand section of the Projects and Setup app, we have been working in the Proj-
ects tab. Now navigate to the second tab, Teams, and you will see that a team has
already been created automatically when the project was created: the PMO Team. The
PMO team is the only team in which the role of the project manager exists.
For this reason, the team cannot be deleted and is marked with a PMO symbol . You
can create a new team via the Create button. Figure 6.17 shows the creation of a team
for development.

Figure 6.17 Create New Development Team

The team’s name is a mandatory field, while the description is optional. Below this, you
will see the role assignment areas shown in Figure 6.18 is shown. The slider symbol
is used to define the project roles that exist in this team. Please note that you must also
assign the newly created project roles to the teams after creation.
In the example in Figure 6.18, some roles are already deactivated for the development
team. You can assign the appropriate project roles directly to your project members
here, or you can do it later when you are back in the detailed view of the project. When
deactivating the roles, both here in the administration and in the detailed view, note
that no more positions can be assigned after deactivation. Existing user assignments to
this role are removed. If user assignments already exist, they will remain in place. In the
upper area of Figure 6.18, you can see that the By Roles choice is selected by default. You
can also select the By Users assignment.

156 156
6 Project Setup
6.3 Teams

Figure 6.18 Role Assignment for the Development Team

After switching to By Users, you will see the Create button on the right-hand side of the
window. Click on it and then select the user on the left-hand side. On the right-hand
side, you can select the corresponding project roles for this user via the selection list, as
shown in Figure 6.19.
The users defined here can see their team members and edit them themselves. They
are also responsible for the task assignments according to their role as defined in the
role properties of the tasks. There is no direct link between the roles listed here and the
authorization roles. If a user is assigned to a team on a project for which they do not
have authorization, the system automatically sends a request to the administration
team. The team then decides whether to approve the user. Administrators also have
the option of granting users individual authorization for projects and tasks. This gives
these users access to projects and tasks, but they are not listed here.

157
157
6 Project Setup 6 Project Setup

Figure 6.19 Role Assignment According to Users

6.3.2 Create Your Own Roles


Now navigate to the third tab, Roles, in the Manage Projects section. There you will see
project roles that have already been created automatically when you created the SAP
Cloud ALM project (see Figure 6.20):
 Analytics Expert
 Business Process Expert
 Configuration Expert
 Data Migration Expert
 Education Expert
 Enterprise Architect
 Extensibility Expert
 Integration Implementation Expert
 Organizational Change Management Expert
 Output Management and Forms Expert

158 158
6 Project Setup
6.3 Teams

 Project Lead
 System Administrator
 Technology Expert
 Testing Expert

To use the agile project approach you learned in Chapter 5 and also to meet your
customer-specific requirements, you can add your own project roles in SAP Cloud ALM.
6
To do this, use the Create button and see the details to be maintained on the right-hand
side, as shown in Figure 6.20. Because of the symbol, you can see that this is a
customer-specific role.

Figure 6.20 Create New Project Role

159
159
6 Project Setup 6 Project Setup

We have added the following roles for the AriHana project in our practical example:
 Monitoring Expert  Release Manager
 Product Owner  Scrum Master

To give you an idea of how the assignment of project members to the roles in the proj-
ect can look, take a look at Figure 6.21 to see the assignments for our AriHana project.

Figure 6.21 Role Assignment in the AriHana Project

6.4 Scopes
The previous section dealt with the project members and how they are assigned project
roles. The configuration of scopes is explained in this section. The theoretical consider-
ation of project scopes is discussed in Chapter 7. As explained in Chapter 5, Section 5.4,
our AriHana template project starts with the Logistics module, as shown in Figure 6.22.

160 160
6.5 6 Project Setup
Deployment Landscape and Deployment Plan

Figure 6.22 AriHana Template Project Release 1

A better example is the AriHana rollout project shown in Figure 6.23.

Figure 6.23 Scope of the AriHana Rollout Project

Here you can see two scopes, one for the location in Dresden and the second for the
location in Madrid. If you select the Manage Scopes link, you will immediately jump
to the Manage Scopes app, where you can create or change scopes as described in
Chapter 7.

6.5 Deployment Landscape and Deployment Plan


In the last step of this project setup, we will show you how to integrate your managed
systems into the project context. To do this, you need to have defined the system
groups and the deployment plan. This is described in detail in Chapter 17.

161
161
6 Project Setup 6 Project Setup

In Figure 6.24, you can see that the system groups have also been assigned by selecting
the AriHana deployment plan. Further information on deployment plans can also be
found in Chapter 17.

Figure 6.24 Assign Deployment Landscape and Deployment Plan

6.6 Tag Management


In SAP Cloud ALM, you can use predelivered tags as well as custom tags. If you use tags
in your SAP Activate roadmap, they will be automatically assigned to template tasks in
your SAP Cloud ALM tenant. You can reuse these tasks, but you cannot rename, delete,
or unassign (from template tasks) them. The benefit of using these tags is for filtering
and grouping. But you can also think about using them for custom attributes in solu-
tion processes.

Tags Possibilities
Custom tags are currently available for tasks, sub-tasks, user stories, requirements,
solution processes, and test cases.

From our perspective, it is essential to think about tags from the very beginning of your
project. You will see many benefits during your project if you give clear guidance to
project team members. Two roles are available for tag management:
 Tag administrator: Create, update, merge, and centrally delete tags; view tag usage;
and organize tags into groups
 Tag viewer: Can view tags, tag groups, and tag usage

You should also think about naming conventions and when tags will be used for better
handling of all entities. It’s a good practice, for example, to use tags for a risk assess-
ment.

162 162
6.6 6 Management
Tag Project Setup

In our example, we have a roadmap task called Setup Project. Because it has a high risk
level, we can create a tag to reflect that by clicking in the empty Tags: line and selecting
the click here link, as shown in Figure 6.25. In the resulting popup window, we can enter
the new tag label “risk_high,” as shown in Figure 6.26.

Figure 6.25 Create New Tag

Figure 6.26 Create New Tag Label

If you need an overview about all tags and tag groups, you can use the Tag Management
app in the Administration area, as shown in Figure 6.27.
In the Tag Management app, you can see all tags as well as their creator and the source
of all tags. Our previously created tags were created by the end user, as shown in Figure
6.28.

163
163
6 Project Setup 6 Project Setup

Figure 6.27 Tag Management in Administration Area

Figure 6.28 Tag Management App: Tags

If you want to create tags that offer multiple tag values for a specific aspect, you should
use tag groups. Tag groups are optional, but if a tag belongs to a specific Tag Group, the

164 164
6.6 6 Management
Tag Project Setup

group’s title will be displayed before the individual tag label, e.g., Risk: Low, Risk:
Medium, and Risk: High, as shown in Figure 6.29.

Figure 6.29 Tag Management App: Tag Groups

Merge Custom Tags


You can also merge custom tags. If you merge two tags, the assignments of both tags
are combined, and the duplicated entry is deleted. Predelivered tags cannot be merged.

Tags can be used for searching, and not only for dedicated entities. You can use this
kind of search for many types of entities cross-project. You can use the search field in
header or many other applications to launch a search based on tags. You simply navi-
gate to the Home screen and click on the magnifier glass button . After that, you can
choose which entities you want to search for—in this case, Tags, as shown in Figure
6.30.

Figure 6.30 Search for Tags

Finally, you will find all related entities that are assigned to the corresponding tag. If
you follow our recommendation for naming conventions and abbreviations, you can
easily identify which type the results belong to. You can see an example in Figure 6.31.

165
165
6 Project Setup 6 Project Setup

The result list can be filtered via the filter button . Here, we have searched for “risk”
as the tag and afterward can easily filter for different risk level: low, medium, and high.
In the filter area you can also filter for object types (e.g., requirements, features, road-
maps tasks, solution processes, etc.) and projects as shown in Figure 6.32.

Figure 6.31 Search for “risk_high” Tags

Figure 6.32 Search for Tags: Filter

166 166
66.7
Project Setup
Summary

You can also directly jump into a search result if you click on the description of the rel-
evant entity. Another easy option is the share button . You can share this search via
email, but a more useful choice is the Save as Tile option. After selecting Save as Tile
you see a popup as shown in Figure 6.33. After saving your search as tile, you can easily
jump to your search once you’ve started SAP Cloud ALM.

Figure 6.33 Search for Tags: Save as Tile

Tags for Result Lists


By default, tags are not displayed in lists. But you can activate it via the Personalization
Settings button . After selecting tags and saving, tags will be displayed in the results
list. You will also be able to search for just part of a tag label, e.g., “risk” instead of “risk_
high.” If there are more than five tags assigned to a solution process, the first five
occurring alphabetically are shown in full, and any further tags can be viewed by
selecting the More link, where n shows the exact number of additional tags.

6.7 Summary
The project is the central bracket for all project activities within the requirement-to-
deploy approach. This is where all processes and their requirements are documented,
from creation and implementation through to the rollout of the developed functions.
In this chapter, we have used our example scenario to show you how to create a project

167
167
6 Project Setup 6 Project Setup

in SAP Cloud ALM for the hybrid scenario with the associated entities such as time-
boxes, teams, scopes, the deployment landscape, and the deployment plan. The project
is now technically prepared. In the following chapter, we will look at the content of the
solution to be implemented. We will present tools that can help determine the appro-
priate project scope from legacy SAP systems. After defining the scope or activating the
required solution scenarios, the associated SAP Best Practice processes are provided in
SAP Cloud ALM. The focus of this chapter is on the documentation of the target busi-
ness processes (solution processes).

168 168
Friedrich, Kindler, Kirsten, Kloppich,
List, Lorenz, Teuber

SAP Cloud ALM


Application Lifecycle Management

■ Manage on-premise and cloud appli-


cation lifecycles with SAP Cloud ALM
■ Walk through an SAP Cloud ALM
project, from planning and prepara-
tion to deployment and operations
■ See how SAP Cloud ALM supports
extensions and integration

www.sap-press.com/5897

We hope you have enjoyed this reading sample. You may


recommend or pass it on to others, but only in its entirety,
including all pages. This reading sample and all its parts
are protected by copyright law. All usage and exploitation
rights are reserved by the author and the publisher.

Matthias Friedrich, Fred Kindler, Marcel Kirsten, Daniel Kloppich, Mathias List,
Bert Lorenz, and Lars Teuber are a team of experts from NTT DATA Business
Solutions GBMS GmbH. Together they have decades of experience with SAP
solutions for application lifecycle management.

ISBN 978-1-4932-2595-8 • 676 pages • 06/2024


E-book: $84.99 • Print book: $89.95 • Bundle: $99.99

You might also like