Formalize
Dependency Breakers
Create service-level agreements for common request types.
Dependency Breakers: Attend • Automate • Block • Contain • Coordinate • Decouple • Flag • Formalize • Measure • Prioritize • Redesign • Reteam • Rotate • Self-service • Standardize • Swarm • Throttle • Toggle • Visualize • Volunteer
Purpose
One strategic approach to managing dependencies is establishing service-level agreements (SLAs) for common request types. These agreements serve as protocols that outline how dependencies between teams will be handled, covering the intake process, decision-making procedures, interaction protocols, cycle-time expectations, and/or metrics related to deliverables. While it may initially seem like additional overhead, in larger organizations, the frequency of their use can more than justify the effort.
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)