Back to Forum

The contents of the "The Nexus Framework for scaling scrum" are inconsistent with the Nexus Guide.

Last post 05:13 am July 15, 2018 by Ching-Pei Li
No replies yet
Ching-Pei Li
05:13 am July 15, 2018

After reading the book "The Nexus Framework for scaling scrum", some of the content was found to be different from Nexus Guide.

Although in the Scrum circle, different views are normal. But these two documents are all from scrum.org, if there is inconsistent content, a bit unreasonable.



The most notable of these include:

1. The ideal number of Scrum members, or the ideal number of Nexus teams.

The recommendations based on Scrum Guide and Nexus Guide are 3~9 (6 +- 3), but the book recommends 5~9 (7 +-  2)



2. There are also different definitions for the Nexus Sprint Backlog.

Nexus guide:  A Nexus Sprint Backlog is the composite to Product Backlog items from the sprint backlogs of the individual

Scrum teams.

The Book: Only items that have dependencies.

 

However, I am not a native speaker of English, perhaps I misunderstood their meaning.

Any input would be appreciated.

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.