Scaled Scrum

About

Best guided by Nexus Guide, which is a separate Scrum Guide, for scaled scrum.

• Means having multiple Scrum Teams working on ONE Product Backlog.

• And they work to fulfill the same Product Goal.

• ONE PO for all Scrum Teams.

• There are multiple Sprint Backlogs each Sprint.

• There can be multiple Definitions of Done.

• There must be ONE integrated Increment at each Sprint.

• Multiple Scrum Master roles which can be occupied by 1 or more Scrum Masters.

The Teams Sprints don't have to be synchronized.

Code can be integrated frequently during the Sprint.

The huge challenge of working with multiple teams is:

• DEPENDENCIES.

Nexus Integration Team

For this the Nexus, prescribes the Nexus Integration Team. Composed by:

• One PO

• One Scrum Master

  • Which might be Scrum Master from Scrum Teams.

• And the Nexus integration team

  • Which might be members from the Scrum Teams.

This team has the role of resolving dependencies and integration issues. Making sure that the entire team is able to deliver the integrated Increment by the end of the Sprint.

This Team is also responsible for defining the Definition of Done, to be applied to the integrated Increment, and this is a MINIMUM.

All Scrum Teams MUST adhere to this Definition of Done.

However this doesn't mean that all Scrum Teams must follow the exactly same Definition of Done, meaning that they can make more stringent definitions, but all have the minimum definition defined by the Integration Team.

Nexus Events

It shares the same events as Scrum, with the exception that the:

• Nexus Sprint Planning

• Nexus Daily Scrums

• Nexus Sprint Retrospective

Complements their "Scrum Versions", with the main goal of handling dependencies between the Scrum Teams.

And the:

• Nexus Sprint Review

Replaces the "Scrum Sprint Review".