Lesson 3 of 5
Quality gates
8 min
Listen to this lesson
A quality gate (often written Q-gate) is a checkpoint where the project confirms that the deliverables of a phase are complete and acceptable before it moves on. In SAP Activate, stakeholders and sponsors sign off at each gate. The gate is not a meeting for its own sake; it is the moment the program decides, on evidence, whether it is ready for the next phase.
Where the gates sit
- End of PrepareProject set up, governed and staffed; tools and systems ready
- End of ExploreFit-to-Standard done; requirements and design approved; test strategy agreed
- End of RealizeSolution built; integration and acceptance testing complete; ready to deploy
- During and end of DeployCutover and production readiness confirmed; go-live decision; hypercare exit
There is no gate after Discover, because Discover happens before the project. Some roadmaps add gates within a phase, for example a go-live readiness check inside Deploy. Your roadmap and your project's governance define the exact set.
What a gate checks
Each gate has a checklist of deliverables and questions. SAP periodically refreshes its quality gate content. Typical items include:
- Are the phase's key deliverables complete and accepted by their owners?
- Are open risks and issues known, with owners and mitigation?
- Is the next phase planned and staffed?
- For testing: are entry or exit criteria for the relevant test levels met, with evidence?
- Has the business formally accepted what it needs to accept, such as the solution design or test results?
Quality gates in SAP Cloud ALM
In SAP Cloud ALM, quality gates are part of the project. They can be predefined from SAP Activate content or created from your own templates, and each gate holds a checklist the team works through and records. Putting test entry and exit criteria into the gate checklists means every gate review asks the same testing questions, and the answers are stored with the project.
| Gate | Testing question for Contoso | Evidence |
|---|---|---|
| Explore | Is the test strategy approved, and is every scoped process covered by planned test cases? | Approved strategy; coverage view in Cloud ALM |
| Realize | Did SIT and UAT meet exit criteria, with no open critical defects? | Test execution analysis; defect report; UAT sign-off |
| Deploy | Did the dress rehearsals pass, and is production verified after cutover? | Rehearsal results; cutover checklist; post-go-live checks |
Testing questions at Contoso's gates.
- Are all key deliverables complete and accepted by their owners?Yes → go on · No → can the gaps be closed by named actions soon?
- Can every gap be closed by a specific action with an owner and a date?Yes → pass with conditions, tracked in the gate · No → fail
- Are the risks of moving on known and accepted by the sponsor?Yes → pass, or pass with conditions · No → fail and re-plan the gate
Running a good gate review
A gate review works best when the evidence is gathered before the meeting, not presented for the first time in it. A week before Contoso's Explore gate, Grace sends each workstream lead the checklist and asks for the status of every item with a link to the evidence. The meeting itself then spends its time on the items that are not green, and on the decision. Keep the attendee list to the people who decide and the people who can answer questions; a gate with forty observers turns into a status meeting.
- One week beforeChecklist sentGrace sends each workstream lead the gate checklist and asks for status with evidence links
- Three days beforeEvidence gatheredLeads mark each item and attach or link the evidence in Cloud ALM
- Gate meetingDiscuss only the exceptionsDeciders review items that are not green, then take the decision
- Same dayDecision recordedOutcome, conditions with owners and dates, and evidence stored in the quality gate
- Until closedConditions trackedEach condition is followed up until it is closed or escalated
Record the decision, the conditions and the evidence in one place, ideally the quality gate in Cloud ALM. Six months later, when someone asks why the program moved into Deploy with an open finance issue, the answer should take a minute to find.
Gates and agility
Some teams see gates as a contradiction of agile delivery. In Activate they are complementary. Sprints inside Realize deliver and test scope incrementally; the gate at the end of Realize confirms that the sum of the sprints is ready to deploy. Without the gate, nobody owns the decision that the whole is ready.
What would you do?
At Contoso's Realize gate, SIT is complete but UAT for finance is only 70% executed. Dan, the finance process owner, is asked to accept. What is the most responsible outcome?
- Quality gates confirm a phase's deliverables are complete and accepted before moving on.
- Gates typically sit at the ends of Prepare, Explore, Realize and within or at the end of Deploy; none after Discover.
- Cloud ALM holds quality gates with checklists; put test entry and exit criteria into them.
- Gate outcomes are pass, pass with specific tracked conditions, or fail.
Check your understanding · not graded
Lesson check
1. What is the purpose of an Activate quality gate?
2. Why is there no quality gate after Discover?
3. Where can quality gate checklists be managed in SAP tooling?
4. What makes a "pass with conditions" acceptable?