Features, Deployment Plans and Release Orchestration in SAP Cloud ALM

Keep this: job aid

Cloud ALM feature and deployment card

• Feature = deployable unit; create it from the requirement; size it to pass or fail on its own.
• Statuses: In Specification → In Implementation → In Testing → Successfully Tested → Ready for Production → Deployed.
• No new transports after Successfully Tested; production deploy only from Ready for Production.
• CTS for private cloud and on-premise ABAP, ATO for public cloud, cTMS for BTP and Integration Suite.
• One transport, one feature. Check Feature Traceability for released, in QAS, in production.
• Deployment plan = system groups + releases; assign it to the project before assigning releases.
• Before Ready for Production: tests passed with evidence, defects closed or accepted, transport checks clean, ATC clean.
• Go-live: mass Deploy to Production for the release; late features move to the next release.
• ChaRM change document → feature; cycle → deployment plan; urgency → priority, tags, release.