- SAP Managed Tags:
In this blog post, I would like to give you a walkthrough of how can you use SAP Cloud ALM to manage Projects in an agile way
You don't need to use Agile methodology if it does not serve your purpose. I have another detailed blog post on this - Why agile or why not
Methodologies and tools are created to help you and not hurt you. If you use the wrong combination of tools and methodologies you will not get the benefit
But you need to know that SAP Cloud ALM has been designed to help you transition to an agile way of working. As an, if only one of the teams wants to use user stories, it will work without impacting other teams. If some teams want to use story points and some do not .. that's also ok.
Another powerful thing is you can decide to enter this agile way of thinking irrespective of where you are in your Project. You can create and close sprints in a running project without any risk.
Some of the steps mentioned are explained in detail below
You can create sprints in the Project setup in the Timeboxes tab
Please note that the dates of the sprints align with the timeline of Realize phase
You can create small-sized teams and later assign user stories to them
you may want to create custom roles Scrum Master, Product Owner, and Developer
You can easily mass upload user stories using the Excel template
as an example, this is what I used for my test data
Then once you upload then your Task list will look like this
please note that the phase is shown as a sub-header. The system already detects that sprint 1 and sprint 2 are aligned to Realize phase
You can select multiple items and perform mass edit to assign user stories to sprint.
please note to manage Backlog, you should assign user stories to teams and assign phase instead of sprints if items are still being refined and timelines are not clear.
You will need to adjust your filters and columns and your view should look like this. You can Group task list by Timebox using the Group by option
please note that your backlog is shown at the top assigned to the phase.
Story point usage is not mandatory but recommended. It helps you perform relative sizing quickly. You can assign story points easily from Tasklist itself
As you proceed in the sprint, you can set the user story to completion
Multiple reports are optimized for sprint usage
you can use the Burnup chart
or use the Sprint Tab in Project Progress Reporting
Hope you enjoyed this post. Please visit the Master Blog post and bookmark it.
To understand an end to end picture, please visit
Expert Portal for Implementation and stay connected
Why use Agile?
You don't need to use Agile methodology if it does not serve your purpose. I have another detailed blog post on this - Why agile or why not
Methodologies and tools are created to help you and not hurt you. If you use the wrong combination of tools and methodologies you will not get the benefit
But you need to know that SAP Cloud ALM has been designed to help you transition to an agile way of working. As an, if only one of the teams wants to use user stories, it will work without impacting other teams. If some teams want to use story points and some do not .. that's also ok.
Another powerful thing is you can decide to enter this agile way of thinking irrespective of where you are in your Project. You can create and close sprints in a running project without any risk.
Steps to create a Project using Agile methodology
- Create a Project
- Create a Sprint schedule aligned to Project phases
- Create custom roles
- Create teams
- Collect Requirements as Product Backlog
- Break Requirements into user stories
- Assign story points to user stories
- Measure sprint progress
- Repeat the process
Some of the steps mentioned are explained in detail below
How to create sprints aligned to Phases
You can create sprints in the Project setup in the Timeboxes tab
Please note that the dates of the sprints align with the timeline of Realize phase
Create Teams
You can create small-sized teams and later assign user stories to them
you may want to create custom roles Scrum Master, Product Owner, and Developer
Mass upload user stories
You can easily mass upload user stories using the Excel template
as an example, this is what I used for my test data
Then once you upload then your Task list will look like this
please note that the phase is shown as a sub-header. The system already detects that sprint 1 and sprint 2 are aligned to Realize phase
Mass assign user stories to teams
You can select multiple items and perform mass edit to assign user stories to sprint.
please note to manage Backlog, you should assign user stories to teams and assign phase instead of sprints if items are still being refined and timelines are not clear.
Customize Task list for Agile
You will need to adjust your filters and columns and your view should look like this. You can Group task list by Timebox using the Group by option
please note that your backlog is shown at the top assigned to the phase.
Assign story points
Story point usage is not mandatory but recommended. It helps you perform relative sizing quickly. You can assign story points easily from Tasklist itself
Set user story status
As you proceed in the sprint, you can set the user story to completion
Use Reports
Multiple reports are optimized for sprint usage
you can use the Burnup chart
or use the Sprint Tab in Project Progress Reporting
Next Steps
Hope you enjoyed this post. Please visit the Master Blog post and bookmark it.
To understand an end to end picture, please visit
Expert Portal for Implementation and stay connected
