Multi-Team Coordination | Dependencies & Scrum of Scrums

Coordinate multiple teams on shared projects. Scrum of Scrums, dependency tracking, joint planning, and GitScrum visibility tools for cross-team alignment.

5 min read

Multi-team coordination enables larger initiatives than one team can handle. Good coordination aligns teams without creating bureaucracy. Bad coordination creates meetings, delays, and frustration. This guide covers effective cross-team coordination.

Coordination Patterns

Pattern	Best For
Scrum of Scrums	Daily sync
Joint planning	Sprint/PI planning
Dependency board	Visibility
Cross-team demo	Alignment

Scrum of Scrums

Daily Coordination

SCRUM OF SCRUMS
═══════════════

STRUCTURE:
─────────────────────────────────────
├── One rep per team
├── Daily or 2-3x/week
├── 15 minutes max
├── Focus on blockers/dependencies
├── Not status report
└── Quick sync

QUESTIONS:
─────────────────────────────────────
Each team rep answers:
├── What did team accomplish?
├── What's planned next?
├── What's blocking us?
├── What do we need from other teams?
└── Inter-team focus

FORMAT:
─────────────────────────────────────
Team A Rep:
├── "We finished the API endpoints"
├── "Starting front-end integration"
├── "Need Team B's auth service deployed"
└── Quick, specific

FOLLOW-UP:
─────────────────────────────────────
├── Blockers discussed offline
├── Not solved in meeting
├── Right people connect after
├── Meeting surfaces, doesn't solve
└── Efficient use of time

Dependency Management

Tracking Dependencies

DEPENDENCY MANAGEMENT
═════════════════════

VISUALIZATION:
─────────────────────────────────────
Dependency board:

Team A    │  Team B    │  Team C
──────────┼────────────┼──────────
Feature 1 │            │
    │     │            │
    └─────┼─────►      │ API
          │  Auth ─────┼───► Feature 3
          │            │

Dependencies visible

DEPENDENCY TYPES:
─────────────────────────────────────
├── Hard: Can't proceed without
├── Soft: Would benefit from
├── Time: Need by specific date
├── Order: Must complete first
└── Different urgency

TRACKING:
─────────────────────────────────────
For each dependency:
├── What is needed
├── From which team
├── By when
├── Status
├── Blocker if at risk
└── Complete visibility

REDUCING DEPENDENCIES:
─────────────────────────────────────
Best coordination = less coordination:
├── Team owns full slice
├── APIs for loose coupling
├── Clear interfaces
├── Feature flags for independence
├── Design for autonomy
└── Minimize need

Joint Planning

Cross-Team Planning

JOINT PLANNING
══════════════

PROGRAM INCREMENT PLANNING:
─────────────────────────────────────
Quarterly (or less):
├── All teams together
├── Present roadmaps
├── Identify dependencies
├── Negotiate commitments
├── Align on priorities
├── Shared understanding
└── Big picture alignment

FORMAT:
─────────────────────────────────────
Day 1:
├── Vision and context
├── Team breakouts for planning
├── Initial dependency mapping

Day 2:
├── Dependency resolution
├── Commitment setting
├── Risk identification
├── Final alignment
└── Intensive but valuable

OUTPUT:
─────────────────────────────────────
├── Team commitments
├── Dependency agreements
├── Program goals
├── Risk register
├── Aligned teams
└── Clear direction

LIGHTER ALTERNATIVES:
─────────────────────────────────────
If full PI planning too heavy:
├── Joint sprint planning kickoff
├── Pre-planning dependency review
├── Monthly sync on roadmap
├── Scale to need
└── Right-size the ceremony

Cross-Team Visibility

Shared Understanding

CROSS-TEAM VISIBILITY
═════════════════════

SHARED TOOLING:
─────────────────────────────────────
GitScrum setup:
├── All teams in same instance
├── Cross-team visibility
├── Dependencies tracked
├── Shared labels
├── One source of truth
└── Transparent

CROSS-TEAM DEMO:
─────────────────────────────────────
Regular show and tell:
├── All teams present
├── See what others built
├── Learn and align
├── Celebrate progress
├── Monthly or quarterly
└── Visibility into work

SHARED ROADMAP:
─────────────────────────────────────
├── Program-level view
├── All team work visible
├── Dependencies marked
├── Timeline visible
├── Stakeholder communication
└── Big picture

COMMUNICATION CHANNELS:
─────────────────────────────────────
├── Cross-team Slack/Teams channel
├── Announce when shipped
├── Flag blockers
├── Quick questions
├── Low-friction communication
└── Connected teams

GitScrum Configuration

Multi-Team Setup

GITSCRUM MULTI-TEAM
═══════════════════

PROJECT STRUCTURE:
─────────────────────────────────────
Option 1: Project per team
├── Team A project
├── Team B project
├── Team C project
├── Cross-link dependencies
└── Team autonomy

Option 2: Shared project
├── Single project
├── Labels for teams
├── Shared board
├── Tight collaboration
└── For very integrated teams

DEPENDENCY TRACKING:
─────────────────────────────────────
├── Label: dependency
├── Custom field: blocked-by-team
├── Link related tasks
├── Filter for dependencies
└── Visible blockers

PROGRAM VIEW:
─────────────────────────────────────
├── Cross-project reporting
├── All team progress
├── Epic-level view
├── Stakeholder dashboard
└── Aggregated view

Best Practices

For Multi-Team Coordination

Minimize dependencies — Design for autonomy

Visualize dependencies — Make them obvious

Regular sync — Scrum of Scrums

Joint planning — Align periodically

Shared tooling — One source of truth

Anti-Patterns

COORDINATION MISTAKES:
✗ Too many coordination meetings
✗ Hidden dependencies
✗ No shared visibility
✗ Over-coordinating
✗ Command and control
✗ Dependencies discovered late
✗ No joint planning
✗ Siloed teams