Dependency Management Guide

Transformation programmes rarely fail because a single workstream underperforms in isolation. They far more often stall, slip or blow their budget because something one team needed from another — a decision, a dataset, an approved design, a piece of infrastructure, a third-party deliverable — did not arrive when the plan assumed it would.

This guide sets out a single, consistent approach to identifying, recording, owning, tracking and reporting on dependencies across business transformation projects and programmes, so that this risk is managed by design rather than discovered by accident.

It defines what a dependency is, who is responsible for what, where dependencies are recorded, how they are integrated into the project plan, the cadence for reviewing and reporting them, and the consequences of not doing so.