Back to Forum

Nexus sprint planning

Last post 02:43 pm July 26, 2018 by Vinod Asokan
2 replies
Rajat Krishna Shrestha
07:13 pm July 23, 2018

Hello,

When different scrum teams are working on a single product,  would the PO meeting the representatives from each team to compose the Sprint Goal and select items from the PB so that the representative can work with its team again to create their separate sprint backlog or all the team members converging at the same time to check the PB so that they can co-ordinate dependencies and create their SB would be a better option for Nexus Sprint planning?

Thanks.

Ian Mitchell
07:46 pm July 23, 2018

From your reading of the Nexus Guide, might it be possible to do both?

Vinod Asokan
09:25 am July 26, 2018

From actual practice in my nexus getting all the team into the sprint planning has helped teams to co-ordinate better and sort out depedencies , it will also help to reduce the  handoff of the teams representative again discussing with their teams to create their sprint backlog .

 

 

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.