Identifying and tracking dependencies across multiple scrum teams working

In my case, along the years, it will be solved thanks the use of a role which is solution accountable: the business analyst. On the other side, that will be solve by using something that is critical mainly in Agile: systemic theory applied to organizations. That is the macro but you need the tools and practices to do that. In this case, there are lot of tools (any type of tools, not software only) outside there that could help you. In my actual work place I was in charge "to sell" this way of work.

Andrew -

that is the benefit of story mapping (early in the life of the project/release) and look ahead modeling.

The former will give teams a chance to start to identify the connections between work items whereas the latter will give them a chance to further explore those dependencies in advance of when they would bring the work items into a sprint. In fact, for most of our teams, their DoR includes "key dependencies identified and planned for".

Kiron

Andrew,
This is where I use my own basic network diagram as a tool whether or not anyone else cares I'm creating them. Forcing myself to diagram a problem at a high level requires significant thinking about it to in order to create that basic abstract. When there are multiple story-lines running concurrently, I am all for creating a map of their planned intersections. It's far easier to follow the plot.

Keith