PM Dependency Mapping Template
==============================

Create a project dependency map and management plan for [Project Name].

Project details:
- Project: [name]
- Phase: [current phase]
- Key workstreams: [list]
- External dependencies: [other projects/teams/vendors]
- Critical path concerns: [describe]

DEPENDENCY MANAGEMENT PLAN

DEPENDENCY TYPES

FINISH TO START (FS) — most common
Task B cannot start until Task A finishes
Example: Testing cannot start until development finishes

START TO START (SS)
Task B cannot start until Task A starts
Example: Documentation starts when coding starts

FINISH TO FINISH (FF)
Task B cannot finish until Task A finishes
Example: QA cannot finish until bug fixes finish

START TO FINISH (SF) — rare
Task B cannot finish until Task A starts

INTERNAL DEPENDENCY LOG
| ID | Task | Depends On | Type | Lag | Owner | Status |
| D001 | [Task B] | [Task A] | FS | 0 days | [] | On Track |
| D002 | [] | [] | SS | [days] | [] | [] |

EXTERNAL DEPENDENCY LOG
| ID | What We Need | From Whom | By When | Risk | Status |
| E001 | [Data feed] | [IT Team] | [date] | [H/M/L] | [] |
| E002 | [Approval] | [Legal] | [date] | [] | [] |

CRITICAL PATH DEPENDENCIES
Highest risk dependencies:
1. [Dependency] — Risk: [describe] — Mitigation: []
2. [Dependency] — Risk: [] — Mitigation: []
3. [Dependency] — Risk: [] — Mitigation: []

DEPENDENCY MONITORING
- Review frequency: [weekly]
- Owner: [PM]
- Escalation trigger: [X days at risk]
- Stakeholder notification: [when]

COMMUNICATION TO DEPENDENT TEAMS
Subject: Dependency notification — [Project Name]

"[Team Name], our project depends on [deliverable] from your team by [date]. This is on the critical path and any delay will impact our [milestone] on [date]. Please confirm this is still on track or notify us immediately if there are concerns."

Source: https://promptzyo.com/prompt/pm-dependency-mapping-template