Solving the Dev/IT Cultural Divide with Operational Agile
summary
Attempts to stop Dev→IT dropped batons by forming mixed teams (product owner, Dev manager, monitoring/platform/DBA/ops) that write user stories, sort them into epics and a visible backlog, and Sprint focused work. The operationalization standup drops scrum orthodoxy—no story points or velocity—but delivers: a groomed backlog in one week, the problem database cleared as a suspect in four weeks, the team disbands in eight, and improvements (higher deployment frequency, better success rate, lower MTTR) touch about 5% of products.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:32Global Hosting Services
- 4:04Grains of Sand
- 4:37Cultural Circle of Life
- 6:16Communication and Accountability
- 12:25Dev vs IT
- 15:27Work Together
- 18:11Good News
- 19:36DevOps Lessons
- 20:06Big Finish
- 23:23Dont insult customers
- 25:20Precision of metrics
- 26:25Enforce roles not boundaries
- 28:01Spin off leadership
- 28:59Ask for it
- 30:19Ambitious things
- 31:03Final Thought
related talks
29mDevOps Transformation at Scale
32mAgile is also for Ops
28mBringing DevOps to Product
30mHow DevOps is Enabling Lean Application Development
01h 02mThe Enterprise DevOps Challenge
30mA Story of DevOps Transformations
20mAgile development application for live ops
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World