# Nexus Framework

Nexus minimally extends Scrum so several teams can manage dependencies and produce one integrated, valuable product increment every Sprint.

- Type: framework
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/nexus-framework/>)

## What it means

Nexus is a Scrum.org framework for approximately three to nine Scrum Teams working from one Product Backlog on one product. It adds only the accountabilities, events, and artifacts needed to make cross-team dependencies and integration work visible, while preserving Scrum’s empirical foundation.

## Why it matters

When several teams work on one product, each can appear productive while the combined system remains unstable. Nexus makes the integrated increment—not separate team outputs—the unit of progress. It provides explicit opportunities to identify dependencies, coordinate work, inspect integration, and adapt the shared plan.

## When to use it

Use Nexus when teams already understand Scrum but cannot reliably deliver an integrated increment because of dependencies, shared components, or late integration. It is most suitable for one product and a modest number of teams; broader portfolio or organizational design problems may need complementary approaches.

## How it works

1. Maintain one Product Backlog, one Product Goal, and a common Definition of Done for the product.
2. Use cross-team refinement to expose dependencies, sequence work, and make backlog items ready for multiple teams.
3. Hold Nexus Sprint Planning to establish one Nexus Sprint Goal and coordinate the work selected by individual teams.
4. Use the Nexus Daily Scrum and ongoing team communication to inspect integration issues and adjust the plan.
5. Produce one integrated increment, inspect it at the Nexus Sprint Review, and improve the whole system in the Nexus Sprint Retrospective.

## A practical example

Four Scrum Teams build a clinical scheduling product. Cross-team refinement reveals that a reminder feature depends on shared consent rules and notification services. The teams adjust the order of work, agree on integration tests, and inspect the combined workflow daily. The Sprint Review evaluates one working increment rather than four disconnected demonstrations.

## Where it breaks

Nexus does not remove dependencies by decree, supply a portfolio model, or repair weak engineering practices. Added Nexus events can become status meetings if teams do not collaborate directly. A single backlog may still hide product complexity, and organizations with more than nine teams or multiple loosely connected products may need a different structure.

## Common mistakes

- Treating the Nexus Integration Team as a separate integration or project-management department.
- Allowing teams to use incompatible Definitions of Done.
- Postponing integration until the end of the Sprint.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/nexus-framework/#visualization-nexus-framework>)

## Sources

1. [The Nexus Guide](<https://www.scrum.org/resources/nexus-guide>) — Scrum.org · Official framework guide
2. [Scaling Scrum with Nexus](<https://www.scrum.org/resources/scaling-scrum>) — Scrum.org · Official resource center
3. [Nexus Overview Datasheet](<https://www.scrum.org/resources/nexus-overview-datasheet>) — Scrum.org · Official overview

## Related topics

- [Scrum](<https://wiki.soroush.uk/topic/scrum/>)
- [Large-Scale Scrum](<https://wiki.soroush.uk/topic/large-scale-scrum/>)
- [Scrum@Scale](<https://wiki.soroush.uk/topic/scrum-at-scale/>)
