What would be the best way to visualize dependencies between 3 different teams in the same project?

At a point you can use any whiteboard tool, create a grid of teams (swim lanes) against sprints, and place the stories on it as post-its with connecting lines. Keep it simple!

AzureDevOps can do this in the Planning Views, and even supports teams with different Sprint or Iteration cadences which is nice…

BUT…

at a point I’d suggest that making it super simple and super easy to display and talk about dependencies is addressing the surface issue.

The underlying problem is how we can really get to the point where we don’t have dependencies, rather than apply technology to managing them.

Perhaps try:

– getting all three teams together in a room
– run an Ishikawa Fishbone analysis with “Dependencies slow us down” as a core problem
– see where you get to as the likely root cause and restated problem
– design an experiment to try and address that root cause
– measure the outcomes, and repeat…

Every dependency represents a risk of an error in communication, a delay, or both.
Try and eliminate that risk!