DevOps Leadership in practice. True stories
summary
Cites industry stats—70% fail (McKinsey) and 84% fail (Forbes)—and shows concrete failure modes: orders to “be DevOps” without authority, unrealistic three‑month deadlines, missing training and onboarding, broken promises, invisible conflicts, micromanagement, and poor handoffs. Real tools and mismatches appear: an engineer asked to script with Ansible and Azure they never used, and teams lacking a RACI matrix for clear ownership. Examples focus on what was attempted, what didn’t get built, and why it stopped delivering.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:25About Andriy
- 2:17Digital Transformation steps
- 2:54DevOps handbook
- 3:34DevOps leadership
- 4:57Examples of failures
- 6:32Common mistakes
- 8:53Team problems
- 11:50Poor communication
- 15:46No small things
- 16:40Conclusion
related talks
29m5 ways to screw up your DevOps Transformation
11mDevOps Pitfalls, Beyond The Technology
27mThe curious case of the DevOps engineer and other things ...
46mWhy DevOps Does Not Deliver on Its Promises
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
30mA Story of DevOps Transformations
13mTen Ways to Doom Your DevSecOps
45mOpening Keynote: The Enterprise DevOps Mind Trap
