Nexus Role 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.
Integration Accountability
The NIT is accountable for ensuring that a done Integrated Increment — the combined work of all Scrum Teams in the Nexus — is produced at least once every Sprint. They don’t do all integration work, but they ensure it happens.
Dependency Detection & Reduction
The NIT works to make dependencies visible and — more importantly — to reduce them. The goal is not better dependency management but fewer dependencies through refinement, architecture, and team organization.
Nexus Event Facilitation
The NIT — through its Scrum Master — facilitates Nexus-level events: Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, and Nexus Sprint Retrospective.
Cross-Team Coaching
The NIT coaches Scrum Teams on practices that reduce integration friction — continuous integration, automated testing, shared code standards, and collaborative development practices.
Transparency & Artifact Management
The NIT ensures transparency across all Nexus artifacts — making the state of the Integrated Increment, dependencies, and cross-team work widely understood by all teams and stakeholders.
Dynamic Membership
NIT membership is dynamic — it includes whoever is needed to ensure integration happens. Members may come from individual Scrum Teams, but their NIT work takes precedence over team-level work.
The NIT is not a management layer, not a coordination committee, and not a separate team with its own backlog. It exists to solve the integration problem — ensuring that multiple teams’ work combines into one working product every Sprint. As integration practices mature across teams, the NIT’s direct involvement should decrease.
Nexus Roles
Explore other roles in the Nexus 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.
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.