Readiness dimensions

"Is the release ready?" is really six questions. Teams that only ask the testing question get surprised on go-live morning by a missing authorization, an unscheduled background job or a warehouse team that was never trained. Release readiness looks across every discipline that has to be ready at the same moment.

Business readinessUsers trained, roles assigned, procedures updated, communications sent, support model known

Data readinessMaster and open items migrated and reconciled; owners have signed the reconciliation

Operations readinessJobs scheduled, monitoring and alerting live, runbooks written, support team staffed

Security readinessBusiness roles tested, segregation-of-duties conflicts resolved or mitigated, emergency access ready

Test readinessPlanned tests executed, exit criteria met, defects within agreed thresholds

Build readinessScope complete, transports released and checked, configuration and code frozen

Six readiness dimensions, from the technical foundation up to the business.

The Sign-Off Table · thesignofftable.com/academy/sap-rel-302

Criteria, not opinions

Each dimension needs criteria that can be evidenced: a measure, a threshold and an owner. SAP's own onboarding guidance describes go-live acceptance criteria in the same spirit: an acceptable share of integration tests passed or UAT cases validated, a number of end users trained, no critical issues open, and validated master and transactional data. Contoso extends that list to all six dimensions.

Dimension	Criterion (Contoso Release 1)	Evidence	Owner
Build	All Release 1 features Ready for Production; no modifiable transports; transport checks clean	Cloud ALM feature list filtered by release	Luis
Test	Integration and UAT exit criteria met; no open very high or high defects	Test execution and defect analytics snapshot	Priya
Security	All business roles tested by key users; SoD conflicts resolved or mitigated with owner sign-off	Role test results; SoD report with mitigations	Security lead
Operations	Job schedule loaded and tested; monitoring alerts tested; hypercare rota published	Job test log; alert test; rota	Sam
Data	Migration reconciliations signed for finance, materials, customers and open items	Signed reconciliation reports	Dan and Maria
Business	95% of named end users trained; cutover communications sent; floor support in place	Training records; communication log	Grace

A readiness checklist with one measurable criterion per dimension.

Weighting the dimensions

Not all criteria are equal. Some are blocking: if they fail, the release does not go. Others are conditional: the release can go with a named workaround and a date. Decide which is which before the board meets. At Contoso, a failed finance reconciliation is blocking; 92% training completion instead of 95% is conditional, with catch-up sessions in hypercare week 1.

Low impact, hard to fix laterUsually conditional; record an owner and a date

High impact, hard to fix laterBlocking: for example unreconciled opening balances

Low impact, easy to fix laterConditional or simply noted: for example a report layout

High impact, easy to fix laterConditional with a strict date: for example catch-up training before first use

Classifying criteria as blocking or conditional before the board meets.

The Sign-Off Table · thesignofftable.com/academy/sap-rel-302

Track readiness early, not on the day

Readiness should be a trend, not a surprise. Contoso starts tracking all six dimensions eight weeks before go-live, with each owner updating their criterion weekly. A dimension that has been amber for three weeks running is discussed long before the board, when there is still time to add people or cut scope. By the time the board meets, the pre-read should contain no news.

T–8 weeksCriteria agreedOwners, thresholds and blocking or conditional status signed off by Grace
T–6 weeksFirst readiness reportEach dimension reported weekly with evidence links
T–4 weeksDress rehearsalCutover rehearsal tests build, data and operations criteria together
T–2 weeksPre-board reviewGaps escalated; scope changes decided
T–1 dayGo/no-go boardFinal decision on frozen evidence

Readiness reporting builds up over weeks, so the board decides rather than discovers.

The Sign-Off Table · thesignofftable.com/academy/sap-rel-302

On SAP S/4HANA Cloud Public Edition, part of the operations dimension shifts to SAP, which runs the system and its upgrades, but the customer still owns business roles, job scheduling choices, monitoring of its own interfaces and the support model. Do not drop the dimension; narrow it to what you control.

What would you do?

Two weeks before go-live, Priya reports that every test exit criterion is met. Grace wants to declare the release ready. What should Luis point out?

Key points

Readiness spans build, test, security, operations, data and business.
Each criterion needs a measure, a threshold, evidence and an owner.
Classify criteria as blocking or conditional before the board meets.
Use the same dimensions, scaled down, for every release, not only go-live.

Criteria, not opinions

Weighting the dimensions

Track readiness early, not on the day

Lesson check