Alignment & delivery

Cross-team dependency map

Each team, what it expects from the others and when. Crossed arrows are the risks.

When. Delivery rarely slows down because of one team, but because of what it is waiting for from the others.

Duration
2 h
Participants
One representative per team
Output
Dated dependencies, named risks
Stage
Scale-up · Mature
Team ATeam BTeam CTeam DTeam ATeam BTeam CTeam D
Open in FigJamFind the right sequence

In FigJam: File → Duplicate to your drafts, then keep this workshop's section. Get the file on Figma Community

Filled example

Team ATeam BTeam CTeam DTeam ATeam BTeam CTeam Dneeds the newdispatch API beforeoffline sync, sprint3needs partscatalogue IDsstable, sprint 2needs activationevents instrumented,sprint 1Team A = Field appsquadneeds photo uploadfix merged first,sprint 1needs the invoicingstatus field, sprint4needs the churncohort export,sprint 2Team B = Office websquadneeds interventionmodel frozen, sprint2needs customeraccount mappingscreen, sprint 3nothing this PITeam C =Integrations squadneeds the same-daylogging event,sprint 1needs dispatchersession tracking,sprint 2needs sync errorlogs in thewarehouse, sprint 4Team D = Dataanalyst

Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.

Scale-up Fieldnote with three squads (Field app, Office web, Integrations) and the data analyst: the offline mode and the Pennylane integration both slipped because of what each squad was waiting for.

What the team took away

Six of the nine arrows land on the Field app squad in sprints 1 and 2. They swap the parts scan feature for sprint 4 and clear the model freeze first.

How to run it

Preparation

Agenda

  1. 10 min
    Rules of the grid
    Explain the reading: the cell at row A, column B is what A must deliver to B. One sticky per dependency, with a date.
  2. 20 min
    Write your needs
    Each rep writes what their team needs from every other team, in the receiving column. Silent, 20 minutes.
  3. 40 min
    Confirm or contest
    Walk the grid team by team. The giving team says yes with a date, or no with a reason. Mark disputed cells in red.
  4. 20 min
    Find the crossings
    Look for pairs where A waits for B and B waits for A. Each crossing is a risk: name it and pick one of the two to go first.
  5. 30 min
    Escalate and close
    List the red cells nobody can settle in the room. Assign each to a named person with a 48-hour deadline. Photograph the grid.

Pitfalls

Afterwards

The grid becomes the dependency row of the program board, or a standing item in the weekly sync. Revisit it every sprint: dependencies that keep reappearing point to a team boundary that needs to move.

Related workshops

Back to the compassAll workshopsVersion française