Dependency Mapping

Definition

Dependency Mapping is the disciplined identification and classification of every relationship between activities, deliverables, or teams that determines what must happen before something else can start or finish. AACE and PMI describe four classes: mandatory (hard logic, dictated by physics or contract), discretionary (preferred sequencing), external (outside the project), and internal (within the project). On the schedule it appears as predecessor/successor links; on a programme it appears as a dependency log.

Why It Matters

Most schedule failures are dependency failures. Tasks finish; their successors cannot start; the team learns at the daily stand-up. The cost of a missed external dependency rises with how late it surfaces. Mapping the dependencies before the work makes the schedule honest and the risk register useful.

Types

• Mandatory — physical or legal necessity ("rebar before pour").
• Discretionary — preferred sequence ("integration test before performance test").
• External — outside the team or project ("permit issuance by regulator").
• Internal — within the project ("steel detailing before fabrication release").

Real-World Construction Example

On a port expansion, a dependency mapping workshop with engineering, procurement, marine, and operations surfaced 23 previously implicit dependencies. The most consequential: a regulatory navigational permit required hydrographic survey data the survey contractor was not contracted to provide before dredging began. The discovery, made eight months early, cost $48,000 to resolve. Found six weeks before dredging, it would have cost approximately $2.1M in vessel standby.

Real-World IT / Agile Example

A platform team mapping cross-squad dependencies for a single quarter identified 41 inter-team handoffs across nine squads. The exercise produced a one-page heatmap of which squads were most coupled. Six handoffs were renegotiated to feature flags or stub APIs; two squads merged epics; one external partner's missing API was escalated and contracted. The next quarter's velocity rose 14% with no team additions.

Key Takeaways

• Dependencies cause more delay than scope, weather, or labour combined on most projects.
• Mandatory and external dependencies are immovable — they must be discovered, not invented.
• Discretionary dependencies hide opportunity; challenge them in every plan review.
• The dependency map ages — re-run it at each rolling wave.

Expert Tips

• Run the workshop with the people who do the work, not their managers.
• Mark every external dependency with a named owner outside the team; ownerless external dependencies are root-cause for missed dates.
• Quantify dependency slack — short slack on external dependencies is the highest-risk pattern in the plan.
• Tag discretionary dependencies so a future planner knows where compression is possible without re-engineering.
• Visualize: a dependency graph reveals patterns no spreadsheet does.

Common Mistakes

• Treating Finish-to-Start as the default and ignoring SS/FF/SF relationships where they are physically real.
• Missing the external dependency on a vendor, regulator, or sister project.
• Burying dependencies in narrative and never re-extracting them when the schedule changes.
• Discretionary dependencies left unchallenged for years because "we have always done it that way."
• Letting look-ahead sessions ignore dependencies in favour of activities — the activities are usually fine; the dependencies are what fail.

Practical Lessons Learned

• Capital projects with a formal dependency log have fewer claims; the log is its own dispute-avoidance tool.
• Squads that map dependencies quarterly run quieter quarters than ones that improvise.
• The dependency that costs you most is the one nobody felt accountable to name.

Related Encyclopedia Entries

• Network Diagram
• Critical Path Method
• Integrated Master Schedule
• Look-Ahead Schedule
• Forward Pass Scheduling
• Epic

Related Research Articles, Case Studies & Tools

• Project Controls Academy: Scheduling
• Schedule Health Checker
• Learning Tracks: Schedule Management
• Books on CPM Scheduling
• Port expansion dependency study
• Cross-team dependency research