Skip to main content

Nexus Sprint planning participation

Last post 03:10 pm April 10, 2018 by Andrzej Engelking
4 replies
08:48 am February 10, 2016

Hi all,

I was reading the Nexus guide and the following sentence was a bit unclear to me:

"To begin Nexus Sprint Planning, appropriate representatives from each Scrum Team validate and make adjustments to the ordering of the work as created during Refinement events. All members of the Scrum Teams should participate to minimize communication issues"

So all members of the Scrum teams participate in the Nexus Sprint Planning, but at the beginning of this meeting appropriate representatives from each Scrum Team validate and make adjustments to the ordering of the work as created during Refinement events?

Cheers, Patt


11:07 am February 10, 2016

Perhaps it is a bit unclear written in the Nexus Guide but in the guide is also state that:

"The first part of cross-team Refinement should be spent decomposing Product Backlog items into enough detail in order to understand which teams might deliver them, and in what sequence over upcoming Sprints."

I would say before the Nexus Sprint Planning starts, the appropriate representatives from each Scrum Team comes together and validate and make adjustments to the ordering of the work as created during Refinement events.


11:07 am February 10, 2016

Think of everyone as being there, and of the teams needing to self-organise so planning can be effective. To begin with, each team will need to self-organise its representation in establishing Product Backlog order. The most important step in planning at scale is to get integration dependencies under control and the ordering of work greatly influences this.


11:17 am February 10, 2016

> I would say before the Nexus Sprint Planning starts, the appropriate representatives
> from each Scrum Team comes together and validate and make adjustments to the
> ordering of the work as created during Refinement events.

They might do that *as well*, during a further Refinement event (as the guide says, "At the scale of Nexus there are many levels of refinement"). However, the re-ordering and validation of work is also a specific activity to be conducted at the beginning of Nexus Sprint Planning, and as part of it. Getting dependencies under control is too important for this step to be elided. Clearly the more conscientiously Refinement is performed, the less controversial the order of work should be during Planning.


07:59 am April 10, 2018

I think it's not complicated :-)

Here we can read: 

"Effective Nexus Sprint Planning occurs in 2 steps:

1. Each team in the Nexus selects their work for the Sprint. This is a collaborative activity with representation from each Scrum Team.

2. Each team performs their normal Sprint Planning process. This occurs per Scrum Team and can happen in parallel."


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.