100 ideas to bring DevOps in an organization
summary
Catalog lists specific practices not slogans: a working platform with container runtime, integrated CI/CD, monitoring and infrastructure‑as‑code that grows from a small team into an orderable service; a hard metric that every new developer pushes to production on day one; experiments like unicorn sprints, approval workflows to block SSH, a “wall of shame” for long‑running servers, self‑service APIs to cut ticket volume, and on‑call as voluntary rotation — details, counts and outcomes.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:20Speeding up Software Delivery
- 7:48Open Source as example
- 10:58Bad times for heros
- 14:07Success Criteria for DevOps
- 20:19Risk Aversion vs. Change Aversion
- 22:49Projects vs. Products
- 27:16Change requires engineering
- 33:50Scaling the Pizza Party
- 37:08Middle management
- 38:02Transformation Models
- 40:02Disablement vs. Enablement Culture
- 45:05Outsourcing
related talks
49m5 Steps to a DevOps Transformation
39mGetting started with DevOps
41mThe Introduction of DevOps in Large-Scale Organizations
41mStealing The Best Ideas From DevOps (Closing Talk)
29mHunting the DevOps Whale
31m10 Enterprise Tips for DevOps Success
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
54mEffective DevOps for Organizations