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

Lesson 2 of 5

Release boards

9 min

A release board (often called a change advisory board, or a go/no-go meeting for a major go-live) exists to make one decision with the right people in the room, on the right evidence. It fails in two familiar ways: as a status theater where everyone reports green and nobody decides, or as a design meeting where the release is rebuilt on the day.

Who sits on the board

RoleAt ContosoResponsibility at the board
ChairGrace, PMO leadRuns the agenda, keeps to evidence, calls the decision
Decision makersProcess owners such as Dan (finance) and Maria for order to cash, plus the program sponsorAccept or reject residual risk for their processes
PresentersLuis (release), Priya (test), Sam (operations), security lead, data leadState each criterion as met, not met or conditional, with evidence
RecorderPMO analystCaptures decisions, conditions, owners and dates

Board roles. Presenters inform; decision makers decide.

Agree a quorum. A board that decides without the finance owner present cannot accept finance risk, however senior the people in the room. If a decision maker cannot attend, their named delegate attends with the authority in writing; otherwise the decisions for that process wait.

Keep the difference between presenters and decision makers sharp. Priya can tell the board that two high-priority defects are open; she should not be the one who decides they are acceptable. That is Dan's or Maria's call, because they own the business consequence.

Before, during and after

  1. T–5 daysCriteria status collectedEach owner updates their criterion with evidence
  2. T–2 daysPre-read circulatedOne page per dimension, dated snapshots, open risks
  3. T–1 dayQuestions answeredDecision makers raise questions in writing; owners respond
  4. BoardDecisionExceptions only; decide go, go with conditions, or no-go
  5. T+1 hourDecision record publishedConditions with owners and dates; communication to the program
A release board cycle. The meeting itself handles only exceptions.
The Sign-Off Table · thesignofftable.com/academy/sap-rel-302

An agenda that decides

  1. Confirm the decision being made and who makes it.
  2. Walk the blocking criteria: met or not met. Any not met means no-go unless the board changes the criterion, on record.
  3. Walk conditional criteria that are not met: workaround, owner, date.
  4. Review residual risks with their owners; decision makers accept or reject each.
  5. Call the decision; read back conditions and owners.
  1. Are all blocking criteria met?Yes → continue · No → no-go, with a re-decision date
  2. Is every unmet conditional criterion covered by a workaround, owner and date?Yes → continue · No → resolve or no-go
  3. Have decision makers accepted every residual risk for their processes?Yes → go, or go with conditions · No → no-go or reduce scope
The decision logic the chair follows.
The Sign-Off Table · thesignofftable.com/academy/sap-rel-302

Go-live board versus routine change board

After go-live, the big go/no-go board gives way to a routine change board for regular releases and urgent changes. Same principles, lighter format. Contoso's weekly change board takes 30 minutes: Luis presents the features proposed for the next release with their test status, the board looks only at items that fail a criterion or carry a risk, and process owners decide. Urgent changes between meetings are approved by Luis and the process owner and reported at the next board.

AspectGo-live boardRoutine change board
FrequencyOnce per major release, plus re-decisionsWeekly or per release
ScopeAll six readiness dimensionsFeatures in the next release and their risks
Decision makersProcess owners and sponsorProcess owners for affected processes; Luis for technical items
EvidenceFull snapshot pack for every dimensionFeature list with test status, transport checks and open risks
OutputDecision record with conditionsApproved feature list; minutes with accepted risks

The same governance at two scales.

What would you do?

During the go/no-go board, Sam reports that the job schedule was loaded but the month-end jobs have not been tested in CMQ. The sponsor says "We'll test them in production." What should Grace do?

Key points
  • A release board makes one decision; presenters inform and decision makers decide.
  • Circulate dated evidence 24–48 hours before and handle only exceptions in the meeting.
  • Blocking criteria not met means no-go unless the board changes the criterion on record.
  • Ask for the weakest item in each dimension to avoid status theater.

Check your understanding · not graded

Lesson check

  1. 1. Who should accept a residual risk affecting order to cash?

  2. 2. When should the pre-read be circulated?

  3. 3. A blocking criterion is not met. What is the default outcome?

  4. 4. What is a sign of a status-theater board?