Skip to main content
Software Delivery & Engineering OpsLast reviewed 2026-09-15

DevOps

The operating model where development and operations share ownership end to end.

Overview

Read the full DevOps guidance
DevOps is an operating model in which the people who build software and the people who run it share ownership of the whole lifecycle — from commit to production telemetry. Teams optimize for flow (short lead time from idea to production), feedback (fast, automated signals when something is wrong), and continuous learning (blameless retrospectives that change the system, not the people). OpsRoadmaps assesses DevOps maturity through the practices that measurably move it: deployment automation, trunk-based flow, automated test pyramids, production ownership by dev teams, and shared on-call. The DORA metrics — deployment frequency, lead time, change failure rate, and time to restore — anchor the measurement: maturity claims that those numbers cannot support do not score well here.

Capabilities

  • Change Management

    Low-ceremony, high-safety change flow: small batches, automated checks, fast rollback.

  • Deployment Automation

    One-command, pipeline-driven, auditable releases with progressive rollout.

  • Rollback Capability

    Reverting a bad change in minutes, from version control, without heroics.

Practices

  • Progressive Delivery

    Canary and staged rollouts that limit the blast radius of every change.

Metrics

  • Change Failure Rate

    Share of deployments causing degraded service requiring remediation.

    Unit: %. Good direction: down.

  • Deployment Frequency

    How often a team releases to production.

    Unit: per week. Good direction: up.

Architecture patterns

Reference architectures and their trade-offs live in the blueprints library.

Maturity

Maturity for devops is measured, not guessed — every score traces to your answers. See how maturity is scored.

Put it to work

Sources

DevOps — OpsRoadmaps | OpsRoadmaps