Scaled Professional Scrum and Nexus – Nexus Artefacts

The Nexus framework extends the artefacts from the Scrum framework in a number of ways.

Product Backlog

There is a single Product Backlog for the entire Nexus and all of its Scrum Teams. The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering.

At scale, the Product Backlog must be understood at a level where dependencies can be detected and minimized in advance of the actual implementation work to deliver the items in a future Sprint. This is to keep the Scrum Teams in the Nexus as autonomous and independent as possible during a Sprint. That way they can work on delivering functionality without excessive reliance on other teams which could slow work and lead to a reduced ownership by the individual teams.

This often means more work has to be done up front to analyse and decompose Product Backlog Items. This work will be done as part of the Product Backlog Refinement event. Product Backlog items may be considered ready for the Nexus Sprint Planning event when they can be selected to be done by Scrum Teams with no or minimal dependencies on other Scrum Teams.

Nexus Goal

During the Nexus Sprint Planning event, a goal for the entire Sprint is formulated. This is called the Nexus Goal. It is the sum of all the work and Sprint Goals of the individual Scrum Teams within the Nexus.

The Nexus should demonstrate the functionality that they developed to achieve the Nexus Goal at the Nexus Sprint Review.

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 and visualise dependencies and the flow of work during the Sprint. It is updated at least daily, often as part of the Nexus Daily Scrum.

Integrated Increment

The Integrated Increment represents the sum of all integrated work completed by a Nexus. The Integrated Increment must be potentially releasable which means it must meet the definition of “Done” for the Nexus. The Integrated Increment is inspected at the Nexus Sprint Review.

Next post: The Nexus Integration Team –>

<– Previous post: The Nexus Framework

Index – Scaled Professional Scrum And Nexus – The Definitive Guide

mm

The Scrum Master is Simon Kneafsey. Simon is a Professional Scrum Trainer with Scrum.org, the home of Scrum run by Scrum co-creator, Ken Schwaber. Simon offers Professional Scrum Certification training courses globally and works with clients to introduce Scrum to their organisations.


Share this Post

Comments 2

    1. mm Post
      Author

Leave a Reply

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