Basics of Deployment and Release Management in SAP Cloud ALM
In this blog post, we would understand
What is a Deployment Plan
What is a Release
How to make use of Deployment Plans and Releases
What is a Deployment Plan
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 a Deployment Plan is required. The Deployment Plan can be thought of like a train and each Project can be thought of as a compartment in that train. One Deployment Plan can serve multiple Projects but one Project can only have a maximum of one Deployment Plan. The assignment of Deployment Plan to a Project is optional.
What are Releases?
A train has always a schedule of stops along the way. They are called Releases. A Release can exist only within a unique Deployment Plan and has a date range. As an example look at the screenshot below
How to use Deployment Plans
Step 1: Create a Deployment Plan
Step 2: Create Releases
Step 3: Assign Deployment Plan to Project
Step 4: Assign Requirement to Releases
Note that since only one Deployment Plan can be assigned to Project, The Requirement has only the Release assignment and does not need Deployment Plan assignment
How to see Release and sprint schedule together
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.
Thanks for the blog above. Could you please tell me what the relation between release and Project Phases are. my understanding is that a release lives between Explore and Deploy.
Lets take the following case :
Imagine that you have 1 Customer Project that will deliver 3 waves (1,2,3).
Lets assume that for the overall project you would have 1 x Discover Phase , 1 x Prepare, Explore Phase per wave , Realize Phase per wave , Deploy Phase per wave, Run Phase per wave.
From and ALM perspective it seems to me that i would build 3 projects in ALM and in each project define a single release and link all releases to 1 Deployment Plan.
Do you agree with this or would you recommend a single project with 3 releases and 1 Deployment plan? Considering that if you have a single project all the methodology tasks available in the default Phases will be completed in the first wave and custom phases for later waves will not have any of the pre-delivered project tasks.
Thanks in advance