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.
| Category | Description |
|---|---|
| People & Culture | Readiness is assumed, not tested. Teams operate with a reactive mindset. |
| Process & Governance | No formal readiness activities before releases. Reliance on hope and heroic recovery. |
| Technology & Tools | Minimal tooling support for pre-release validation. No structured rollout planning. |
| Measurement & Metrics | Readiness checks are not measured or tracked. Post-release incidents are common. |
| Category | Description |
|---|---|
| People & Culture | Some teams discuss readiness but lack shared definitions. |
| Process & Governance | Readiness checks (e.g., monitoring, rollback) are applied inconsistently. |
| Technology & Tools | Basic tools support some readiness tasks. Alerting and dashboards exist but are incomplete. |
| Measurement & Metrics | Teams may track readiness activities manually, but data is not analysed systematically. |
| Category | Description |
|---|---|
| People & Culture | Readiness is a standard expectation. Teams take pride in releasing stable, supportable features. |
| Process & Governance | Defined checklist covers monitoring, alerting, rollbacks, support handover, and system health. |
| Technology & Tools | Tooling supports structured readiness checks and documentation. |
| Measurement & Metrics | Readiness compliance is tracked pre-release and reviewed post-release. |
| Category | Description |
|---|---|
| People & Culture | Teams analyse readiness failures and refine pre-release practices. |
| Process & Governance | Readiness is a release gate for major changes. Automated checks validate key conditions. |
| Technology & Tools | Dashboards display readiness status by team and environment. |
| Measurement & Metrics | Metrics show the correlation between readiness and incident trends. Coverage is tracked over time. |
| Category | Description |
|---|---|
| People & Culture | Operational readiness is treated as a team learning tool. Scenarios are rehearsed to improve capability. |
| Process & Governance | Readiness is embedded in the Definition of Done. Practices evolve through post-incident and success reviews. |
| Technology & Tools | Simulations, chaos testing, and automated drills validate end-to-end readiness. |
| Measurement & Metrics | Readiness scores are benchmarked across teams and products. Failures trigger continuous improvement loops. |