Ready, Set, DevOps Roadblock
summary
Argument: shift the incentive from protecting uptime to personal impact and adoption accelerates releases. A single engineer champions automation tools and an automated release process, and the organization goes from 4 releases a year to over 40 while delivering 20 micro changes every month. The approach requires no new architecture — it focuses on who benefits, uses pragmatic automation, and demonstrably works because cadence and promotions follow the outcomes.
AI-written summary · about
chapters (5)
related talks
47mOvercoming Obstacles to DevOps
54mEffective DevOps for Organizations
43mDevOps – when doing the right thing hurts!
50mAdopting DevOps? You are Aiming at the Wrong Target!
32mDevOps as Driver of Organization-Wide Change
34mYou only have to change one thing to do the DevOps
11mBreaking down the walls between developers and operations
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
