Standard : Dependency Lead Time
Description
Dependency Lead Time measures the time it takes for work to be unblocked when a team is waiting on another team, system, or external vendor. It reflects how well cross-team collaboration supports flow.
How to Use
What to Measure
- Time from when a dependency is raised to when it is resolved.
- Track average and 85th/95th percentile lead times.
Dependency Lead Time = Resolution Date − Request Date
Example: Average time to resolve dependencies = 5.2 days.
Instrumentation Tips
- Tag dependencies explicitly in Jira or delivery tracking tool.
- Track partial completions for large dependencies.
- Visualise dependency aging in a dashboard.
Why It Matters
- Flow efficiency: Long waits slow delivery of value.
- Bottleneck detection: Highlights systemic constraints.
- Team alignment: Encourages proactive planning.
Best Practices
- Identify recurring dependencies and automate or decouple them.
- Use Team Topologies to reduce cross-team handoffs.
- Review aging dependencies in weekly portfolio syncs.
Common Pitfalls
- Not tagging dependencies consistently.
- Counting blocked time as active work.
- Ignoring dependencies outside immediate team (e.g. vendors).
Signals of Success
- Decreasing average and P95 dependency lead times.
- Fewer delivery delays caused by external blockers.
- Higher roadmap delivery confidence.
- [[Roadmap Delivery Confidence]]
- [[Flow Efficiency]]
- [[Cycle Time]]