Stop 01 · DevOps FoundationsTopics · 4/9

DevOps Culture & CALMS Framework

In short

Companies often buy fancy tools and still ship slowly. CALMS is a simple checklist of five things a team needs before the tools actually make a difference.

CALMS — Culture, Automation, Lean, Measurement, Sharing — is a framework describing the pillars a genuine DevOps transformation needs beyond just adopting new tools.

The mascot backstage at a school function holds a stopwatch while stage lights switch on by themselves.

Think of it like this

The school annual day crew

A great annual day needs teachers and students planning together, lights cued automatically, short rehearsals for each act, a stopwatch on every performance, and notes saved for next year. Skip any one and the show drags. That is CALMS in a school hall.

Watch it happen

The five letters of CALMS

Culture

Automation

Lean

Measurement

Sharing

1/6Culture: dev and ops share goals. After an outage the question is 'what failed', never 'who failed'.

The big ideas

What you need to know

Blameless postmortems

After an incident, write what happened and how to stop it repeating. Blaming a person makes people hide mistakes next time.

Small batches

Lean thinking says small pieces of work move faster and break less than big ones.

DORA metrics

Deploy frequency, lead time, change failure rate and time to restore are four common ways to measure delivery.

Share by default

Wikis, demos and open chat channels spread knowledge so nobody becomes the only person who knows a system.

Save yourself the pain

Common mistakes

Oops

Starting a 'DevOps transformation' by only buying new tools.

Do this instead

Start with Culture and Measurement. Find where work waits, then pick tools that remove that wait.

Oops

Running postmortems that end with 'Ravi should be more careful'.

Do this instead

End with system fixes: an alert, a test, a safer default. People make mistakes; systems should catch them.

Your mission

Score a team on CALMS

~15 min

Quick check

After an outage, the manager asks 'Which alert or test would have caught this earlier?' Which CALMS idea is this?

Go deeper

1Learn what each CALMS letter represents and give one concrete example per pillar.
2Identify a company practice you've observed that violates one of the CALMS pillars.
3Understand why 'just buying the tools' without culture change usually fails to deliver DevOps benefits.