Nexus Events
Nexus Sprint Planning
Cross-team then per-team · Timebox: Nexus: ≤2 hrs + team planning
Overview
Nexus Sprint Planning happens in two phases: first, representatives from all teams coordinate on cross-team concerns and dependencies. Then each team conducts its own Sprint Planning. The Nexus-level phase ensures teams are aligned before they plan independently.
Event Ownership
Owned / Facilitated By
NIT Scrum Master (Nexus-level) / Team Scrum Masters (team-level)
NIT SM facilitates the Nexus-level planning phase with representatives from all teams
Product Owner presents priorities and helps teams understand which items involve cross-team dependencies
Teams coordinate on shared work, interfaces, and integration points before individual team planning
Each team then conducts standard Sprint Planning to create their Sprint Backlog
Who Should Be Present
Team Representatives
At least one representative per team (often more). Discuss cross-team dependencies, coordinate work selection, identify integration risks
Product Owner
Presents priority items, clarifies dependencies between items, helps teams understand which items may span multiple teams
NIT Members
Facilitate dependency detection, propose integration strategies, help teams identify cross-team coordination needs
All Team Members (team phase)
Standard Sprint Planning per team — decompose items, create Sprint Backlog, agree on Sprint Goal
Preparation Checklist
01Product Backlog refined with dependency indicators visible
02Cross-team refinement completed for top items
03NIT: integration environment and CI/CD pipeline ready
04Teams: capacity calculated, prior Sprint outcomes reviewed