Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

Gates and evidence

9 min

Listen to this lesson

0:00 / 7:32

A quality gate is a planned checkpoint where a project stops and asks: is the work good enough to move to the next phase? SAP Activate builds quality gates into its phases (Prepare, Explore, Realize, Deploy) and SAP's Cloud ALM guidance recommends at least one gate per phase, held at the end of that phase. Gates fail when they become a slide-review ritual. They work when every question has an answer you can show.

SAP Cloud ALM holds most of that evidence already: scope and solution processes, requirements, user stories, test cases and test runs, defects, features and deployments. In Cloud ALM, a gate itself is managed as a task of type Quality Gate with a checklist of items to review and approve, and gates appear on the project overview and on the project timeline. This course connects the two: gate questions on one side, Cloud ALM data on the other.

  1. End of PrepareProject ready to startPlan, team, tools and standards in place; Cloud ALM project set up.
  2. End of ExploreDesign completeScope confirmed, requirements and gaps documented and approved.
  3. Mid RealizeReady for integration testBuild complete, unit tests passed, test cases prepared and linked.
  4. End of RealizeReady for UAT and cutover rehearsalIntegration test exit criteria met, defects within thresholds.
  5. DeployGo-live readinessUAT accepted, cutover proven, production readiness confirmed.
Typical gate points for Contoso Motor Co.'s S/4HANA program. Your project may add or merge gates.
The Sign-Off Table · thesignofftable.com/academy/sap-alm-303

From vague questions to answerable ones

"Is testing on track?" cannot be answered from data. "Have all in-scope requirements for order to cash at least one linked test case that has been executed, with no open priority 1 defects?" can. A good gate question names the scope, the measure, the threshold and the source.

  1. ScopeOrder to cash, in-scope requirements for scope Contoso US
  2. MeasureRequirements with at least one linked, executed test case
  3. Threshold100%, with no open priority 1 defects
  4. SourceRequirement traceability analytics, dated snapshot
  5. OwnerPriya, the test lead, presents and states met or not met
The five parts that turn a vague gate question into one the data can answer.
The Sign-Off Table · thesignofftable.com/academy/sap-alm-303
Gate questionCloud ALM sourceThreshold (Contoso)Owner
Are all in-scope requirements approved?Requirements app, filtered by scope and status100% approved or explicitly deferredProcess owners
Does every requirement have a linked test case?Requirement traceability analytics100% for critical processes; 95% overallTest lead
Has every planned test run been executed?Test execution analytics for the cycle's test plan100% executed; 95% passedTest lead
Are open defects within tolerance?Defect list and defect analytics by priority and scopeNo open very high or high; medium with workaroundTriage lead
Is the cutover plan rehearsed?Tasks app, cutover tasks and rehearsal resultsDress rehearsal complete within windowCutover manager

Turning gate questions into measures with a source, a threshold and an owner.

Evidence the gate can rely on

Cloud ALM analytics are live. The number you see on Tuesday may differ on Thursday when the gate meets. For a gate, you need a snapshot: the figure, the filter that produced it, the date and time, and who took it. Record that alongside the checklist item, and use the live view in the meeting only to answer follow-up questions.

Who does what at a gate

Three roles keep a gate honest. The gate owner (usually the PMO lead, Grace at Contoso) schedules the gate, owns the checklist and chairs the review. Item owners (the test lead, process owners, the cutover manager, the data lead) prepare the evidence for their checklist items and state whether each is met. Decision makers (the accountable process owners such as Dan for finance, plus the program sponsor or steering committee) judge the residual risk and decide. Name all three in the gate task before the phase starts. When the same person prepares the evidence and decides on it, say so openly and add a second reviewer for critical items.

Decision makersAccountable process owners such as Dan, plus the sponsor or steering committee: judge residual risk and decide
Gate ownerGrace, the PMO lead: schedules the gate, owns the checklist, chairs the review
Item ownersTest lead, process owners, cutover manager, data lead: prepare evidence and state whether each item is met
EvidenceDated snapshots of Cloud ALM data: figure, filter, date and time, author
Who does what at a quality gate, from the evidence up to the decision.
The Sign-Off Table · thesignofftable.com/academy/sap-alm-303

What would you do?

Grace, Contoso's PMO lead, drafts the end-of-Realize gate checklist. One item reads "Testing substantially complete." What should Priya suggest?

Key points
  • A quality gate is a planned checkpoint; SAP recommends at least one per Activate phase.
  • In Cloud ALM a gate is a Quality Gate task with a checklist, visible on the project overview and timeline.
  • Each gate question names scope, measure, threshold, source and owner.
  • Gates use dated snapshots of Cloud ALM data, not whatever the live view shows on the day.

Check your understanding · not graded

Lesson check

  1. 1. How is a quality gate represented in SAP Cloud ALM?

  2. 2. Which gate question is answerable from Cloud ALM data?

  3. 3. Why take a dated snapshot of analytics for the gate?

  4. 4. When should the checklist for an end-of-phase gate be written?