Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Risk Management, Scrum
Identifying and tracking dependencies across multiple scrum teams working
Network:2265



Would like to hear experiences from community members on identifying and tracking dependencies across multiple scrum teams. We can all agree that if a dependency is identified in the current sprint, then it is too late. How can we capture dependencies earlier?
Sort By:
Network:1851



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.
...
1 reply by Andrew Craig
Mar 24, 2019 11:37 AM
Andrew Craig
...
Thanks, Sergio. Yes, great points. It is solely not software related, but having the right individuals involved to drive and influence the efforts and actions.

In my scenario, I have done such that. Ensured the BA's are involved and integral to the process.
Network:1506



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
...
1 reply by Andrew Craig
Mar 24, 2019 11:45 AM
Andrew Craig
...
Thanks, Kiron. I love that inclusion into DoR. I have set up some cross-team activities, but I am absolutely going to suggest that and discuss incorporating into our working agreement. Thanks!
Network:299



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
...
1 reply by Andrew Craig
Mar 24, 2019 11:48 AM
Andrew Craig
...
Great points, Keith. A visual representation of features, stories, and dependencies would be absolutely valuable. I would like to try to incorporate that a bit more. Diagrams seem to be not given their due! As of now, we highlight through linking in the tool. That way either team will see the link, whether a predecessor or successor.
Network:2265



Mar 17, 2019 9:39 AM
Replying to Sergio Luis Conte
...
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.
Thanks, Sergio. Yes, great points. It is solely not software related, but having the right individuals involved to drive and influence the efforts and actions.

In my scenario, I have done such that. Ensured the BA's are involved and integral to the process.
Network:2265



Mar 17, 2019 10:27 AM
Replying to Kiron Bondale
...
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
Thanks, Kiron. I love that inclusion into DoR. I have set up some cross-team activities, but I am absolutely going to suggest that and discuss incorporating into our working agreement. Thanks!
Network:2265



Mar 17, 2019 11:47 PM
Replying to Keith Novak
...
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
Great points, Keith. A visual representation of features, stories, and dependencies would be absolutely valuable. I would like to try to incorporate that a bit more. Diagrams seem to be not given their due! As of now, we highlight through linking in the tool. That way either team will see the link, whether a predecessor or successor.
Network:7163



Visualisation tools including GANT charts help in quickly identifying dependencies

Please login or join to reply

Content ID:
ADVERTISEMENTS

Mediocrity knows nothing higher than itself, but talent instantly recognizes genius.

- Arthur Conan Doyle

ADVERTISEMENT

Sponsors