Back to Forum

Nexus Planning

Last post 12:27 pm October 9, 2023 by Thomas Owens
3 replies
ezgi kakaliçoğlu cihan
08:35 am October 9, 2023

Hi 

Do you have any best practice when to held nexus planning? Do you recommend to held the nexus planning after individual team sprint planning or before?

Looking forward to hear to best practices for dependency management.

Thanks in advance

Ian Mitchell
11:34 am October 9, 2023

The Nexus Guide says:

Each Scrum Team’s Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum.  

Hence these issues should be understood and brought to each Daily Scrum.

The Guide also says:

The Nexus Daily Scrum is not the only time Scrum Teams in the Nexus are allowed to adjust their plan. Cross-team communication can occur throughout the day

so if the timing of cross-team collaboration is presenting difficulty, ask why. In Scrum, regardless of whether it is at scale or otherwise, collaboration ought to be an ongoing dynamic.

 

Ian Mitchell
11:41 am October 9, 2023

NB this principle also applies to Nexus Sprint Planning. Teams ought to be able to collaborate on their own Sprint plans while their representatives also collaborate on a cross-team basis. There is no particular reason to stage-gate these things out, and every reason to try and avoid doing so.

Thomas Owens
12:27 pm October 9, 2023

Previous editions of the Nexus Guide (such as the January 2018 edition) were more explicit than the current (January 2021) edition.

In previous editions, Nexus Sprint Planning began with "appropriate representatives" from each Scrum Team reviewing the Product Backlog, crafting a Nexus Sprint Goal, selecting Product Backlog Items for each team, and then each team holding their Sprint Planning to craft a team Sprint Goal and plan their Sprint, with additional interactions between each team as necessary.

What Nexus describes is similar to the concepts of Sprint Planning 1 and Sprint Planning 2 from the LeSS framework.

However, the November 2020 Scrum Guide and January 2021 Nexus Guide removed some aspects that were considered prescriptive, including exactly how to organize the Sprint Planning. The teams that form a Nexus can continue to follow the previous descriptions or some of the LeSS practices or they can develop new ways of working and still be consistent with the LeSS framework.

Something to keep in mind - there are no best practices when working in a complex domain. I've had good luck with the concepts of Sprint Planning 1 and Sprint Planning 2 from LeSS, so in the absence of other suggestions or ideas that seem more appropriate for the context, that's where I'd start.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.