Basics of Release Management in SAP Cloud ALM

In this blog post, we would understand

What is a Release

What is a Release Version

How to make use of Releases

We know Project is an endeavor to perform work in a given amount of time. Each Project lead wants to define the timelines based on the Project plan. But how do you facilitate coordination across multiple projects from a timeline perspective.  This is where Release is required. The release can be thought of like a train and each Project can be thought of as a compartment in that train. One Release can serve multiple Projects but one Project can only have a maximum of one Release. The assignment of Release to a Project is optional.

A train has always a schedule of stops along the way. They are called Release versions. A Release version can exist only within a unique Release and has a date range. As an example look at the screenshot below

  • Step 1: Create a Release

  • Step 2: Create Release Versions

  • Step 3: Assign Release to Project

  • Step 4: Assign Requirement to Release Versions

Note that since only one Release can be assigned to Project, The Requirement has only the Release version assignment.

Gantt chart allows you to see Release and Project timeboxes together

Hope you found this post. Make sure you bookmark the Master Blog post for SAP Cloud ALM for implementation. You can also visit Expert Portal.