This is a mind map about "Nexus Guide".
Similar Mind Maps
NEXUS INTEGRATION TEAM
Coordinate, coach and supervise the application of Nexus and the operation of Scrum
Highlight awereness of dependencies and crossteam issues
Accountable for ensuring that a "done" integrated increment once every sprint
Might perform work from product backlog
provides a focal point of integration for the Nexus (scrum teams may address integration issues)
Product Owner, Scrum Master and Nexus Integration Team Members
*members of the Nexus Integration Team are often also members of the individual Scrum teams(they must give priority to their work on the Nexus Integration Team to thelp ensure that thework to relsolve issues affecting many teams has priority)
Composition of the team may change over time to reflect the current needs of a Nexus
is responisble for maximizing the value of the product and the work performed and integrated by the scrum teams
is a member of the NIT
has overall responsibility for ensuring the Nexus framework is understood andenacted
*may be a Scrum Master in one or more of the Scrum Teams
responsible for delivering done increments
professionals who are skilled in the use of various tools and practices
ensure the Scrum Teams whithin the Nexus understand and implement the practices and tools neededto detect dependencies and frequently integrate all artifacts to the definition of "Done"
*team members may also work as Dev team members in one or more Scrum Teams.
DEFINITION OF 'DONE'
Nexus Integration Team is responsible for a definition of done
All Scrum Teams adhere to the same definition (individual scrum teams can apply amore stringent definition of "done", but no less rigorous criteria.
The increment is 'done' when integrated, usable and potentially releasable by the PO
All teams uses the same Product Backlog
PO is accountable for it, including its content, availability and ordering
Ready items it must be understood at a level where dependencies can be detectedand minimized
Nexus Sprint Backlog
Exists to assist with transparency during the sprint
it highlight dependencies and the flow of work during the sprint
All Scrum Teams mantain their individual Sprint Backlogs
is the composite of the product backlog items from the sprint backlogsof individual teams
Frequency, duration and attendance is based on the dependencies in the product backlog
Is continous thyoughout the Sprint as necessary and appropriate
Nexus Sprint Planning
to coordinate the activities of all Scrum teams for a single sprint
to discuss and review the refined product backlog
representatives from each Scrum Team
all members of the Scrum Teams
(to minimize communication issues)
Nexus Sprint Goal
describes the purpose that will be achieved by scrum teams in the sprint
sum of all the work and Sprint goals of the scrum teams
After understanding the overall work for the Nexus, scrum teams perform their own Sprint Planning
Nexus Sprint Planning is complete when each scrum team has finished individual Sprint Planning.
NEXUS DAILY SCRUM
appropriate representatives from individual Dev teams
to inspect the current state of the integrated increment and to identify integration issues or crossteam dependencies/impacts
to inspect progress toward the Nexus Sprint Goal
a set of Sprint Goals aligned to the Nexus Sprint Goal
each Scrum Team's Sprint Backlog
a Single Nexus Sprint Backlog
was the previous day's work successfully integrated?
what new dependencies or impacts have been identified?
what information needs to be shared across teams in the Nexus?
issues and work identified during the Nexusdaily scrum are taken back to be plannedon their individual Daily Scrum
NEXUS SPRINT REVIEW
held at the end of the Sprint
to provide feedback on the integrated increment and to adapt the product backlog if needed
*it may not be possible to show all work in detail, so techniques may be necessary tomaximize stakeholder feedback.
Replaces individual Scrum Teams Reviews, because the entire integrated increment is the focus
a revised product backlog
NEXUS SPRINT RETROSPECTIVE
a formal opportunity for a Nexus to inspectand adapt itself and create plans forimprovements for the next sprint
Was any work left undone? Did the Nexus generate technical debt?
Were all artifacts, particularly code, daily successfully integrated?
Was the software successfully built, tested, and deployed often enough to prenvent overwhelming accumulation of unresolved dependencies?
Part 1. Make shared issues transparent to all teams.
Opportunity for appropriate representatives from across a Nexus to meet and identify issues that have impacted more than a sigle team
Part 2. Each Scrum team holding their own Sprint retrospective
Part 3. Opportunity for appropriate representatives from the scrum teams to meet again and agree on how to visualize and track theidentified actions (allows the Nexus as a whole to adapt)