Nexus framework guide(2021)

nexus Theory
Accountability in Nexus
3 Scrum specific sets of accountabilities
Nexus Events
The Sprint
Cross-team refinement
Nexus Sprint planning
Nexus Daily Scrum
Nexus Sprint Review
Nexus Sprint Retrospective
Nexus Artefacts and commitments
Product Backlog
Nexus Sprint Backlog
Integration Increment
framework for developing and sustaining scaled product delivery initiatives
build upon Scrum, extending it only where absolutely necassy
minimise and manage dependencies between multipe Scrum teams while promoting empiricism and scrum values.
Still Scrum: not change the core ideas of Scrum, or leave out elements or negate the rules of Scrum
Delays in communication and feedback reduce the flow of work
Reduce or remove dependencies
Help solve dependency and collaboration challenges of cross-team work
NIT ensures that the Nexus delivers
useful Integrated Increment
at least once every sprint
appended to, placed around, or replace regular Scrum events to augemnt them
Serve both all Scream Teams and individual Scrum Team
All Scrum teams use the same, Single PB
Refined and made ready
make transparent which team will most likely do the work inside a Sprint
Nexus Sprint Backlog:assist with transparency during the Sprint
Integrated increment: represents the current sum of all integrated work completed by a Nexus
Nexus Integration Team(NIT)
Accountable for ensuring that a done Integrated Increment(the combined work completed by a Nexus is produced at least once a Sprint
Appopriate NIT members
Add to or extends the events defined by Scrum
coordinate the activies of all STs within a Nexus for a single Sprint
Identify any integration issues and inspect progress toward the Nexus Sprint Goal
Held at the end of the Sprint
Purpose: to plan ways to increase quality and effectiveness across the whole Nexus
Represent work or value
Single: list of what is needed to improve the product for the entire Nexus and all of its STs
is the composite of the Nexus Sprint Goal and PBIs from the Sprint Backlogs of the individual STs
Represents the current sum of all integrated work completed by a Nexus toward the Product Goal
Is ongoing activitie
Reduces or eliminates cross-team dependencies
If needed each team will continue their own refinement in order to for the PBIs to be ready in a nexus Sprint planning event
appropriate representatives from each ST + PO to plan the Sprint
Not the only time STs in the Nexus are allowed to adjust their plan
Replaces individual ST reviews
Focus capturing feedback from stakeholders
Commitment: Product Goal
Must be understood at a level where dependencies can be detected and minimized
Accountable: PO
Commitment: Nexus Sprint Goal
Used to highlight dependencies and the flow of work during sprint
Updated throughout the Sprint as more is learned
Should have enough detail that the Nexus can inspect their progress in the Nexus Daily Scrum
Commitment: Definition of Done(DoD)
Is inspected at the Nexus Sprint Review, but may be delivered to stakeholders before the end of the Sprint
Must meet the DoD
Desicions made based on the state of artifacts are only as effective as the level of artifact transparency
Provide focal point of Integration(technical & non-technical cross-functional team constraints) for the Nexus
Responsible for coaching and guiding the STs to acquire, implement and learn practices and tools that improve their ability to produce a valuable ans useful Increment
Group of 3-9 Scrum Teams(STs), that work together to deliver 1 product
Connection between people and things
1 Product Backlog(PB)
Define: accountabilities, events and artefacts that bind and weave together the work of the Scrum Teams in a Nexus
Minimaly extends the Scrum framework only where absolutely necessary to enable multiple teams to work from a single PB to build an Integrated Increment that meets a goal.
Nexus preserve and enhance Scrum's foundational :
goal: scale the value that a group of Scrum Teams, working on a single product is able to deliver.
Help teams solve common scaling challenges like:
helps to make transparent dependencies
provide opportunities to change:
conterintuitive but: scaling the value that is delivered does not always require adding more people
Accountable: ensuring the Nexus framework is understood and enacted as describe in the Nexus guide
May also be a SM in >=1 ST in the Nexus
people with the necessary skills and knowledge to help resolve the issues the Nexus faces at any point in time
ST members
composition may change over time to reflect the current needs of a Nexus
1 Product Owner(PO)
The Nexus Framework
bottom-up intelligence
reducing cross-team dependencies
preserving team self-management and transparency
ensuring accountability
degree to which different concerns are independly seperated in the product will greatly affect the complexity of creating an integrated product release.
the way that people communicate within and between teams affects their ability to get work done.
product structure
communication structure
Scaling-down(Descaling): reducing the number of people who work on something, can be an important practice in delivering more value.
Product structure
communications structure
Accountable for maximizing:
Value of the product
Work performed and integrated by the STs in a Nexus
Effective PB management
Help STs adopt tools and practices=>deliver valuable and useful Integred Increment that frequently meets the DoD
highlighting awareness of dependencies and cross-team issues
Same as in Scrum
STs produce 1 Integrated increment
Decompose PB=>dependencies
identified across teams
removed or minimized
Helps the STs forecast which team will deliver which PBIs
Identifes dependencies across those teams
Frequency, duration, attendance varies to optimize those 2 purposes
Nexus Sprint Goal: align withe the Product Goal
Sprint Goal for each ST: align with the Nexus Sprint Goal
1 Nexus Sprint Backlog
1 Sprint Backlog for each ST
Describe the purpose that will be achieved by the Nexus during the Sprint
represents the work of the Nexus toward the Nexus Sprint Goal
Make cross-team dependencies transparent
Make transparent the work they will do in support of the Nexus Sprint Goal
Appropriate representatives from STs
Part 1: Representatives
Part 2: ST's Daily Scrum
Identify integration issues and newly discovered cross-team dependencies or impacts
inspect the current state of the integrated Increment
Complements the Nexus Daily Scrum
Creating plan for the day
focus primarily on addressing the integration issues raised during the Nexus Daily Scrum
Cross-team communication can occur througout the day for more detailled discussions about adapting or re-planning the rest of the Sprint's work
the Nexus presents
may not possible to show all completed work in detail
attendees collaborate on what the Nexus should do to address the feedback
The PB may be adjusted to reflect discussions
the results of their work to key stakeholders
progress toward the Product Goal is discussed
The Nexus Inspects how the last Sprint went with regards to
each ST's retrospective
Bottom-up intelligence to focus on issues that affect the Nexus as a whole
individual team improvements
Describes the future state of the product
Serves as a long-terme goal of the Nexus
Is the sum of all the work and Sprint Goals of the STs within the Nexus
Creates coherence and focus for the Nexus for the Sprint
Created at the Nexus Sprint Planning event and added to the Nexus Sprint Backlog
STs keep the Nexus Sprint Goal in mind during the Sprint
The Nexus should demonstrate the valuable and useful functionality that is done to achieve the Nexus Sprint Goal at the Nexus Sprint Review in order to reveive stakeholder feedback
Encourage STs to work together rather than on separate initiatives
to provide feedback on the done Integrated increment
Determine future adaptations
Defines the state of the integrated work when it meets the quality and measures required for the product
The Increment is done only when:
All STs within the Nexus must define and adhere to this DoD
Individual STs self-manage to achieve this state
The impact of those decisions can be magnified at the scale of Nexus
Incomplete or partial information will lead to incorrect or flawed decisions
May choose to apply a more stringent DoD within their own teams
BUT cannot apply less rigorous criteria than agreed for the Integrated Increment
concludes the Sprint
Duration is guided by the length of the corresponding events in the Scrum guide
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
Adequately refined PB will minimize the emergence of new dependencies during Nexus Sprint Planning
Are designed to maximize transparency
NIT work with STs within a Nexus
Commitments: exist to reinforce
to ensure transparency is achieved acroo all artifacts
the state of the integrated Increment is widely understood
Scrum value for the Nexus and its stakeholders
extends Scrum:
1 / 2
197 1 2