Cross-Team Dependency Language: English Collocations
Cross-team dependencies are one of the biggest sources of delivery risk in scaled engineering organisations. From identifying and tracking dependencies to resolving blockers and escalating risks, programme managers and tech leads need precise vocabulary. This exercise covers the collocations used in PI planning, dependency boards, and ART sync meetings.
0 / 5 completed
1 / 5
The delivery manager asked each squad to ___ cross-team dependencies in the quarterly planning session.
Identify dependencies is the standard programme management collocation — dependencies are 'identified' as a formal step in planning. 'Flag' is used when drawing attention to a specific risk; 'list' and 'find' are more mechanical. 'Identify dependencies' is the precise phrase used in PI planning, SAFe, and cross-team roadmap sessions.
2 / 5
The programme manager created a dependency board to ___ the status of all cross-team commitments.
Track dependencies is the standard delivery management collocation — dependencies are 'tracked' on boards and in tools to maintain visibility. 'Monitor' implies watching for changes; 'record' is the initial capture action; 'manage' is the broader process. 'Track' is the precise verb for maintaining an up-to-date status view of each dependency.
3 / 5
The teams met to ___ the blocking dependency between the data platform and the analytics squad.
Resolve the dependency is the natural cross-team coordination collocation — dependencies are 'resolved' when the blocking condition is removed and work can proceed. 'Fix' is informal; 'address' implies discussing without necessarily solving; 'clear' is also used informally. 'Resolve' is the standard verb in programme management dependency tracking.
4 / 5
The engineering lead agreed to ___ the dependency risk to the programme manager before the sprint review.
Escalate the risk is the precise dependency management collocation — unresolved dependency risks are 'escalated' to programme management when they cannot be resolved at team level. 'Raise' is also used; 'report' is informational; 'communicate' is too broad. 'Escalate' implies invoking authority to resolve a cross-team blocker.
5 / 5
During the ART sync, teams were encouraged to ___ any dependencies that could affect the release train.
Surface dependencies is the standard SAFe and programme-level collocation — 'surfacing' means actively bringing hidden or poorly visible dependencies into the group's awareness. 'Flag' also works for drawing attention; 'highlight' and 'mention' are informal. 'Surface' is the preferred verb in large-scale Agile and PI planning vocabulary.