Nexus: Core concepts and features

Nexus, like LeSS, uses Scrum as a building block for its framework. Nexus utilizes the Scrum concepts that we are familiar with, thereby making it easier to adopt within organizations that already use Scrum.

A Nexus is normally formed with a group of three to nine Scrum teams, and the Nexus framework supports the concept of multiple scrum teams working from a common backlog to create an integrated product.

As with Scrum, Nexus supports the self-organization of teams where they can determine which of their members should be assigned to various tasks. However, the Nexus framework focuses more on the interdependency and collaboration among multiple scrum teams who are working towards delivering an integrated increment with each sprint.

Unlike LeSS, where the team is responsible for the coordination of their own work, Nexus takes this task from the teams and ‘centralizes’ coordination through the Nexus Integration Team (NIT). The NIT manages the coordination and collaboration between teams in the Nexus. Although each scrum team is still responsible for integrating their work on a regular basis, the Nexus Integration Team can offer support to teams as issues arise.

For more information on the Nexus framework, see Scaling Scrum with Nexus.

Let’s move on to the next step in which we look at Nexus roles, team structures, and events.