SAP Solution Manager 7.2 · Quality Gate Management (QGM)

What are QGM's four standard roles, and what's the benefit of splitting them this way?

  • Development lead — creates + releases transports.
  • IT operator — triggers imports to QAS/PRD.
  • Quality manager — quality checks at each Q-Gate/milestone, supports board approvals.
  • Quality advisory board — manages risk, defines + oversees quality standards.

Benefits: almost no impact on developers/config, small training footprint, easy rollout, and separation of duties across approval roles.

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)

How are milestones technically realized in QGM, and who oversees them?
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 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?