Dependency Mapping Exercise

J

Jordan Reyes

@jordan-reyes

·

Map and manage project dependencies across teams and systems

45 copies0 forks
Map dependencies for {{initiative}}.

Initiative scope: {{scope}}
Teams involved: {{teams}}
Timeline: {{timeline}}

**Dependency Categories:**

1. **Technical Dependencies**
   - Systems that must be in place
   - APIs needed
   - Infrastructure requirements
   - Data dependencies

2. **Team Dependencies**
   - Work from other teams needed
   - Shared resources
   - Expertise required

3. **External Dependencies**
   - Third-party services
   - Vendor deliverables
   - Partner integrations

4. **Sequential Dependencies**
   - What must happen first
   - Critical path items
   - Blockers

**Dependency Matrix:**
| Dependency | Type | Owner | Due Date | Risk Level | Status |

**Critical Path Analysis:**
- Identify the critical path
- Highlight schedule risks
- Buffer recommendations

**Dependency Management Plan:**
- How to track dependency status
- Escalation process
- Communication cadence

**Risk Mitigation:**
- For each high-risk dependency:
  - Mitigation strategy
  - Contingency plan
  - Early warning signals

Details

Category

Analysis

Use Cases

Project planningRisk managementCross-team coordination

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing