How we killed DevOps by creating a dedicated DevOps team
summary
Company creates a central DevOps team, then discovers it hoards knowledge, becomes a bottleneck and spawns constant firefighting; response is a DevOps wartime channel and daily coordination, an automated NPS workflow and Bob (Slack bot) to sync tickets and roles. Measured results: staging setup drops from weeks to about eight minutes, ticket lead time target moves under two days, and an NPS target 50 becomes the steering metric so changes are visible and acted on.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:02How we killed DevOps
- 8:18Growth
- 9:04DevOps team
- 13:16Hiring engineers
- 16:57Desperate measures
- 17:29DevOps wartime
- 22:54Focus
- 27:26Aha moment
- 31:00DevOps pillars
- 31:40Culture
- 34:42Three Cultures Model
- 39:15Automation
- 41:59Parameters
- 44:48Lean
- 46:47Metrics
- 51:27Sharing
related talks
01h 02mWe have DevOps. No one was fired. But what to do?!
30mWhat's It Like When DevOps Is Just Another Day at the Office?
34mDevOps culture
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
37mFrozen DevOps? Team Topologies Comes to the Rescue!
23mDevOps Is More About Customer Feedback And Quick Learning...
29mDevOps at Scale is a Hard Problem
40mHow did our DevOps team become another silo?