This standard ensures operational readiness is tested before every major release-covering monitoring, alerting, rollback plans, and support handovers. It builds confidence that systems can perform reliably under real conditions.
Aligned to our "Resilience Over Uptime" policy, this standard reduces post-release surprises and enables safer, faster delivery. Without it, releases carry hidden risks that impact users, teams, and operational stability.
Level 1 – Initial: Operational readiness is unstructured or overlooked. Testing is ad hoc, with limited checks before release. Issues are often discovered in production.
Level 2 – Managed: Some teams conduct readiness checks (e.g., monitoring, alerting), but scope and rigour vary. Handover and rollback plans are inconsistent.
Level 3 – Defined: Readiness criteria are standardised and documented. All major releases include checks for monitoring, alerting, rollbacks, support readiness, and system health.
Level 4 – Quantitatively Managed: Readiness assessments are automated and auditable. Compliance is tracked and informs post-release reviews. Gaps are addressed before release is approved.
Level 5 – Optimising: Readiness practices continuously evolve through feedback and incident learnings. Teams rehearse operational scenarios and embed readiness as part of their definition of done, driving improved resilience and confidence.