In Kanban or Scrum the removal of impediments or blockages is critical for the productivity of teams. One effective behaviour is swarming. Here’s what it is and how it works …
In lean production the andon cord stops the line and all employees affected by the stoppage swarm to collectively resolve the issue. How can this effective behaviour applied to software development?
When upstream folks such as developers and testers help systems-maintainance people to recover an environment, this behaviour is often referred to as swarming. Swarming implies the concept that the team swarms together to work on a single problem until it is resolved. The nature of Kanban encourages teams to focus on lead time, throughout, and flow throughout the value stream. By aligning all the groups up and down the value stream with the same goals, there is an incentive for swarming behaviour to emerge. Everyone wins when idle pople volunteer to collaborate to resolve an issue that affects them event though it is not in their immediate work area or are of responsibility.
- 2 Approaches to Handle Impediments in Kanban
- Take Aways from Scrum Essentials