frameworkDelivery & agility

Nexus Framework

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

Download Markdown (.md)

01What 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.[1][2][3]

Minimal coordination for several Scrum Teams on one product Cross-team refinement and integration practices protect one valuable increment
One product + integrated increment
One Product Backlog
Shared ordered work and Product Goal
Nexus Integration Team
Accountability for effective integration
Cross-team refinement
Expose dependencies and make work selectable
Nexus Sprint Goal
One coherent objective across team plans
Nexus Daily Scrum
Inspect integration issues and adapt coordination
Integrated events
Review and retrospect on the whole product system

Nexus typically serves three to nine Scrum Teams and adds only the accountabilities, events, and artifacts needed to expose dependencies and integration work.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. The Nexus GuideScrum.org · Official framework guideThe Nexus Guide
  2. Scaling Scrum with NexusScrum.org · Official resource centerScaling Scrum with Nexus
  3. Nexus Overview DatasheetScrum.org · Official overviewNexus Overview Datasheet
View saved topics

Start typing to search titles, definitions, categories, and frameworks.