The Road More Traveled: Putting Transformation Back on the Rails
summary
Argues that measurable, self-reinforcing cycles of metrics plus tools produce repeatable DevOps transformation, backed by five years of State of DevOps data and Chef customer telemetry. Key metrics cluster around speed, efficiency and risk; one move — reducing time from commit to deploy to minutes — forces small batches, feature flags, different project metrics and executive alignment. Chef Automate, inspect and habitat implement automated compliance tests, detect-and-correct remediations and artifact pipelines. Notes surprising pattern: a dozen leading indicators drive city-scale change and medium performers show higher failure rates than low performers.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:03How do you drive transformation
- 4:18Cities around the world
- 7:12The road less traveled
- 8:36Identifying the right metrics
- 9:13Measure the things that matter
- 10:06Defining metrics
- 10:58Unintended consequences
- 12:15State of DevOps
- 16:48Decentralizing Knowledge
- 18:32Fail Quickly
- 19:41Operational Chasm
- 21:51Dont Experiment
- 22:17The Scientific Method
- 23:52How to Develop a Good Filter
- 24:52Tools and Behaviors
- 25:04Change Your Tool
- 26:07What are the Tools
- 26:59Metrics
- 27:38Compliance Automation
- 27:50Development and Security
- 29:04Whitepaper
- 29:33Chef Automate
- 30:42Speed
- 32:48The Way to Succeed
related talks
33mMeasuring Developer Efficiency in DevOps: Key Questions, Metrics, Best Practices
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
42mData-Driven DevOps
30mA Story of DevOps Transformations
54mEffective DevOps for Organizations
49m5 Steps to a DevOps Transformation
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
05mThe Road to DevOps Success: It’s Human