Mission Impossible Prioritizing DevOps
summary
Argues that DevOps succeeds by finding a single bottleneck, fixing it, then iterating rather than chasing a full transformation; recommends starting with version control and resolving test automation dependencies, mapping capabilities with a Kanban-style dependency model, and launching small pilots to prove value. Emphasizes measuring both system metrics and business outcomes, using formal feedback loops, recruiting supporters to avoid "death by a thousand initiatives," and running an organized intake process. Prioritize the constraint that blocks delivery and expand from there.
AI-written summary · about
related talks
47mOvercoming Obstacles to DevOps
01h 02mThe Enterprise DevOps Challenge
01h 02mThe Enterprise DevOps Challenge
34mDevOps Transformation from the C-Level point of view
01h 02mWe have DevOps. No one was fired. But what to do?!
54mEffective DevOps for Organizations
50mAdopting DevOps? You are Aiming at the Wrong Target!
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
