Three basic models have established themselves in many projects resp. in the maintenance, after the project phase.
1. Feature-driven
A lean approach in which the feature is the central control element. This is particularly suitable for agile teams with a high implementation speed and low formal approval requirements. The status flow of the feature enables transparent implementation without unnecessary complexity.
2. Requirement-driven
This approach adds the requirement element to the feature level. It serves as a control instrument for approvals and can bundle multiple features. Particularly suitable for organizations with moderate compliance requirements or increasing complexity.
3. Fully integrated
A comprehensive variant in which SAP Cloud ALM is integrated into an existing ITSM tool. This creates a continuous process chain from incident to change management to deployment in production. This option is particularly useful for companies with complex IT landscapes and high governance requirements.
An overview of these models is shown in the following figure.
Organizations should choose the entry point that suits their current requirements. The scalability of SAP Cloud ALM makes it possible to start with simple structures and add more complex control elements and integrations step by step as needed.
For companies that are currently considering optimizing or introducing change management, the models described offer proven approaches that can be flexibly adapted to different conditions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 33 | |
| 28 | |
| 24 | |
| 13 | |
| 13 | |
| 12 | |
| 11 | |
| 10 | |
| 9 | |
| 8 |