How do you manage dependencies between Scrum teams?

Cross-team dependency management is the biggest challenge in scaled Agile. Approaches: (1) Identify dependencies early — during backlog refinement, tag stories with team dependencies. Use a dependency visualization tool (Jira, Miro dependency boards, or physical big visible charts); (2) Inter-team backlog alignment — teams refine related stories together, ensuring all prerequisites are planned in the same or earlier Sprint; (3) Scrum of Scrums — Scrum Masters or tech leads from dependent teams meet 2-3x/week to surface and resolve cross-team blockers; (4) Feature teams over component teams — redesign teams to be cross-functional end-to-end feature teams rather than component-specialized. Eliminates most dependencies by design; (5) PI Planning (SAFe) — the quarterly event explicitly identifies and risks cross-team dependencies using the Program Board (a physical/digital board showing team tracks and dependency arrows); (6) Architecture runway — invest in shared technical foundations (APIs, shared services) that reduce coupling; (7) Communities of Practice — cross-team technical guilds create consistency in interfaces, reducing integration friction; (8) Kanban + FIFO — dependent teams commit to FIFO processing of cross-team requests to prevent starvation.