Block
Dependency Breakers
Say "No" to new work items when they have 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
Don't hesitate to decline new work items if they come with dependencies. It's essential to assess the potential impact on your workflow. Safeguard your team's throughput by only allowing stories with dependencies into your workflow when you're confident that those dependencies will be resolved promptly. Remember, sometimes saying "No" can be just as important as saying "Yes" to maintain productivity.
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)