DevOps Foundations and Culture
What this domain tests
DevOps Foundations and Culture tests whether you can explain DevOps as a socio-technical operating model rather than a toolchain. Expect CALMS (Culture, Automation, Lean, Measurement, Sharing), the Three Ways (flow, feedback, continual learning), DORA's four key metrics, Conway's Law, and blameless learning.
Core rules and concepts
- Optimize the whole value stream, not a single silo. Local efficiency, such as a fully utilized QA team, can worsen lead time.
- The Three Ways: accelerate left-to-right flow, shorten and amplify feedback loops, and embed continual experimentation.
- DORA measures outcomes: deployment frequency, lead time for changes, change failure rate, and time to restore service. Story points or ticket counts are not substitutes.
- Conway's Law says system design mirrors communication structures; team boundaries and platform teams should be designed deliberately.
- Blameless culture fixes systems and processes, not individuals. Psychological safety is a prerequisite for fast incident learning.
Worked example
A team deploys monthly, has a 12-day lead time, a 25% change failure rate, and a 9-hour MTTR. The tempting fix is "add more testers." Reasoning: the 12-day lead time is dominated by a two-week integration branch and a 30-step manual release, so adding testers increases batch size and queue time. Higher-leverage changes are trunk-based development with small batches, automated build and test gates, and a tested rollback path. Those target flow and feedback and should reduce lead time and MTTR before headcount changes.
Traps that cost marks
- Defining DevOps as "developers doing ops" or as Jenkins plus Docker.
- Treating DORA metrics as individual performance targets; they are system outcomes and invite gaming.
- Calling a postmortem blameless while recording "human error" as the root cause.
- Assuming the org chart must change before any technical practice can improve.