DevOps
Definition
DevOps is a set of practices, cultural norms, and tools that unify software development (Dev) and IT operations (Ops) to shorten the development lifecycle, increase deployment frequency, and improve software reliability.
DevOps emerged around 2009 from the intersection of the agile movement and the infrastructure-as-code movement. The 'DevOps days' conference in Ghent, Belgium — organized by Patrick Debois — is often cited as the origin point. The term reflects a deliberate rejection of the wall between development teams (who ship features) and operations teams (who run infrastructure) — a wall that caused slow releases, finger-pointing, and fragile systems.
The CALMS model captures DevOps values:
- Culture: shared ownership of delivery and reliability; no 'throw it over the wall'
- Automation: automate everything that can be automated — builds, tests, deployments, monitoring
- Lean: eliminate waste; optimize flow; minimize batch sizes
- Measurement: measure everything; use data to improve; define and track DORA metrics
- Sharing: share knowledge, tools, and on-call responsibility across teams
Key DevOps practices: continuous integration, continuous delivery, infrastructure as code, monitoring and observability, incident management, and blameless post-mortems.
DORA (DevOps Research and Assessment) metrics are the standard measures of DevOps performance: deployment frequency, lead time for changes, change failure rate, and mean time to recovery (MTTR).
DevOps architecture and workflow discussions happen frequently at whiteboards — pipeline diagrams, on-call structure, incident runbooks, and observability architecture are all common whiteboard subjects.
Examples
- DORA elite performer: deploy to production multiple times per day, lead time under one hour, change failure rate under 5%, MTTR under one hour
- Infrastructure as code: Terraform manages all cloud resources; developers can spin up a full environment in 10 minutes via a single command
- Blameless post-mortem: after an outage, the team documents the timeline, contributing factors, and action items — no blame, systematic improvement
- Platform team: internal developer platform abstracts cloud complexity so product engineers can deploy without knowing Kubernetes
Related terms
Snap a devops. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.