Confusion related to product backlog refinement in Nexus

Last post 02:12 pm November 18, 2018 by vishal Rajadhyaksha

No replies yet

02:12 pm November 18, 2018

1. Nexus guide mentions- The number, frequency, duration and attendance of Refinement is based on the dependencies and uncertainty inherent in the Product Backlog.

Does this mean , there is no rule that only representatives from each team should be present during refinement? It can be either representatives or all team members?

Also, unlike Nexus Sprint Planning or Nexus Daily Scrum, why the refinement meeting is simply mentioned as Refinement in Nexus guide?

2. As per the Nexus guide- Refinement meeting helps the Scrum Teams forecast which team will deliver which Product Backlog items,

So, suppose we have identified team A will work on User story 1 , 2 , 3, 4, 5 and 6 .

In which bucket / sprint backlog these user stories will go after this identification?

Team A maintains Sprint Backlog which contains user stories of current sprint and not future sprint.

So, my question is does each also has it's own product 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.