Nexus framework

The Nexus framework (Nexus) is a framework for developing and sustaining scaled product and software delivery initiatives, using Scrum as a building block.

Nexus was developed by Ken Schwaber and Scrum.org, it is offered freely and described in the Nexus Guide.

Definition of Nexus

Nexus is defined as “a framework consisting of roles, events, artefacts, and rules that bind and weave together the work of approximately three to nine Scrum teams working on a single Product backlog to build an integrated increment that meets a goal”.

Note: This article is currently being finalised, please return too to see the finished version!

Transparency

Similar to the Scrum framework, on which Nexus is built, Nexus is based on the idea of transparency.

Definition of “Done”

Within Nexus, the “Nexus Integration Team” is responsible for defining a common specification of “Done” which is used across all of the Scrum teams within the Nexus.

The goal of each Nexus Sprint is to create an integrated, usable and potentially releasable increment of work.

Notes

Nexus is one of several frameworks available to assist in developing and sustaining scaled product and software delivery initiatives.

As with the Scrum framework, the Nexus roles, artefacts, events and rules are considered immutable. That is to say, whilst implementing only parts of Nexus is possible, the result is not Nexus.

For a more comprehensive approach to scaling and organisational agility, please refer to the XSCALE framework for organisational agility.

For more information on the Nexus framework …

Please refer to the Scrum.org website and the Nexus Guide.

This page is part of the ÆGILITY Agile Lexicon
Please advise any updates or corrections by emailing the information to lexicon@aegility.ch
Whilst every effort is made to ensure correctness of the information, ÆGILITY and Lyaeus GmbH take no responsibility for the accuracy of the information or its use