What would we do if the Nexus sprint planning have too many dependencies and cannot resolve

Last post 07:55 am April 29, 2021
by Scott Anthony Keatinge
3 replies
11:42 pm April 28, 2021

Hi everyone,

I got a concern and I'm not sure how to handle it as a Scrum master. That would be great to have your help, Thanks so much!

Like in the Nexus sprint planning, there are many dependencies and hard for teams to choose the work they could pull into their individual teams for the next Sprint. No matter how we reorganize the backlog items, they continually find more or new dependencies. 
Should we Extend the sprint length OR re-organize team members between the teams to eliminate cross-team dependencies or The Nexus Integration Team should complete the dependent work ahead of the Sprint for the teams OR reorder Product Backlog Items so that you can accommodate the dependency





05:18 am April 29, 2021

How about encouraging people to self-organize into Scrum Teams so dependencies are minimized?

07:07 am April 29, 2021

Thanks for your response Ian, I agree that we should encourage people to self-organize into teams if we cannot resolve it! but if we identify them right in the Nexus sprint planning, is there a good solution to resolve/minimize in advance.!




07:55 am April 29, 2021

This is why the Cross Team Refinement event comes before the Nexus Sprint Planning event, as it is the main event where dependencies are identified and resolved.  Of course, dependencies can be identified and reported at any time during the sprint too. 

The Nexus practices have a wealth of knowledge that should help you to improve your Nexus skills:-  https://www.scrum.org/scaled-professional-scrum-nexus-practices