This standard ensures build, test, and deploy processes are fully automated and consistently applied. By removing manual steps, teams gain speed, reduce errors, and create more stable, reliable releases.
It supports our policy to "Automate everything possible" and drives a delivery culture focused on flow, repeatability, and quality at scale. Without this standard, teams risk slow, error-prone deployments, reduced confidence, and mounting technical debt.
Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.
| Category | Description |
|---|---|
| People & Culture | - Build, test, and deploy steps are manual and error-prone. - Teams lack awareness of automation benefits. |
| Process & Governance | - No formal processes for automation. - Builds and deployments vary widely by team or project. |
| Technology & Tools | - Manual scripts or manual steps dominate pipelines. - Little to no automation tooling used. |
| Measurement & Metrics | - No tracking of build or deployment success/failure rates. |
| Category | Description |
|---|---|
| People & Culture | - Teams start adopting automation scripts to reduce manual work. - Some automation knowledge exists but is siloed. |
| Process & Governance | - Basic scripting implemented for build, test, or deploy steps. - Automation is applied inconsistently across teams. |
| Technology & Tools | - Initial CI/CD tools introduced but usage varies. - Manual approvals or interventions still common. |
| Measurement & Metrics | - Build success/failure rates begin to be tracked, but not consistently. |
| Category | Description |
|---|---|
| People & Culture | - Automation is part of standard team practices. - Teams collaborate on improving pipeline reliability. |
| Process & Governance | - CI/CD pipelines are established and documented. - Automated testing is integrated into build and deploy stages. |
| Technology & Tools | - Mature CI/CD tools support end-to-end automation. - Environments are provisioned and deployed via automation. |
| Measurement & Metrics | - Metrics on build times, deployment frequency, and success rates are regularly reviewed. |
| Category | Description |
|---|---|
| People & Culture | - Teams use data to optimise pipeline performance. - Automation ownership is shared across roles. |
| Process & Governance | - Pipeline efficiency and stability are monitored and improved. - Automation failures trigger alerts and fast remediation. |
| Technology & Tools | - Advanced automation includes automated rollback, testing, and security scans. - Automated environment provisioning supports consistent deployments. |
| Measurement & Metrics | - Quantitative metrics drive continuous pipeline improvements. - Mean time to recovery (MTTR) and deployment lead time monitored. |
| Category | Description |
|---|---|
| People & Culture | - Automation enables continuous deployment and rapid feedback. - Teams innovate with self-healing and adaptive workflows. |
| Process & Governance | - Automation strategy evolves dynamically with emerging needs. - Processes incorporate AI/ML for predictive failure detection. |
| Technology & Tools | - Fully automated pipelines with intelligent routing and self-remediation. - Environments are ephemeral, versioned, and reproducible on-demand. |
| Measurement & Metrics | - Continuous delivery metrics consistently improve. - Automation drives innovation, cost efficiency, and resilience. |