Dependency Management

Very little work in a large organization happens in isolation. A new customer app may depend on an API that another team is building, a data migration may need to finish before a reporting project can start, and several projects may all rely on the same platform upgrade. When these dependencies are not managed, one late delivery can delay many others, and teams discover the problem only when they are already blocked. By then, the options for recovery are limited and usually expensive. Dependency management makes these relationships visible and coordinates the work on both sides of each one.

Dependencies exist at every level: between tasks within a project, between projects in a program and between programs and teams across a portfolio. The larger and more interconnected the portfolio, the more important it becomes to manage them deliberately. For portfolio leaders and PMOs, dependency management is often the difference between a portfolio that delivers on schedule and one in which delays spread from project to project.

Definition of Dependency Management

Dependency management is the identification, documentation, analysis, monitoring and resolution of dependencies between work items, so that the delivery of each item is coordinated with the items it relies on and the items that rely on it.

It is a core activity in program management and is usually recorded in tools such as the RAID log, where dependencies sit alongside risks and issues.

Types of Dependencies

Task dependencies link activities within a project, such as testing that cannot start until development is complete.

Project dependencies link separate projects, where one needs an output, decision or capability from another.

Resource dependencies arise when several pieces of work need the same people, environments or equipment at the same time.

Technical dependencies link systems, such as an application that needs an interface, data source or platform version provided by another system.

External dependencies rely on parties outside the organization, such as vendors, regulators or partners. They are often the hardest to control, so they usually need more buffer and closer monitoring.

Direction and Strength of Dependencies

Every dependency has a provider, who must deliver something, and a consumer, who needs it. Both sides need to agree what will be delivered and when.

Hard dependencies are unavoidable, such as needing a system to exist before it can be tested. Soft dependencies reflect preference or convenience and can sometimes be removed by changing the plan.

Dependencies with long lead times, many consumers or uncertain providers carry the most risk and deserve the closest attention. Dependencies on a single person or team are also high risk, since any absence or reprioritization affects every consumer.

Mapping dependencies, often as a network diagram or matrix, shows which items are critical and where a single delay would have the widest effect.

Importance of Dependency Management in Strategic Portfolio Management

Dependency management prevents delays from spreading. Spotting a late provider early gives consumers time to adjust plans or find workarounds.

It improves planning. Knowing which projects depend on each other allows leaders to sequence the portfolio realistically and avoid starting work that will immediately be blocked.

It also clarifies accountability. Recording each dependency with a named provider and consumer makes it clear who must deliver what, and to whom.

Dependency Management and Financial Management

Delays caused by unmanaged dependencies often have direct costs, such as idle teams, extended contracts and postponed benefits.

Understanding dependencies helps leaders judge the real cost of stopping or delaying a project, since other projects may lose value if they rely on it.

Investments in shared platforms and capabilities that many projects depend on can be justified by the value they make possible across the portfolio, not just their own business case.

Including dependency risk in portfolio risk management helps size contingency for the portfolio as a whole.

Common Challenges

Dependencies are often recorded only by the consumer, so the provider may not know that others rely on its work.

Dependency information quickly goes out of date if it is not reviewed regularly with both sides. Dates agreed at the start of a quarter can shift several times before the delivery is due.

In large portfolios, the number of dependencies can become overwhelming. Focusing on the most critical ones is more effective than trying to track every link.