Nexus Guide Scaling Scrum

Nexus Guide for Scaling Scrum

Get Started. It's Free
or sign up with your email address
Nexus Guide Scaling Scrum by Mind Map: Nexus Guide Scaling Scrum

1. Integrated Increment

2. - has overall responsibility for ensuring the Nexus framework is understood and enacted *may be a Scrum Master in one or more of the Scrum Teams

3. - helps the Scrum team forecast which team will deliver which product Backlog items - identifies dependencies across the teams (teams can monitor and minimize dependencies - makes items ready for selection in the Nexus Sprint Planning.

4. is the current sum of all integrated work completed by a Nexus must be usable and potentially releasable


5.1. - Nexus (n): a relatioship or connection between people or things - Is a process framework consisting of roles, events, artifacts and rules that bind together the work of 3 to 9 scrum teams working on a single Product Backlog to meet an Integrated Increment.

5.2. Purpose

5.2.1. - refinement continues until the product backlog items are suficciently independent to be worked by a single Scrum Team


6.1. - Is a framework for developing and sustaining scaled product initiatives. - It uses Scrum as its building block. *more attention is paid to dependencies and interoperation between Scrum Teams.

6.2. Dependencies

6.2.1. - Requirements: scope may overlap and implementation may affect each other. should be considered when ordering and selecting items - Domain Knowledge: should be distributed across the Scrum Teams (to minimize interruptions between teams). - Test artifacts: Dependencies of requirements, domain knowledge and software artifacts should drive the organization.


7.1. Refinement

7.1.1. to coordinate the activities of all Scrum teams for a single sprint to discuss and review the refined product backlog

7.1.2. Purpose

7.2. Nexus Sprint Planning

7.2.1. Attendees - representatives from each Scrum Team - all members of the Scrum Teams (to minimize communication issues)

7.2.2. Output 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

7.2.3. Sprint planning - 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.

7.3. issues and work identified during the Nexus daily scrum are taken back to be planned on their individual Daily Scrum


7.4.1. Attendees appropriate representatives from individual Dev teams

7.4.2. Purpose to inspect the current state of the integrated increment and to identify integration issues or cross-team dependencies/impacts to inspect progress toward the Nexus Sprint Goal

7.4.3. Daily Scrum

7.5. Spint Retrospective

7.5.1. Frequency, duration and attendance is based on the dependencies in the product backlog Is continous thyoughout the Sprint as necessary and appropriate

7.6. - 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?


7.7.1. - a set of Sprint Goals aligned to the Nexus Sprint Goal - each Scrum Team's Sprint Backlog - a Single Nexus Sprint Backlog

7.7.2. 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 the identified actions (allows the Nexus as a whole to adapt)


8.1. Product Backlog

8.1.1. All teams uses the same Product Backlog

8.1.2. Ready items - it must be understood at a level where dependencies can be detected and minimized PO is accountable for it, including its content, availability and ordering

8.2. Nexus Sprint Backlog

8.2.1. Exists to assist with transparency during the sprint it highlight dependencies and the flow of work during the sprint updated daily

8.2.2. All Scrum Teams mantain their individual Sprint Backlogs

8.2.3. is the composite of the product backlog items from the sprint backlogs of individual teams



9.1.1. Role - Coordinate, coach and supervise the application of Nexus and the operation of Scrum - Highlight awereness of dependencies and cross-team 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)

9.1.2. Team 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 the work to relsolve issues affecting many teams has priority) Composition of the team may change over time to reflect the current needs of a Nexus

9.1.3. PO - 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 needed to 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.

9.1.4. SM 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 NEXUS SPRINT REVIEW 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 to maximize stakeholder feedback. held at the end of the Sprint Purpose


9.2.1. responsible for delivering done increments team Members


10.1. Nexus Integration Team is responsible for a definition of done

10.2. All Scrum Teams adhere to the same definition (individual scrum teams can apply a more stringent definition of "done", but no less rigorous criteria.

10.3. The increment is 'done' when integrated, usable and potentially releasable by the PO