This standard ensures changes are deployed to production frequently and sustainably, enabling faster feedback, safer releases, and quicker time-to-value. Deployment Frequency (DF) is a key DORA metric and a signal of healthy engineering flow.
Aligned to our "Fast Feedback Loops" and "Empower Teams to Self-Serve" policies, this standard promotes autonomy, reduces risk, and supports continuous delivery. Without it, releases become bottlenecks, innovation slows, and operational risk increases.
| Category | Description |
|---|---|
| People & Culture | Teams are reluctant to deploy often due to risk and stress. Releases are often hero-led events. |
| Process & Governance | Manual release approvals and coordination dominate. Cadence is undefined. |
| Technology & Tools | Deployment scripts or tooling are ad hoc or inconsistent. |
| Measurement & Metrics | No metrics on frequency or deployment success rates. |
| Practices | Releases often require downtime or full system restarts. |
| Category | Description |
|---|---|
| People & Culture | Teams begin to value faster deployment but remain cautious. |
| Process & Governance | Some governance processes are defined but inconsistently applied. |
| Technology & Tools | CI pipelines exist, but deployment automation is partial. Approvals often still manual. |
| Measurement & Metrics | Deployments are logged. Teams begin to track cadence informally. |
| Practices | Scheduled releases occur weekly or monthly. Rollback plans exist but are manual. |
| Category | Description |
|---|---|
| People & Culture | Teams embrace continuous delivery mindset. Smaller, safer deployments are encouraged. |
| Process & Governance | Standardised deployment process across teams. |
| Technology & Tools | Fully automated CI/CD pipelines with deployment controls (e.g. feature flags, blue-green). |
| Measurement & Metrics | Deployment frequency is measured per service or team. |
| Practices | Releases occur at least once per day per service. Post-deployment checks are standard. |
| Category | Description |
|---|---|
| People & Culture | Teams review delivery metrics to improve flow. Failures are used as learning signals. |
| Process & Governance | Delivery metrics are used to streamline governance. |
| Technology & Tools | Real-time dashboards track frequency, failure rate, and flow efficiency. |
| Measurement & Metrics | Deployment frequency trends analysed across time, services, and teams. |
| Practices | Deployment strategies include canary, progressive delivery, and automation of release notes. |
| Category | Description |
|---|---|
| People & Culture | Teams experiment with continuous deployment and rapid iterations. |
| Process & Governance | Governance adapts to optimise speed and safety together. |
| Technology & Tools | Tooling enables proactive detection of delivery bottlenecks. Platform teams support reuse. |
| Measurement & Metrics | Continuous improvement of DF trends across org. Success linked to team goals. |
| Practices | Releases are on-demand, zero-downtime, and safe by default. Engineering flow is measured and celebrated. |