How Swarming Transforms Enterprise Support to Work Better with DevOps
summary
Argues that replacing rigid tiered queues with real-time, self‑organizing swarms — dispatch swarm, backlog swarm, severity one war room — lets teams probe complex failures (using Cynefin-style safe‑to‑fail experiments), cut ticket tennis, and speed learning (one senior support line reports knowledge doubled in a year). Uses chat‑ops and rotations (Microsoft Teams, Slack), pulls in third‑party reps on calls, and shows first‑year gains in mean time to resolution and customer satisfaction, while flagging cost/metric perceptions (first‑line $20 vs third‑line $250) as a management hurdle.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:42DevOps is changing the world
- 5:25What is swarming
- 10:32How to make it work
- 16:23Potential issues
- 18:16DevOps
- 18:45Service Desks
- 19:32Scale
- 20:51The message
- 21:54King Evan
- 22:23Dave Snowden
- 23:03Complexity
- 25:04Experimenting on Complex Systems
- 25:42Dispatch Swarm
- 26:24Other Domains
- 28:22Whats next
- 29:24More resources
related talks
10mCombine Support and DevOps work in an Agile team
51mThe subtle art of supporting mature products
46mThe Neverending Story: Agile Transformation for DevOps
58mHow we killed DevOps by creating a dedicated DevOps team
33mOperations: the last Mile for DevOps
19mDevOps transformation tailored to organizational culture
05mDevOps and incident management: A recipe for success
30mKeeping Your DevOps Transformation from Crushing Your Ops Capacity