In this chapter, you learned how Ken Schwaber, through his company, Scrum.org, implement Scrum scaling practices via their Nexus Framework. The Nexus Framework does not replace the Scrum Framework; rather, it extends Scrum to organize and coordinate the work of three to nine Scrum Teams in order to deliver Integrated Increments of value across each planned Sprint.
You have learned that Nexus modifies one artifact, adds two additional artifacts, adds five new events, and adds one new role. Artifacts provide transparency to help avoid bad decision-making from having bad information. Events guide the flow of work across each Sprint. The roles define the responsibilities of the Nexus integration and Scrum Teams.
As with Scrum, there is only one Product backlog for the entire Nexus, from which all the underlying Scrum Teams pull work. Since there is only one only Product backlog, there is one Product Owner who is ultimately accountable for the value that's identified...