Swarm
Dependency Breakers
Let team members flock to where they can resolve dependencies.
Dependency Breakers: Attend • Automate • Block • Contain • Coordinate • Decouple • Flag • Formalize • Measure • Prioritize • Redesign • Reteam • Rotate • Self-service • Standardize • Swarm • Throttle • Toggle • Visualize • Volunteer
Purpose
Encourage team members to contribute to the areas where they can best address dependencies. By temporarily shifting team members possessing the requisite skills between value streams, you ensure that dependent requirements are met while respecting release cadences. It's all about leveraging the individual strengths of each team member to overcome challenges together and adapt to evolving project needs.
Notes
Dependencies are not necessarily bad. Actually, there are many good reasons for people to depend on each other. But you have a problem when those dependencies result in value that is not able to flow.
Rules / Constraints
We have not yet defined any rules or constraints.
“We have broken the cycle of dependency. People have found out they're better off working.”
(Source: John Engler)