DevOps Culture, Collaboration, and Automation
DevOps Culture, Collaboration, and Automation
This domain tests the DevOps mindset and specific automation practice, and whether you can tell culture change apart from tool acquisition.
CALMS and the Three Ways
CALMS: Culture (shared ownership of outcomes rather than handoffs), Automation (repeatable, versioned, tested), Lean (small batches, flow, limited WIP), Measurement (evidence and feedback), Sharing (knowledge and blameless learning). The Three Ways: flow from development to operations (small batches, shift left), fast feedback at every stage (telemetry, tests, monitoring), and continual learning (experimentation, repetition, blameless postmortems).
Culture diagnostics
Westrum's typology classifies organisations as pathological (information hoarded, messengers shot), bureaucratic (silos, messengers ignored) or generative (information shared, failures investigated). High delivery performance correlates with generative cultures. Blameless postmortems ask what made an action seem reasonable at the time, not who did it, and must produce actions with owners and dates.
Automation practice
Automate toil: manual, repetitive, automatable, tactical work that scales linearly with service growth. A sensible order is version control for everything, build once and promote the same artifact, automated tests in the pipeline, infrastructure as code, self-service environments, then deployment automation with tested rollback. Security shifts left: scanning in the pipeline, secrets management, least privilege.
Worked example
Provisioning a test environment takes ten working days: an email request, a weekly approval forum, then a two-hour manual build. A proposal is to buy a faster build tool. Reasoning: the build is two hours of a ten-day cycle, so the constraint is the weekly queue. Automating the build alone leaves almost nine days of waiting intact. The correct sequence is a self-service request with automated policy checks, then an automated build - the queue, not the build speed, is what to remove.
Traps
Defining DevOps as a team, a role or a tool; equating continuous delivery with continuous deployment; postmortems that identify a person and stop there; automating a process before removing its waste; assuming 'sharing' happens without a mechanism such as demos, documentation or on-call rotation.