Please enable JavaScript.
Coggle requires JavaScript to display documents.
Nexus - Coggle Diagram
Nexus
Nexus Events
Refinement
The Product Backlog needs to be decomposed so that dependencies are identified and removed or minimized
-
PBI Ready: sufficiently independent to be worked on by a single Scrum Team without excessive conflic
The number, frequency, duration and attendance of Refinement is based on the dependencies and uncertainty inherent in the Product Backlog
Nexus Sprint Planning
Appropriate representatives from each Scrum Team meet to discuss and review the refined Product Backlog
-
-
Nexus Sprint Planning is complete when each Scrum Team has finished their individual Sprint Planning events
Development work
All teams frequently integrate their work into a common environment that can be tested to ensure that the integration is done
Nexus Daily Scrum
Appropriate representatives from each Development Team meet daily to identify if any integration issues exist
If identified, this information is transferred back to each Scrum Team’s Daily Scrum
-
Nexus Sprint Review
A Nexus Sprint Review replaces individual Scrum Team Sprint Reviews, because the entire Integrated Increment is the focus for capturing feedback from stakeholders
-
-
-
-
Nexus Roles
Nexus Integration Team
exists to coordinate, coach, and supervise the application of Nexus and the operation of Scrum so the best outcomes are derived. The Nexus Integration Team consists of the Product Owner, a Scrum Master, and Nexus Integration Team Members
-
-
-
Nexus Integration Team
-
-
Composition of the Nexus Integration Team may change over time to reflect the current needs of a Nexus
-
Nexus Artifacts
Product Backlog
-
-
Product Backlog items are deemed “Ready” for the Nexus Sprint Planning meeting when the Scrum Teams can select items to be done with no or minimal dependencies with other Scrum Teams
Nexus Sprint Backlog
-
The Nexus Sprint Backlog makes the work of all Scrum Team's selected Product Backlog items and any dependencies transparent
It is updated at least daily, often as part of the Nexus Daily Scrum.
Integrated Increment
The Integrated Increment must be usable and potentially releasable which means it must meet the definition of “Done”
Dependencies
-
Domain knowledge
Their knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work
-
Artifact Transparency
Definition of “Done”
Individual Scrum Teams may choose to apply a more stringent definition of “Done” within their own teams, but cannot apply less rigorous criteria than agreed for the Increment
Nexus is a process framework for multiple Scrum Teams working together to create an Integrated Increment.
The difference is that more attention is paid to dependencies and interoperation between Scrum Teams, delivering at least one “Done” Integrated Increment every Sprint
-