Nexus is a lightweight framework for scaling Scrum, developed by Ken Schwaber and Scrum.org. It extends Scrum minimally to coordinate multiple teams working on the same product, ensuring an integrated increment each Sprint. Its focus is on integration, transparency, and dependency management.
Origin and Purpose
Scrum is most effective in small teams. As team numbers grow, dependencies and integration risks increase exponentially. Nexus, first published in 2015, addresses this by adding minimal structure while preserving Scrum principles, targeting setups with 3–9 teams (20–80 people).
Core Elements
Nexus Integration Team (NIT): responsible for ensuring a single integrated increment each Sprint.
Roles: classic Scrum roles plus the NIT as an additional integration-focused structure.
Events: extensions of Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and the additional Nexus Refinement.
Artifacts: Nexus Sprint Backlog (aggregated, showing dependencies), integrated increment as the single valid product increment.
Scope: optimized for 3–9 Scrum Teams; Nexus+ for larger configurations.
Application and Best Practices
- Integration as the centerpiece: CI/CD, automated tests, and a strong Definition of Done are essential.
- Refinement as a necessity: not optional, it’s the mechanism for dependency management.
- Transparency tools: dependency boards, integrated burndowns, shared artifacts.
- Team design: Nexus often pushes organizations to restructure toward more cross-functional teams.
Practice Examples
Financial services: A bank used Nexus for core banking modules. Quality only stabilized after CI/CD pipelines and common test frameworks were established.
Medical technology: Nexus ensured every Sprint delivered integrated code, tests, and documentation – critical for compliance.
Scaling SMEs: A company scaling from two to five teams used Nexus; only with test automation did integration stop being a bottleneck.
Automotive case: Nexus worked for software but failed for hardware integration, requiring hybrid setups with SAFe practices.
Criticism and Limitations
- Integration bottleneck: Nexus depends on solid engineering practices; without them it breaks down.
- Scaling ceiling: Designed for up to 9 teams; larger organizations require Nexus+ or other frameworks.
- No portfolio scope: Funding, strategy, and value stream management are not covered.
- High maturity required: Organizations without strong Scrum discipline tend to fail with Nexus.
- Common misinterpretations: It is not “Scrum++” but a structural and cultural shift emphasizing disciplined integration.
Embedding and Combination
- Scrum: Nexus does not alter Scrum, only extends it.
- LeSS vs. Nexus: LeSS involves more organizational redesign; Nexus focuses on integration.
- SAFe vs. Nexus: SAFe includes portfolio/value stream levels; Nexus is strictly delivery-focused.
- Living Transformation®: Nexus serves as a tactical delivery mechanism; Living Transformation® provides the strategic umbrella and outcome focus.
CALADE Perspective
We consider Nexus a practical scaling tool for organizations with multiple Scrum Teams. CALADE helps assess whether Nexus suffices or should be combined with other frameworks like SAFe. Our experts bring real-world lessons from both successful Nexus adoptions and cases where alternative approaches were more effective.
Related Glossary Entries
- Scrum
- LeSS
- SAFe
- Agile Release Train (SAFe)
- Living Transformation®
- Continuous Integration
- Definition of Done
← back to list