Lesson 4 of 6
Quality gates in SAP Activate
8 min
Listen to this lesson
SAP Activate, SAP's implementation methodology, divides a project into six phases: Discover, Prepare, Explore, Realize, Deploy and Run. SAP Learning describes formal quality gates after each project phase that check that the relevant deliverables for the phase are available before the project moves on. Test sign-off is one of the main inputs to those gates, especially at the end of Realize.
- PrepareProject set upPlans, team, governance, test strategy approach. Gate: is the project ready to explore?
- ExploreFit-to-StandardProcesses validated, gaps in backlog, test strategy refined. Gate: is scope confirmed?
- RealizeBuild and testConfiguration, extensions, integration and acceptance testing, data migration loads. Gate: is the solution accepted for deployment?
- DeployReady for go-liveCutover rehearsals, end-user training, production setup. Gate: go or no-go
- RunOperate and improveHypercare, stabilization, regression testing for changes. Gate: stable operation and handover
What a quality gate is
A quality gate is a checkpoint at which key deliverables and milestones are reviewed and approved before the project proceeds. SAP Learning describes gates as checkpoints that confirm specific criteria are met, and notes that stakeholders and sponsors accept each gate as the official approval to move on. The gate checklists come from the SAP Activate roadmaps (browsable in the SAP Activate Roadmap Viewer), and SAP has periodically refreshed the gate questions.
Gates are run jointly. SAP's guidance describes gate execution as a collaborative milestone between the partner and customer project teams, led by their project managers. In SAP Cloud ALM, the quality gate checklists can be completed and submitted, and SAP uses submitted gates as input to its Continuous Quality Check reviews on supported engagements. Whether your project uses those services depends on its contract; the gate discipline applies either way.
- Take the checklistGate questions from the SAP Activate roadmap for your product and deployment
- Attach evidenceEach yes points to a deliverable, such as a signed test phase or a migration report
- Joint reviewPartner and customer project managers walk through the answers together
- Sponsor decisionStakeholders accept the gate as official approval to move on
- OutcomePass, pass with recorded conditions, or hold the phase
Gate content differs by product. Roadmaps for SAP S/4HANA Cloud Public Edition, for private edition and for on-premise conversions each have their own deliverables and questions, and a conversion such as Contoso's adds items such as custom code adaptation and technical conversion rehearsals. Check the roadmap that matches your program rather than reusing a checklist from a previous project.
How test sign-off feeds the gates
Test phase sign-offs are evidence for the gates. The Realize gate, in particular, asks whether the solution has been tested and accepted: integration testing complete against exit criteria, user acceptance signed by the business, data migration tested, and open issues understood. If test phase sign-offs are weak, the gate is weak, and the project enters Deploy carrying risk nobody has looked at.
Gates earlier in the project matter for testing too. The Explore gate is the right time to confirm that a test strategy exists, that test scope follows the Fit-to-Standard decisions, and that the test environment and data plan are realistic. Problems found there cost a planning conversation. The same problems found at the Realize gate cost a delayed go-live.
| Realize-to-Deploy gate item (example) | Evidence from testing | Contoso owner |
|---|---|---|
| Integration testing complete | Integration test summary against exit criteria, signed | Priya, with functional leads |
| User acceptance signed | UAT sign-off by process owners, with conditions listed | Dan (finance), Maria's process owner (order to cash) |
| Data migration validated | Mock load reconciliation and test results on migrated data | Data migration lead, with Dan for balances |
| Non-functional tests complete | Performance and authorization test results | Technical lead; security lead |
| Open defects and risks managed | Defect list by severity with workarounds; risk acceptance records | Priya; Grace for the risk log |
| Cutover plan ready | Rehearsal results, timings, issues closed | Luis |
An illustrative Realize-to-Deploy gate checklist with its test evidence. Use the checklist from your project's SAP Activate roadmap.
- Does every yes on the checklist point to evidence?Yes → continue · No → collect the evidence or answer no
- Are all test phase sign-offs in place?Yes → continue · No → can the missing area be a condition with an owner and date?
- Is any open critical defect in a process going live?No → pass the gate · Yes → hold, or pass with explicit conditions the sponsor accepts
What would you do?
Contoso's Realize-to-Deploy gate is next week. UAT for order to cash is signed, but finance UAT is still running with two critical defects in period-end close. Grace asks whether the gate can pass on schedule. What should Priya advise?
- SAP Activate phases: Discover, Prepare, Explore, Realize, Deploy, Run.
- A quality gate after each phase checks that the phase's deliverables exist and are accepted.
- Gates are run jointly by partner and customer, led by project managers; sponsors and stakeholders accept them.
- Test phase sign-offs are key evidence, especially at the Realize-to-Deploy gate.
- A gate must be able to say no, or to pass with explicit conditions.
Check your understanding · not graded
Lesson check
1. Where does SAP Activate place quality gates?
2. Which phase follows Realize in SAP Activate?
3. Who leads quality gate execution according to SAP's guidance?
4. Which test evidence is most central to the Realize-to-Deploy gate?