Agile is also for Ops
summary
Argues agile does work for Ops and shows what actually changes: move from chaotic Jira piles to a single pull queue, enforce work-in-progress limits, break tickets into bite-size pieces, and embed Ops in dev standups so the 10% of direct coordination happens earlier. Uses Kanban then Scrumban, measures outcomes with sprints as timeboxes, adopts 20% engineering time and plans around a 60/40 planning split to tame interrupts.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:10Disclaimers
- 2:12Why Agile
- 5:07Working in Ops
- 6:33Frustration
- 8:15Scrum vs Agile
- 9:23Kanban
- 11:32Never assume words mean the same
- 13:32Scrumbonne
- 16:52The Return
- 18:42Gift Structure
- 19:22New Forms of Toil
- 19:55Collaborate
- 20:40Bring sanity
- 21:38Capacity controls
- 22:16My favorite resources
- 23:27Onesizefitsall model
- 24:41Getting everyone on board
- 25:41Embedded ops
- 26:38Factor in voices in your organization
- 28:00The 6040 rule
- 29:30Boston DevOps community
- 30:17Jasons current organization
related talks
46mThe Neverending Story: Agile Transformation for DevOps
32mSolving the Dev/IT Cultural Divide with Operational Agile
20mDon't Cross the Streams - Op Tasks, SRE Teams & Sprint
20mAgile development application for live ops
33mOperations: the last Mile for DevOps
30mING's Journey to Agile
08msoftware architecture and agile development
30mHow DevOps is Enabling Lean Application Development