A Story of DevOps Transformations
summary
Argues that old manufacturing mental models block DevOps progress and shows concrete fixes: replace stale status reports with a live Splunk dashboard that aggregates JIRA/VersionOne and pinpoints lagging projects; score releases with a release score 0–100 tied to late changes, failed builds and production impact; prefer vendors with APIs and modular engineering or else resorting to a UI screen-scraper; notes a vendor’s claimed 30% average-day-rate cut often hides junior staffing, not real automation.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:40What got you here
- 2:06I stole the title
- 2:26The core problem
- 3:09Where we were
- 5:10Transformation Lifecycle
- 7:14Mental Models
- 8:36Manufacturing vs IT
- 12:49Burning down the factory
- 15:36Production processes
- 17:15Governance
- 20:19Context
- 21:32Technology
- 25:46SLA
- 28:05Vendors
- 28:41Conclusion
related talks
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
42mData-Driven DevOps
34mDevOps Transformation from the C-Level point of view
47mOvercoming Obstacles to DevOps
48mNew barriers for DevOps adoption
17mDevOps Leadership in practice. True stories
38mDevOps transformation – the good, the bad and the ugly
50mAdopting DevOps? You are Aiming at the Wrong Target!