Building big teams with Nexus
summary
Nexus applies Scrum to one product with about three to nine teams, requiring a single integrated increment each sprint and a visible nexus sprint backlog so all teams see work and dependencies. It enshrines a Nexus Integration Team (representatives, not a permanent silod build team), makes refinement becomes mandatory to spot cross‑team dependencies early, and recommends feature teams, CI with automated acceptance tests, short demo videos or science‑fair reviews, and internal open‑source reuse to keep scaling sustainable.
AI-written summary · about
chapters (25)
- 0:00Start
- 6:19The state of Agility for Software
- 10:13The Journey
- 16:32Step 1: Do Scrum Well
- 17:11Step 3: Introduce Scrum Values
- 23:38Nexus Roles, Events and Artifacts
- 28:48Understand How to Structure for Scaling Success
- 30:05Identifying Dependencies in the Product Backlog
- 30:41Types of Dependencies
- 31:12Feature Teams
- 32:17The Nexus Integration Team
- 35:30Impact Mapping
- 36:23Story Mapping
- 38:32Product Backlog Refinement Event
- 39:27Cross Team Refinement
- 41:53Nexus Sprint Planning Flow
- 43:52Nexus Sprint Planning Room Layout
- 45:58Nexus Daily Scrum
- 46:33Nexus Sprint Review
- 48:11Offline Sprint Review
- 49:14Nexus Sprint Retrospective
- 50:05Retrospective Board
- 51:37Scaled Product Ownership
- 54:47Automated Acceptance Testing
- 55:36Internal Open Source
related talks
26mThe Challenge of Implementing Nexus from Scrum.org
49mScaling Professional Scrum with Visual Studio Team Services
48mTwo Dimensions Of Agile At Scale
47mHow Microteams Change the Way We Collaborate. Again
35mBuilding and Growing an Agile Team
48mHow microteams change the way we collaborate. Again.
58mScaling Agile in Organizations
15mAdvanced Scrum techniques for optimal delivery