If Pair Programming is two people working together on a single problem at the same time (pre-Covid, Pairing meant sitting side by side with one computer), then Swarming takes Pairing to the next level, with three or more people working on a problem together.
Most teams discover Swarming as they approach the end of the Sprint with multiple Sprint Backlog Items in progress. If it’s clear that not all items will get to ‘Done’, they start to swarm one or two items at a time to complete them.
More effective teams learn to swarm all items, so a team of six people might only have two items in progress at one time. Each item gets worked on by several people collaboratively until it gets to ‘Done’. Beware, Swarming is often a gateway drug to Ensemble Programming.
Scrum by Example – Overtime on a Scrum Team is an Unhealthy Sign – Swarming would have helped, just a bit.
Scrum by Example – The Story of an Incomplete Sprint – the classic example that should lead to a team discovering Swarming.
- The Kanban Story: Swarming
- Swarming: A Team-based Approach to Getting Work Done
- Swarm: Beyond pair, beyond Scrum
- Swarming: One-Piece Continuous Flow
- How Swarming Helps Agile Teams to Deliver
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index