Nexus Sprint Goal

Nexus Sprint Planning

The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams within a Nexus for a single Sprint. Appropriate representatives from each Scrum Team and the Product Owner meet to plan the Sprint.

The result of Nexus Sprint Planning is:

● a Nexus Sprint Goal that aligns with the Product Goal and describes the purpose that will be achieved by the Nexus during the Sprint

● a Sprint Goal for each Scrum Team that aligns with the Nexus Sprint Goal

● a single Nexus Sprint Backlog that represents the work of the Nexus toward the Nexus Sprint Goal and makes cross-team dependencies transparent

● A Sprint Backlog for each Scrum Team, which makes transparent the work they will do in support of the Nexus Sprint Goal

The NIT creates the Nexus SG and ensures that it is aligned with the PG. 

Who defines Nexus Sprint Goal?

Who will do the work and commit to achieving it?

Scott Anthony Keatinge Thank you very much for the clarification.

Ian Mitchell,  Thanks for asking the question, but i am novice in this subject. I would recommend you to please open a NEW thread if you have a question or any doubt to clarify. We have a lots of qualified guru's on this forum to respond back. 

Ian Mitchell,  Thanks for asking the question, but i am novice in this subject. I would recommend you to please open a NEW thread if you have a question or any doubt to clarify. We have a lots of qualified guru's on this forum to respond back. 

LOL

@Ajay Sood, you should have looked at Ian's profile before making that comment, as he is one of this sites gurus, and was trying to prompt you to come up with your own answer, which is what scrum masters do when confronted by scrum team situations.  :-)

Bear in mind that a Nexus Sprint Goal is a commitment, and commitments are best made by the people who actually do the work.

Scott Anthony Keatinge Unfortunately, I am a techie, for me everything is 0 or 1. In my world, there is nothing like my own answer, it's either a universally right answer or wrong answer. Moreover, i believe if i need to come up with my own answer for everything then i don't need a framework to follow or validate my skills against certificates that cost me $$$.

For me framework provides best practices, it's upto the client to stick to it or not but it has to provide a clear cut path to follow for best results.

I understand Nexus is still quite new (as compare to Scrum) but i was hoping that these basic questions would have been asked by current Nexus follows in 5+ years of it's existence, which is not the case.

But i appreciate your time and efforts you put to explain not only the ans but why that is the right ans.

Bear in mind that a Nexus Sprint Goal is a commitment, and commitments are best made by the people who actually do the work.

Ian Mitchell Thanks for your ans. What i understand from The Nexus Guide is 'NIT does the coaching, consulting and highlighting awareness of dependencies and cross-team issues'. Also, 'Scrum teams addresses integration issues'. That gives me a sense that only Scrum team/s does the actual work, which means Scrum teams are responsible for setting the Nexus Sprint Goal.

That actually proves the below ans from Scott Anthony Keatinge wrong.

The NIT creates the Nexus SG and ensures that it is aligned with the PG. 

@Ajay Sood, the NIT is made up of the PO, one of the SMs, and appropriate members of each scrum team depending upon the event, so how can my answer be incorrect? 

Please review the Nexus Sprint Planning from the Nexus Guide again, in order to aid your understanding. 

Please remember that the scrum framework does not tell you how to do things, it simply tells you what should be done in order to implement scrum.  Even the scrum guide itself states that it is purposely incomplete. 

I would say that the majority of people on this site are techies. 

According to your profile, you have already passed PSM1 and PSPO1, so you should know exactly what I meant by my comment on why Ian asked you a question. 

Scott Anthony Keatinge Actually i personally agree with your answer and the explanation behind it, but Ian Mitchell responses made it look wrong.

I understand NIT = PO + SM of NIT + Other members that may include some external resources, but then The Nexus Guide states 'NIT does the coaching, consulting and highlighting awareness of dependencies and cross-team issues'.  and 'Scrum teams addresses integration issues'. Which means actual work is carried out by Scrum Teams in Nexus.

Ian Mitchell responses were 

Who will do the work and commit to achieving it?

Bear in mind that a Nexus Sprint Goal is a commitment, and commitments are best made by the people who actually do the work.

People who actually do the work = Scrum Teams

Your Response = NIT

Hope this may summarise, how Ian Mitchell responses made your response look wrong.

Think of it this way:  Nexus is still scrum. 

Scrum = scrum team creates sprint goal (aligned with product goal)

Nexus = NIT creates Nexus sprint goal (aligned with product goal) & each scrum team creates their own sprint goal (aligned with Nexus sprint goal)

Yes, the scrum teams do the work and the NIT manages the dependencies, etc.; however, as the NIT is made up of scrum team members, the NIT creates the NSB.