Cross-Project Dependencies | Tracking & Coordination
Track cross-project dependencies with linking, timeline visualization, and coordination workflows. Prevent delays in multi-project initiatives.
6 min read
Cross-project dependencies create hidden risks that surface at the worst possible times. GitScrum's dependency tracking, cross-project linking, and timeline visualization help teams identify, communicate, and coordinate dependencies before they cause delays in complex multi-project initiatives.
Dependency Types
| Type | Example | Management Approach |
|---|---|---|
| Sequential | API must exist before UI | Sequence sprints correctly |
| Shared resource | Both teams need DBA | Coordinate schedules |
| Technical | Shared library update | Version coordination |
| External | Vendor integration | Contract + timeline |
| Knowledge | Team A has expertise | Schedule knowledge transfer |
Dependency Tracking Framework
DEPENDENCY IDENTIFICATION
DURING PLANNING:
┌─────────────────────────────────────────────────┐
│ For each epic/initiative, ask: │
│ │
│ 1. What do we need from other teams? │
│ ├── APIs or services │
│ ├── Shared components │
│ ├── Infrastructure │
│ └── Expertise or reviews │
│ │
│ 2. What are other teams waiting on from us? │
│ ├── APIs we need to deliver │
│ ├── Specs or designs │
│ ├── Data or access │
│ └── Approvals or reviews │
│ │
│ 3. External dependencies? │
│ ├── Vendor deliverables │
│ ├── Customer decisions │
│ └── Regulatory approvals │
└─────────────────────────────────────────────────┘
Cross-Project Epic Structure
MULTI-TEAM INITIATIVE TRACKING
Epic: Payment Gateway Integration (Q2)
Owner: Product Manager
Teams: Backend, Frontend, Mobile, Security
┌─────────────────────────────────────────────────┐
│ DEPENDENCY MAP: │
│ │
│ Phase 1 (Sprint 1-2): │
│ ┌─────────────┐ │
│ │ API Design │ ← Security review │
│ │ (Backend) │ │
│ └──────┬──────┘ │
│ │ │
│ Phase 2 (Sprint 3-4): │
│ ▼ │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ API Build │ │ Mock API │ │
│ │ (Backend) │ │ for testing │ │
│ └──────┬──────┘ └──────┬──────┘ │
│ │ │ │
│ Phase 3 (Sprint 5-6): │ │
│ ▼ ▼ │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ Web UI │ │ Mobile UI │ │
│ │ (Frontend) │ │ (Mobile) │ │
│ └──────┬──────┘ └──────┬──────┘ │
│ │ │ │
│ Phase 4 (Sprint 7): │ │
│ ▼ ▼ │
│ ┌─────────────────────────────────┐ │
│ │ Integration Testing (All teams) │ │
│ └─────────────────────────────────┘ │
└─────────────────────────────────────────────────┘
Dependency Task Template
DEPENDENCY DOCUMENTATION
┌─────────────────────────────────────────────────┐
│ Task: Integrate payment webhook handling │
│ Project: Backend API │
│ Labels: [dependency] [waiting-on-external] │
│ │
│ DEPENDENCIES: │
│ │
│ We depend on: │
│ ├── [FRONT-234] Payment form validation │
│ │ Team: Frontend │
│ │ Status: In Progress │
│ │ Expected: Sprint 5 │
│ │ │
│ └── [VENDOR] Stripe webhook documentation │
│ Contact: stripe-support@... │
│ Status: Waiting (ticket #12345) │
│ Expected: Feb 15 │
│ │
│ Depending on us: │
│ └── [MOBILE-567] Payment confirmation screen │
│ Team: Mobile │
│ Impact if late: Mobile release delayed │
│ │
│ MITIGATION: │
│ Using Stripe sandbox for development │
│ Created mock endpoints for mobile team │
└─────────────────────────────────────────────────┘
Cross-Team Coordination
DEPENDENCY COORDINATION PRACTICES
WEEKLY DEPENDENCY SYNC:
┌─────────────────────────────────────────────────┐
│ Attendees: One rep from each team │
│ Duration: 30 min │
│ Cadence: Weekly │
│ │
│ Agenda: │
│ 1. Review blocked items (5 min) │
│ 2. Upcoming deliverables (10 min) │
│ 3. At-risk dependencies (10 min) │
│ 4. Actions and owners (5 min) │
│ │
│ Output: Updated dependency status │
└─────────────────────────────────────────────────┘
DEPENDENCY STATUS UPDATES:
┌─────────────────────────────────────────────────┐
│ On Track: ✓ Proceeding as planned │
│ At Risk: ⚠ May slip, needs attention │
│ Blocked: 🔴 Cannot proceed │
│ Completed: ✓✓ Delivered │
│ │
│ Rule: Update status before weekly sync │
└─────────────────────────────────────────────────┘
ESCALATION PATH:
┌─────────────────────────────────────────────────┐
│ Day 1: Blocked → Notify other team lead │
│ Day 3: Still blocked → Escalate to managers │
│ Day 5: Still blocked → Escalate to directors │
│ │
│ Adjust timelines based on dependency impact │
└─────────────────────────────────────────────────┘
Portfolio View
CROSS-PROJECT DEPENDENCY DASHBOARD
INITIATIVE: Q2 Platform Upgrade
┌─────────────────────────────────────────────────┐
│ Dependencies Overview: │
│ │
│ Total dependencies: 24 │
│ ├── On Track: 18 (75%) ✓ │
│ ├── At Risk: 4 (17%) ⚠ │
│ └── Blocked: 2 (8%) 🔴 │
│ │
│ Blocked Items: │
│ ├── [BE-123] Payment API - waiting on vendor │
│ │ Owner: @john │
│ │ Blocked since: 3 days │
│ │ Impact: Frontend, Mobile blocked │
│ │ │
│ └── [SEC-45] Security audit - resource crunch │
│ Owner: @security-team │
│ Blocked since: 2 days │
│ Impact: Production release blocked │
│ │
│ At Risk Items: │
│ ├── [FE-567] Dashboard redesign - 2 days late │
│ └── [DB-89] Schema migration - pending review │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Implicit dependencies ("they know we need it")
✗ No tracking of external dependencies
✗ Waiting until blocked to communicate
✗ No escalation path defined
✗ Dependencies discovered mid-sprint
✗ Single point of failure for coordination