Lesson 3 of 7
Gates
10 min
Listen to this lesson
A gate is a planned decision point where the program stops, checks evidence against agreed criteria, and decides to proceed, proceed with conditions, or stop. Gates turn sign-off from a single go-live event into a series of smaller, earlier decisions. A good framework has gates for the implementation phases, extra gates for a conversion, and lightweight gates for every release after go-live.
Gates across SAP Activate
SAP Activate organizes a program into phases: Discover, Prepare, Explore, Realize, Deploy and Run. SAP Learning's description of a conversion project in SAP Cloud ALM shows the project created from a roadmap template with phases, sprints, milestones and quality gates, with go-live as the key milestone. Use those quality gates as the backbone, and attach your sign-off criteria to them. The idea is not SAP-specific: the UK government's gate review process, for example, gives major programs independent assurance at fixed decision points such as the investment decision, as a snapshot that complements internal assurance rather than replacing it.
- End of PrepareQ-gate: ready to exploreScope, test strategy, evidence standard and decision rights approved
- End of ExploreQ-gate: design acceptedFit-to-standard results and requirements accepted by process owners; test scope derived
- End of RealizeQ-gate: solution acceptedIntegration tests and UAT accepted; data migration rehearsed; open risks accepted or blocking
- DeployGo/no-goCutover rehearsed; financial data acceptance; all accountable owners' decisions in
- RunHypercare exitStability, first period-end close, incidents within thresholds; handover to support
Extra gates for a conversion
A system conversion adds technical rehearsals that each need an exit decision. Contoso's conversion has two mock conversions and a dress rehearsal before the production weekend. Each one is a gate with its own criteria, and each one also rehearses the business acceptances that will be needed on the real weekend.
| Gate | Entry criteria | Exit criteria |
|---|---|---|
| Mock 1 exit | Readiness Check findings dispositioned; custom code adapted in CMD; mock plan approved | Conversion runs end to end; runtimes measured; finance reconciliation attempted; issues logged with owners |
| Mock 2 exit | Mock 1 issues fixed; regression pack ready | Runtime within the 60-hour window with buffer; reconciliation passes or exceptions owned; regression pack passed |
| Dress rehearsal exit | Final transports frozen; cutover plan approved | Full cutover run to the minute; all acceptances signed as if real; fallback rehearsed |
| Go/no-go | Dress rehearsal exit passed; business readiness confirmed | Every accountable owner has accepted or a formal risk acceptance exists; steering decides |
Conversion gates at Contoso. Entry criteria stop a rehearsal starting unprepared; exit criteria stop it ending unproven.
Gates for every release
After go-live, the system keeps changing: transports every week, SAP Feature Pack Stacks and release upgrades for Private Edition on the schedule you agree with SAP, and new waves such as Alternadores del Norte. Each change needs sign-off, but not a full program gate. Design a release gate that scales with the size of the change.
- Does the change touch financial postings, legal or control requirements?Yes → full release gate: impact assessment, regression pack, finance sign-off · No → next question
- Does it change an integration or a critical process?Yes → standard release gate: targeted tests plus regression of affected processes · No → next question
- Is it an SAP upgrade or Feature Pack Stack?Yes → upgrade gate: regression pack, impact on custom code and APIs, process owner sign-off · No → next question
- Is it a minor fix in one process?Yes → light gate: test evidence and key user confirmation · No → treat as standard
Aligning criteria across tracks
Every track tends to invent its own gate language: "functionally complete", "data green", "interfaces stable". Align them with a common structure. Each track states, for each gate, its entry criteria, exit criteria, the evidence that proves exit, and the accountable owner. Then the gate review reads one table, not seven slide decks.
What would you do?
Mock 2 finishes with a conversion runtime of 58 hours against a 60-hour window, and the finance reconciliation for 1810 still has an unexplained difference. Grace must decide the mock 2 exit gate. What is the best decision?
- Gates are decision points with entry criteria, exit criteria, evidence and an accountable owner.
- Map sign-off gates to SAP Activate quality gates; add conversion gates for each mock and the dress rehearsal.
- Size release gates to the change: full, standard, upgrade or light.
- A gate must be able to stop the program; conditions become entry criteria for the next gate.
Check your understanding · not graded
Lesson check
1. What does an entry criterion prevent?
2. Which gate should require all acceptances to be signed as if real?
3. A release changes how freight costs post to the G/L. Which gate size fits?
4. When is go/no-go 1 on Contoso's cutover weekend, and what does it check?