Managing Dependencies Across Programmes
Summary
Dependencies are often identified too late, forcing re-planning and creating delivery risk. A structured mapping session at inception surfaces them while there is still time to act.
Shared challenge
This opportunity addresses Dependency management — a challenge experienced by multiple teams across the contract.
What one team learned
Dependencies are often identified too late — typically once delivery is underway and options are limited.
Reusable improvement
A dependency mapping workshop run at project inception, with a dependency register, RACI and escalation routes.
How other teams can apply it
- 1Run the dependency mapping workshop during mobilisation.
- 2Maintain the dependency register through delivery.
- 3Agree escalation routes with dependent teams up front.
Evidence and artefacts
Suggested SoW wording
A dependency mapping workshop will be held at project inception, producing a maintained dependency register with agreed escalation routes for cross-programme dependencies.
Teams that could benefit
Linked Statements of Work
Benefits expected and measured
Earlier risk identification, improved planning, better coordination.
Late-stage dependency surprises down 55% on Border Trading alpha.
Comments and decision history
- Daniel OkaforDelivery Manager· 8 Mar 2026
Surfaced three cross-team dependencies we'd otherwise have hit in beta.
- Defra Portfolio OfficeGovernance· 2 Apr 2026Status change
Benefits measured and verified — status updated to Measured.