DevOps Pitfalls, Beyond The Technology
summary
Argues that DevOps fails when people and funding are ignored: creating a separate devops team recreates silos, lavish automation like Azure DevOps pipelines or GitHub Actions does not fix broken processes, and insisting to release every day is unnecessary for many products. Calls for top‑management buy‑in, team autonomy to own infrastructure (Azure Functions example), a funded plan for shared pipelines and libraries, measurable baseline and targets, and heavy investment in education.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:12You don't have to release everyday!
- 2:58DevOps is more than just automation
- 4:00Top Management Buy-in
- 6:10Autonomy
- 7:02Who pays for the common needs?
- 8:13Changing culture costs money!
- 9:12Measure!
related talks
25mDevOps: Why do we Keep Messing Up?
17mDevOps Leadership in practice. True stories
05m5 Pitfalls of Using DevOps to Govern
44mWhy DevOps Fails to Deliver?
45mOpening Keynote: The Enterprise DevOps Mind Trap
35mMore Buzzwords Won't Help: The Long History of DevOps Failures
05mDevOps Is Not a Department
11mBreaking down the walls between developers and operations