SAP Solution Manager 7.2 · Quality Gate Management (QGM)

How are milestones technically realized in QGM, and who oversees them?

As Quality Gates (Q-Gates), overseen by a quality manager + quality advisory board who plan/approve changes at each lifecycle phase — ensuring changes reaching PRD meet quality standards.

QGM in 7.2 is more flexible with ChaRM-like technical capabilities; transport analytics shows what changed, which systems are affected, and who approved.

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 Quality Gate Management (QGM)

For QAS to receive changes from DEV in QGM, what must happen at the Q-Gate, and how does that differ from a milestone?
What does the QGM task list handle, and how does it differ from ChaRM's task list?
What are QGM's four standard roles, and what's the benefit of splitting them this way?
What is the quality management process in QGM, and what should you do if building change management from scratch?
Which standard does QGM follow, and what options exist for how transports move?
Why does using ToCs mean only one transport ever reaches production, no matter how many test rejections?