Big Scrum: Scaling Scrum with Nexus
summary
Argues that scaling only helps when teams are already professional and otherwise descaling is better, citing a case with 80 teams in 12 locations across 9 countries and Microsoft VSTS using ~70 teams on their own product. Recommends Nexus: one integrated increment per sprint, a new integration team, Nexus sprint planning and daily team-of-teams syncs, plus tools like TFS/VSTS/JIRA, strict Definition of Done, feature teams, telemetry and internal open source; these practices reduce merge chaos and make scale feasible.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:57Martins background
- 2:24Working with customers
- 3:17The Kaos Report
- 6:29Agenda
- 7:48Cost
- 11:11Amateur Scrum
- 12:24Following the rules
- 12:39We still need the rules
- 14:21We need courage
- 15:32Professional Scrum Team
- 16:13How do we get there
- 17:07Scale
- 18:10Vertical Access
- 21:04Where is your company
- 22:40Methodology
- 24:10Scrum Diagram
- 25:31Nexus Sprint Planning
- 32:55Nexus Integration Planning
- 33:50One Product Owner
- 41:38Deliver the Right Software
- 42:55Pull the chain
- 45:34Dependency map
- 47:00Scaling
- 47:57Cadence
- 48:57Feature Teams
- 49:26Communities of Practice
- 51:17Microservices
- 51:59Hierarchy
- 53:19Telemetry
- 54:59Internal Open Source
- 56:20Not Scaling
related talks
39mScrum at Scale
58mScaling Agile in Organizations
49mScaling Up!
45mOverview of Enterprise-Scale Agile Frameworks
21mScaling Scrum in Fully Remote Work — Challenges from 3 People to 30 People and 6 Teams over Three Years and Applying Scrum@Scale and LeSS Practices
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
16mSmall Scale Scrumming
58mAgility at Scale: Tactical and Strategic Approaches