Nexus framework

LeSS or Scrum of Scrum are not the only existing frameworks to manage multiple Scrum teams. Ken Schwaber, who has already co-founded Scrum, also wanted to offer his framework to manage between 3 and 9 Scrum teams together called Nexus.

The Nexus allows teams to work on the same Product Backlog as you could also see with LeSS. This framework is in total coherence with Scrum and should not confuse those who use it.

Nexus integration team

The Nexus adds a team across the Scrum teams who will have the roles of coordinating, coaching and supervising the setting up of this framework. The team will consist of a Scrum Master, a Product Owner and Nexus Integration Team Members.

However, the Scrum Master can also be Scrum Master of one or more Scrum teams in parallel. An Agile coach could also take on this role of Scrum Master of integration team because the roles are relatively close.

Members of the Nexus Integration Team can work in any Scrum team if necessary. However, they will have to prioritize their Nexus integrator roles in relation to this secondary role.

This team will aim to avoid all potential inter-team problems. They will make every effort to ensure harmony between the teams.

One Product Owner

The Nexus is a framework that works on a single backlog. It will be part of the integration team and will be external to Scrum teams.

The organization of the Nexus framework

This framework is organized differently from other frameworks and a classic Scrum.

Here is the official diagram of his organization:

The Nexus is quite flexible in terms of team building. It is possible to build a team that will be adapted to be specific.

Refinement Backlog: The team will refine the product backlog together as in a classic Refinement Product Backlog.

Sprint Planning Nexus: Teams will all decide to split user stories between each team.

Sprint planning: Each team will then do a classic sprint schedule with user stories although the aura will have recovered. The goal of the teams will be based on the overall Nexus goal of all teams.

Work in common: In this Scrum framework, the teams worked on the common spaces in order to regularly share the work between them.

Daily Scrum Nexus: Each team will be represented by two ambassadors who will present the work done to all other ambassadors, once a day. They will share a maximum of information between the teams (even the problems encountered)

Daily Scrum: Next to the Daily Scrum Nexus, the teams come together to talk about the work and the problem potentially accounted. The ambassadors will explain the problems explained during the Daily Scrum Nexus in order to settle them as soon as possible.

Sprint Review Nexus: all teams meet with the product manager for the presentation of the entire product. Backlog adjustments may be purposed at this time.

Nexus Retrospective: The ambassadors of each team and the integration team will be together to do a global retrospective of the Sprint that ends.

Retrospective: When the Nexus retrospective is over, the teams do the classic retrospective.

Conclusion Nexus

This framework is close to the LeSS framework but offers this notion of stronger support through this cross-functional Nexus integration team.

If this framework is a good working basis, stay Agile in your thoughts and feel free to adapt it to your context to make it more efficient.