SAP Solution Manager 7.2 · Release Management

What are the phases of a release cycle (SMRE)?

  • Created — technical start.
  • Scope — review IT requirements (experts define, business approves, requirements manager handles, solution architect hands to build).
  • Build — implement approved scope + unit test (some scope can be deferred to the next release).
  • Test — acceptance/regression/integration; errors → defect correction.
  • Deploy — technical cutover; admin triggers; SolMan centrally imports all released changes to all production systems in sequence.
  • Hypercare — post-go-live high-incident window, intense monitoring.
  • Operate — handed to the operations team.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Release Management

What are the three setup steps of Release Management, and which two dates matter most?
How does Release Management's predecessor/successor philosophy gate deployment?
What does the system check before letting you delete a release, and what's the ordering rule for minor releases?
How does a major release differ from a minor release in Release Management?
How does Release Management differ from ChaRM on the trade-off between dates versus scope?
What does Release Management add to the change-control framework, and who is it for?