DevOps culture

What it is

DevOps culture is the people and process dimension of DevOps: collaboration, shared ownership, blameless feedback, small fast iterations, and continuous learning — as opposed to the tooling alone.

Why it exists

Tooling (pipelines, automation) fails without the right culture. Culture is what makes teams actually ship often, share on-call for what they build (“you build it, you run it”), and learn from failures instead of assigning blame.

Key ideas

• Collaboration & shared ownership across dev, ops, and security.
• Automation of everything repetitive.
• Small, frequent, reversible changes (enabled by feature-flags/rollback-strategy).
• Blameless postmortems and continuous improvement.
• Shift-left on testing & security (shift-left).

Exam notes

• AZ-400 is half-technical, half-cultural: expect questions on process, collaboration, and continuous improvement — not just tooling.
• “You build it, you run it” is a core cultural pillar.

Related

delivery-pipeline · dev-sec-ops · continuous-feedback · shift-left

📘 Source: Microsoft Learn — Devops Culture