The Problem DevOps Solves
Traditionally, software teams were split into two silos:
- Development — writes code and wants to ship features fast.
- Operations — runs infrastructure and wants stability above all.
These goals conflict. DevOps is the set of practices, cultural values, and tools that unite these teams around a single goal: delivering value to users quickly and reliably.
The CALMS Framework
DevOps culture is often summarised as CALMS:
| Pillar | Meaning |
|---|---|
| Culture | Shared ownership, blame-free retrospectives |
| Automation | Automate repetitive tasks — builds, tests, deployments |
| Lean | Small batches, fast feedback, eliminate waste |
| Measurement | Track everything — deploy frequency, lead time, MTTR |
| Sharing | Open source tools, blameless postmortems, team knowledge |
The DevOps Lifecycle
Plan → Code → Build → Test → Release → Deploy → Operate → Monitor
↑____________________________________________________|
Each phase feeds back into the next, creating a continuous loop.
Key Metrics (DORA)
The DORA research programme identified four metrics that predict high-performing teams:
- Deployment Frequency — how often you ship to production.
- Lead Time for Changes — time from commit to running in production.
- Change Failure Rate — percentage of deployments that cause incidents.
- Mean Time to Recovery (MTTR) — how fast you restore service after failure.
Elite teams deploy multiple times per day and recover from incidents in under an hour.
DevOps Is Not a Role
DevOps is a mindset, not a job title. A "DevOps Engineer" typically builds and maintains the platform (CI/CD pipelines, infrastructure) that enables development teams to ship safely and frequently.