Professional Documents
Culture Documents
2595 Reading Sample
2595 Reading Sample
2595 Reading Sample
Preface ....................................................................................................................................................... 19
Part I Prepare
7
Contents Contents
8 8
Contents
9
Contents Contents
10 10
Contents
Part II Explore
11
11
Contents Contents
13.2 From the Requirements Backlog to the Product Backlog .................................... 328
12 12
Contents
13
13
Contents Contents
Part IV Deploy
14 14
Contents
Part V Operate
15
15
Contents Contents
19 Implementation 499
16 16
Contents
17
17
Contents Contents
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
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
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.
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.
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.
145
145
6 Project Setup 6 Project Setup
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).
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.
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.
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.
150 150
6 Project
6.2 Setup
Timeboxes
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.
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.
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
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
In Figure 6.15, you can see how it looks in the system for our quality gate for the explore
phase.
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
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.
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
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
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.
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.
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
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.
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.
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.
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
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.
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.
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.
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.
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
www.sap-press.com/5897
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.