We have DevOps. No one was fired. But what to do?!
summary
Argues that organizational change, not firing people or hiring a single expert, is required for successful DevOps adoption; recommends influencing others and delivering small measurable wins. Recommends reading The Phoenix Project and Accelerate, measuring DORA metrics (lead time, deploy frequency, change‑failure rate, time‑to‑restore), building CI pipelines with Jenkins and Docker plus continuous testing, and using progressive delivery to reduce reliance on large staging environments.
AI-written summary · about
chapters (10)
- 0:00DevOps context
- 3:50What DevOps is
- 13:30Influence without authority
- 23:03Why DevOps is needed
- 31:15Convincing management
- 45:07DevOps objections
- 51:30Negotiation tactics
- 55:06If negotiation fails
- 57:36Career after DevOps
- 59:19Q&A
related talks
30mSurviving DevOps
25mDevOps for Pointy-Haired Bosses
54mEffective DevOps for Organizations
37mWant to do the DevOps? Change Everything
01h 01m"Doing Devops" as a politically powerless developer
47mOvercoming Obstacles to DevOps
50mAdopting DevOps? You are Aiming at the Wrong Target!
28mYou Can’t buy DevOps, but you may Need to Sell it