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. 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.
The Nexus Framework helps teams solve common scaling challenges like reducing cross-team dependencies, preserving team self-management and transparency, and ensuring accountability.
- Nexus helps to make transparent dependencies.
- Nexus provides opportunities to change the process, product structure, and communication structure to reduce or remove these dependencies.
Nexus Accountabilities
- Nexus Integration Team. The Team is accountable for ensuring that a done Integrated Increment (the combined work completed by a Nexus) is produced at least once a Sprint.
- It provides the focus that makes possible the accountability of multiple Scrum Teams to come together to create valuable, useful Increments, as prescribed in Scrum.
- Integration includes addressing technical and non-technical cross-functional team constraints that may impede a Nexus’ ability to deliver a constantly Integrated Increment.
- It should use bottom-up intelligence from within the Nexus to achieve resolution.
- The Product Owner:
- A Product Backlog has a single Product Owner who has the final say on its contents.
- The Product Owner is accountable for maximizing the value of the product and the work performed and integrated by the Scrum Teams in a Nexus.
- Is accountable for effective Product Backlog management.
- A Scrum Master:
- The Scrum Master in the Nexus Integration Team is accountable for ensuring the Nexus framework is understood and enacted as described in the Nexus Guide.
- This Scrum Master may also be a Scrum Master in one or more of the Scrum Teams in the Nexus.
- One or more Nexus Integration Team Members:
- Scrum Team members who help the Scrum Teams to adopt tools and practices that contribute to the Scrum Teams’ ability to deliver a valuable and useful Integrated Increment that frequently meets the Definition of Done.
Nexus Events
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.
- It may not be practical for all members of Nexus to participate to share information or 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.
- The Sprint. A Sprint in Nexus is the same as in Scrum.
- Cross-Team Refinement. Reduces or eliminates cross-team dependencies within a Nexus.
- The Product Backlog must be decomposed so that dependencies are transparent, identified across 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.
- The frequency, duration, and attendance of Cross-Team Refinement vary.
- Where needed, each Scrum Team will continue its own refinement in order for the Product Backlog items to be ready for selection in a Nexus Sprint Planning event.
- Nexus Sprint Planning. Coordinates 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 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.
- Nexus Sprint Review. It 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.
- The Nexus Sprint Review replaces individual Scrum Team Sprint Reviews.
- Nexus Sprint Retrospective. The purpose 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.
Nexus Artifacts
- Product Backlog. There is a single Product Backlog that contains a list of what is needed to improve the product for the entire Nexus and all of its Scrum Teams. At scale, the Product Backlog must be understood at a level where dependencies can be detected and minimized.
- Commitment: Product Goal - The Product Goal, describes the future state of the product and serves as a long-term goal of the Nexus.
- Nexus Sprint Backlog. It is the composite of the Nexus Sprint Goal and 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. The Nexus Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that the Nexus can inspect their progress in the Nexus Daily Scrum.
- Commitment: Nexus Sprint Goal. It is a single objective for Nexus.
- Integrated Increment. It 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.
0 Comments:
Post a Comment