Default to Open: Creating a DevOps Culture
summary
Argues that DevOps succeeds only when culture changes, not just tools, and gives concrete starting points: measure the four Accelerate metrics including deployment frequency and lead time, get leadership buy‑in, run two‑week iterations, and create a fail fast culture with resources to fix findings. Recommends three open source artifacts to adopt now — Red Hat’s Open Organization Culture Assessment, the Ready to Innovate team tool, and the Open Practice Library — and advises start small and iterate.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:13Introductions
- 1:03Red Hat DevOps Capability Model
- 2:15Software Delivery Performance
- 4:15We Can't Just Deploy New Technology
- 4:42What is Culture?
- 6:28What are the Cultural Values of DevOps?
- 8:00Open Source Is More Than Code. It's Culture
- 9:11Degrees of Open
- 11:28Open Organisation Characteristics
- 12:11Transitioning to a DevOps Culture
- 13:03Starts with Leadership Buy-In
- 15:49Discovery Process
- 16:51Identify Your Key Challenges
- 19:40Fail Fast Culture
- 21:45What We Believe
- 22:52Org Culture Assessment
- 24:13Team Capabilities: Ready to Innovate
- 26:26The Open Practice Library
- 26:37DevOps Practices
related talks
14mA DevOps Mindset: Transforming Organizational Culture
09mexplains DevOps Culture
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
01h 02mWe have DevOps. No one was fired. But what to do?!
39mGetting started with DevOps
30mDevOps: From the Center Out
44mDevops - What does devops culture mean for engineers?
47mOvercoming Obstacles to DevOps