Nexus framework : Events

Nexus Definition

• 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.
• The Nexus framework defines the Accountabilities, Events, and Artifacts that bind and weave together the work of the Scrum Teams in a Nexus.
• Nexus builds upon Scrum’s foundation, and its parts will be familiar to those who have used Scrum.
  • It minimally extends the Scrum framework only where absolutely necessary to enable multiple teams to work from a single Product Backlog to build an Integrated Increment that meets a goal.

Nexus Events purpose

• Nexus adds to or extends the Events defined by Scrum.
  • The duration of Nexus events is guided by the length of the corresponding Events in the Scrum Guide.
    • They are timeboxed in addition to their corresponding Scrum Events.
  • At scale, it may not be practical for all members of the Nexus to participate to share information or to come to an agreement.
    • Except where noted, Nexus events are attended by whichever members of the Nexus are needed to achieve the intended outcome of the event most effectively.

Nexus events

• Sprint
• Cross-Team Refinement
• Nexus Sprint Planning
• Nexus Daily Scrum
• Nexus Sprint Review
• Nexus Sprint Retrospective

Sprint

• A Sprint in Nexus is the same as in the Scrum framework.
  • The Scrum Teams in a Nexus produce a single Integrated Increment.

Cross-Team Refinement

• Cross-Team Refinement of the Product Backlog reduces or eliminates cross-team dependencies within a Nexus.
  • The Product Backlog must be decomposed so that dependencies are transparent, identified across Scrum Teams, and removed or minimized.
  • Product Backlog items pass through different levels of decomposition from very large and vague requests to actionable work that a single Scrum Team could deliver inside a Sprint.
  • Cross-Team Refinement of the Product Backlog at scale serves a dual purpose:
    • It helps the Scrum Teams forecast which team will deliver which Product Backlog items.
    • It identifies dependencies across those teams.
  • Cross-Team Refinement is ongoing.
    • The frequency, duration, and attendance of Cross-Team Refinement varies to optimize these two purposes.
    • Where needed, each Scrum Team will continue their own refinement in order for the Product Backlog items to be ready for selection in a Nexus Sprint Planning event.
  • An adequately refined Product Backlog will minimize the emergence of new dependencies during Nexus Sprint Planning.

Nexus Sprint Planning

• The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams within a Nexus for a single Sprint.
• Appropriate representatives from each Scrum Team and the Product Owner meet to plan the Sprint.
• The result of Nexus Sprint Planning is :
  • a Nexus Sprint Goal that aligns with the Product Goal and describes the purpose that will be achieved by the Nexus during the Sprint
  • a Sprint Goal for each Scrum Team that aligns with the Nexus Sprint Goal
  • a single Nexus Sprint Backlog that represents the work of the Nexus toward the Nexus Sprint Goal and makes cross-team dependencies transparent
  • a Sprint Backlog for each Scrum Team, which makes transparent the work they will do in support of the Nexus Sprint Goal

Nexus Daily Scrum

• The purpose of the Nexus Daily Scrum is to identify any integration issues and inspect progress toward the Nexus Sprint Goal.
  • Appropriate representatives from the Scrum Teams attend the Nexus Daily Scrum, inspect the current state of the integrated Increment, and identify integration issues and newly discovered cross-team dependencies or impacts.
  • Each Scrum Team’s Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum.
    • The Nexus Daily Scrum is not the only time Scrum Teams in the Nexus are allowed to adjust their plan.
      • Cross-team communication can occur throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work.

Nexus Sprint Review

• The Nexus Sprint Review is held at the end of the Sprint to provide feedback on the done Integrated Increment that the Nexus has built over the Sprint and determine future adaptations.
  • Since the entire Integrated Increment is the focus for capturing feedback from stakeholders, a Nexus Sprint Review replaces individual Scrum Team Sprint Reviews.
  • During the event, the Nexus presents the results of their work to key stakeholders and progress toward the Product Goal is discussed, although it may not be possible to show all completed work in detail.
    • Based on this information, attendees collaborate on what the Nexus should do to address the feedback.
    • The Product Backlog may be adjusted to reflect these discussions.

Nexus Sprint Retrospective

• The purpose of the Nexus Sprint Retrospective is to plan ways to increase quality and effectiveness across the whole Nexus.
  • The Nexus inspects how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done.
  • In addition to individual team improvements, the Scrum Teams’ Sprint Retrospectives complement the Nexus Sprint Retrospective by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.
• The Nexus Sprint Retrospective concludes the Sprint.

The Nexus framework

Nexus Framework : Accountabilities

Nexus framework : Artifacts

Nexus framework : Rules

Scrum for Developers : Scrum PSD flashcards