Why DevOps is not enough
summary
Argues DevOps sparks a reorg but won’t deliver alone: IT must become an ecosystem of agile practices, platform teams and automation so cross-functional groups can push features in sub-day or even several-hours cycles. Recommends cloud and containers for instant provisioning, microservices or self-contained systems for independent evolution, automated ops and monitoring for resilience, and organizational shifts toward outcome over output with roughly 20% of cycles reserved for continuous improvement.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:09What DevOps really means
- 7:56Why DevOps isn't enough
- 12:37Evolution of IT and markets
- 19:33New drivers for IT change
- 23:31Building blocks for new IT
- 28:07DevOps as organizational driver
- 34:48Technology and feedback loops
- 37:59Interconnected building blocks
- 39:01Summary and recommended reading
- 40:13Q&A
related talks
30mAdopting DevOps? You are aiming at the wrong target!
54mEffective DevOps for Organizations
05mPost "Accelerate": Why are we still failing at adopting DevOps in the Enterprise?
01h 02mWe have DevOps. No one was fired. But what to do?!
50mAdopting DevOps? You are Aiming at the Wrong Target!
06mLow Growth DevOps
11mDevOps Pitfalls, Beyond The Technology
36mThe Rise and Fall of DevOps