Nexus Role Framework
Scrum Master
In Nexus, the Scrum Master is a core member of the Nexus Integration Team, accountable for ensuring the Nexus framework is understood and enacted across all 3–9 Scrum Teams. Their focus extends beyond single-team facilitation to cross-team integration, dependency reduction, and coaching teams toward producing a done Integrated Increment every Sprint.
NIT Membership & Integration Accountability
The Scrum Master serves as the designated SM on the Nexus Integration Team alongside the Product Owner and integration-skilled members. Their overriding accountability is ensuring all teams’ work integrates into a single, done Integrated Increment every Sprint.
Nexus Event Facilitation
The SM facilitates all Nexus-level events — Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, and the three-part Nexus Sprint Retrospective — keeping each focused on integration and cross-team coordination.
Dependency Detection & Reduction
The Nexus SM focuses on making dependencies visible and — more importantly — reducing them. The goal is not better dependency tracking but fewer dependencies through refinement, architecture, and team composition.
Cross-Team Coaching
The SM coaches all teams on practices that reduce integration friction — continuous integration, automated testing, shared code standards, and collaborative development — building toward team self-sufficiency.
Transparency & Artifact Stewardship
The SM ensures transparency across all Nexus artifacts — making the state of the Integrated Increment, dependencies, and cross-team work visible to all teams and stakeholders for empirical decision-making.
Dynamic NIT Composition & Self-Sufficiency
The SM manages the NIT’s evolving composition and coaches the Nexus toward decreasing reliance on the NIT — as integration practices mature across teams, the NIT’s direct involvement should naturally decrease.
The Scrum Master on the Nexus Integration Team is not a project manager, not a coordination committee chair, and not a cross-team status collector. The role exists to solve the integration problem — ensuring that 3–9 Scrum Teams’ work combines into one working, done product Increment every Sprint. Unlike SAFe’s layered role hierarchy or LeSS’s organizational change mandate, the Nexus SM focuses specifically on integration accountability and dependency reduction within Scrum’s existing empirical framework. As integration practices mature and teams learn to coordinate directly, the SM’s Nexus-level facilitation load should naturally decrease.
Nexus Roles
Explore other roles in the Nexus framework
Nexus Integration Team
The NIT is accountable for ensuring a done Integrated Increment is produced every Sprint. It consists of the Product Owner, a Scrum Master, and members with integration-relevant skills drawn from across the Scrum Teams.
Product Owner
In Nexus, a single Product Owner manages one Product Backlog for 3–9 Scrum Teams working on the same product. As a core member of the Nexus Integration Team, the PO ensures coherent product direction, minimizes cross-team dependencies through strategic backlog ordering, and drives the production of a single Integrated Increment every Sprint.