16 June 2021

The Nexus framework

The Nexus framework :

  • A Nexus is a group of approximately three to nine Scrum Teams that work together to deliver a single Product; it is a connection between people and things.
  • A Nexus has a single Product Owner who manages a single Product Backlog from which the Scrum Teams work.
  • Scrum.org has introduced the Nexus framework for this purpose with some difference with scaled Scrum.
  • Nexus contains 3-9 Scrum Teams and a Nexus Integration Team.

Nexus integration :

  • The Nexus Integration Team is responsible for a Definition of Done that can be applied to the Integrated Increment developed each Sprint.
  • The Nexus Integration Team consists of professionals who are skilled in the use of tools, various practices, and the general field of systems engineering. Nexus Integration Team Members ensure the Scrum Teams within the Nexus understand and implement the practices and tools needed to detect dependencies, and frequently integrate all artifacts. Nexus Integration Team Members are responsible for coaching and guiding the Scrum Teams in a Nexus to acquire, implement, and learn these practices and tools.
  • Additionally, the Nexus Integration Team coaches the individual Scrum Teams on the necessary development, infrastructural, or architectural standards required by the organization to ensure the development of quality Integrated Increments.

Nexus Increment :

  • The Integrated Increment represents the current sum of all integrated work completed by a Nexus toward the Product Goal. The Integrated Increment is inspected at the Nexus Sprint Review, but may be delivered to stakeholders before the end of the Sprint. The Integrated Increment must meet the Definition of Done.
  • The commitment for the Integrated Increment is the Definition of Done,which defines the state of the integrated work when it meets the quality and measures required for the product.
  • The Increment is done only when integrated, valuable, and usable.

Nexus Definition of Done :

  • All Scrum Teams within the Nexus must define and adhere to this Definition of Done.
  • Individual Scrum Teams self-manage to achieve this state.
  • They may choose to apply a more stringent Definition of Done within their own teams, but cannot apply less rigorous criteria than agreed for the Integrated Increment.

Nexus transparency :

  • Decisions made based on the state of artifacts are only as effective as the level of artifact transparency.
  • Incomplete or partial information will lead to incorrect or flawed decisions.
  • The impact of those decisions can be magnified at the scale of Nexus.

Nexus Sprint Backlog :

  • A Nexus Sprint Backlog is the composite of all Product Backlog items from the Sprint Backlogs of the individual Scrum Teams. It is used to highlight dependencies and the flow of work during the Sprint. It is updated at least daily, often as part of the Nexus Daily Scrum.

Nexus Daily Scrum :

  • During the Nexus Daily Scrum, attendees should focus on each team’s impact on the Integrated Increment and discuss:
    Was the previous day’s work successfully integrated? If not, why not?
    What new dependencies have been identified?
    What information needs to be shared across teams in the Nexus?

Nexus Sprint Review :

  • Only one Sprint Review for all Teams.
  • However, the integrated Increment as a whole, which contains all Teams’ outputs is used to demonstrate in the Sprint Review.

More informations for the Scrum PSD certification here.

Leave a Reply

Your email address will not be published. Required fields are marked *