1. EVENTS
1.1. Refinement
1.1.1. Frequency, duration and attendance is based on the dependencies in the product backlog
1.1.2. Is continuous throughout the Sprint as necessary and appropriate
1.2. Nexus Sprint Planning
1.2.1. Purpose
1.2.1.1. to coordinate the activities of all Scrum teams for a single sprint
1.2.1.2. to discuss and review the refined product backlog
1.2.2. Attendees
1.2.2.1. representatives from each Scrum teams
1.2.2.2. all members of the Scrum Teams
1.2.3. Output
1.2.3.1. Nexus Sprint Goal
1.2.3.1.1. describes the purpose that will be achieved by scrum teams in the sprint
1.2.3.1.2. sum of all the work and Sprint goals ò the scrum teams
1.2.4. Sprint Planning
1.2.4.1. After understanding the overall work for the Nexus, scrum teams perform their own Sprint Planning
1.2.4.2. Nexus Sprint Planning is complete when each scrum team has finished individual Sprint Planning
1.3. Nexus Daily Scrum
1.3.1. Attendees
1.3.2. Purpose
1.3.3. was the previous day's work sucessfully integrated?
1.3.4. what new dependencies or impacts have been identified
1.3.5. what information needs to be shared across teams in the Nexus?
1.3.6. Daily Scrum
1.3.6.1. issues and work identified during the Nexus daily scrum are taken back to the be planned on their individual Daily Scrum
1.4. Nexus Sprint Review
1.4.1. held at the end of the Sprint
1.4.2. Purpose
1.4.2.1. to provide feedback on the integrated increment and to adapt the product backlog if needed
1.4.2.2. it may not be possible to show all work in detail, so techniques may be necessary to maximize stakeholder feedback
1.4.2.3. Replaces individual Scrum Teams reviews, because the entire integrated increment is the focus
1.4.3. Ouptut
1.4.3.1. a revised product backlog
1.5. Nexus Sprint Retrospective
1.5.1. a formal opportunity for a Nexus to inspect and adpt itself and create plans for improvements for the next sprint
1.5.2. was any work left undone? Did the Nexus generate technical debt?
1.5.3. were all artifacts, particularly code, daily successfully integrated?
1.5.4. was the software successfully built, tested, and deployed often enough to prevent overwhelming accumulation of unresolved dependencies
1.5.5. Part 1. Make shared issues transparent to all teams
1.5.6. Opportunity for appropriate represnentatives from accross a Nexus to meet and identofy issues that have impacted more than a single team
1.5.7. Part 2. Each Scrum team holding their own Sprint Retrospective
1.5.8. Part 3. Opportunity for appropriate represnentatives from accross a Nexus to meet again and agree on how to visualize and track the identified actions (allows the Nexus as a whole to adapt)
1.5.9. Sprint Retrospective
2. ARTIFACTS
2.1. Product Backlog
2.1.1. All teams uses the same Product Backlog
2.1.2. PO is accountable for it, including its content, availability and ordering
2.1.3. Ready items it must be understood at a level where dependencies can be detected and minimized
2.2. Nexus Sprint Backlog
2.2.1. Exists to assist with transparency during the sprint
2.2.2. It highlight dependencies and the flow of work during the sprint
2.2.3. updated daily
2.2.4. All Scrum Teams maintain their individual Sprint Backlogs
2.2.5. is the composite of the product backlog items from the sprint backlogs ò individual teams
2.3. Integrated Increment
3. ROLES
3.1. Nexus Integration Team
3.1.1. role
3.1.1.1. Coordinate, coach and supervise the application of Nexus and the operation of Scrum
3.1.1.2. Highlight awareness of dependencies and crossteam issues
3.1.1.3. Accountable for ensuring that a "done" integrated increment once every sprint
3.1.1.4. Might perform work from product backlog
3.1.1.5. provides a focal point of integration for the Nexus (scrum teams may address integration issues)
3.1.2. Team
3.1.2.1. PO, SM an Nexus team members
3.1.2.2. composition of the ream may change over time to reflect the current needs of a Nexus
3.1.3. PO
3.1.3.1. is responsible for maximizing the value of the product and the work performed and the integrated by scrum teams
3.1.3.2. is a member of the NIT
3.1.4. SM
3.1.4.1. has overall responsible for ensuring the Nexus framework is understood and enacted
3.1.5. team Members
3.2. Scrum Teams
3.2.1. responsible for the delivering done increments
3.2.2. professionals who are skilled in the use of various tools and practices
3.2.3. ensure the Scrum Teams within the Nexus understand an implement the practices and tools needed to detect dependencies and frequently integrate all artifacts to the definition of "Done"
3.2.4. team members may also work as dev team members in one or more Scrum Teams