Cross-Team Sync

Purpose

The Cross-Team Sync creates a regular, time-boxed forum for representatives from multiple teams to surface dependencies, share progress on shared initiatives, resolve blockers, and align on priorities. It prevents silos from forming and catches misalignments early.

At a glance

How to run

1. Open (3 min): Facilitator states the purpose and reviews the agenda: updates, dependencies, blockers, decisions needed.
2. Team updates (15 min): Each team representative shares in 2–3 minutes: What shipped since last sync? What is in progress? Any changes in priority?
3. Dependency review (10 min): Walk through the shared dependency board. For each: Is it on track? Is any team blocked by another? Flag new dependencies.
4. Blocker resolution (10 min): For flagged blockers, assign an owner and agree on a resolution timeline. If a blocker needs more discussion, schedule a separate session.
5. Decisions & announcements (5 min): Capture any decisions made. Share announcements that affect multiple teams.
6. Close (2 min): Confirm next sync date. Share action items.

Materials needed

• Shared dependency board (spreadsheet, Jira board, or physical wall)
• Timer
• Shared notes document
• Video conference setup for remote participants

Pitfalls & common mistakes

• Status reporting without interaction: If teams only broadcast, there is no alignment. Encourage questions and discussion.
• Too many attendees: Keep it to 2–3 reps per team. Full-team attendance makes the meeting unwieldy.
• No dependency tracking: Without a visible board, dependencies are forgotten between syncs.
• Running over time: Strict time-boxing is essential. Park deep discussions for follow-up.

Inclusion & accessibility

• Rotate the facilitator role across teams.
• Share the agenda and dependency board 24 hours in advance so people can prepare.
• Record the session or share detailed notes for those who cannot attend.
• Use async updates (e.g., a pre-sync form) to reduce live time for status.

Variations

• Async-first sync: Teams post written updates before the meeting; live time is only for dependencies and blockers.
• Scrum of Scrums: Adapted for agile teams, with a focus on sprint-level coordination.
• Visual dependency map: Use a large physical or digital map showing inter-team flows.

When NOT to use this

• When there are no real cross-team dependencies — the meeting will feel like overhead.
• When teams have very different cadences and a shared sync frequency does not fit.
• When it replaces direct team-to-team communication — it should complement, not replace.

Source & further reading

• Jeff Sutherland, *Scrum: The Art of Doing Twice the Work in Half the Time* (Crown Business, 2014)
• SAFe (Scaled Agile Framework) — scaledagileframework.com
• Team Topologies — Matthew Skelton & Manuel Pais (IT Revolution, 2019)