Nexus Sprint Backlog contains all PBI's?
I'm in the process of reading "The Nexus Framework for scaling Scrum" and it says that the Nexus Sprint Backlog contains only the PBI's that have cross dependencies or integration issues and not PBI's that do not have these features. The Nexus guide indicates that it is a composite of all team sprint backlogs. So these two ideas seem to be at odds and just wondered if someone could clarify please.
In Scrum, whenever in any doubt, it is the information in the Scrum Guide which holds. I think that the same principle will need be observed regarding Nexus, i.e. go by what it says in the Nexus Guide.
I suspect the point being made in the book is that a Nexus Sprint Backlog ought to reveal dependencies and integration issues. Providing this transparency is the actual purpose of the thing. PBI's free of such concerns ought to be handled at Development Team level.
Thanks Ian, I guess you are right but I find it very strange and confusing, the statement reads
"The Nexus Sprint Backlog contains the PBIs that have cross team dependencies or potential integration issues. It does not contain PBIs that have no dependencies, nor does it contain tasks from the individual Scrum Team Sprint Backlogs. It is used to highlight dependencies and the flow of work during the Sprint...."