GuideRolesEventsWorkflow

Nexus Events

Nexus Sprint Retrospective

The Nexus Sprint Retrospective has three parts: (1) cross-Nexus issues identified by representatives, (2) individual team retrospectives incorporating Nexus themes, (3) representatives reconvene to agree on shared improvement actions. This structure ensures both team-level and Nexus-level improvements.

Three-part improvement · Timebox: ≤3 hours (1-month Sprint)

Overview

The Nexus Sprint Retrospective has three parts: (1) cross-Nexus issues identified by representatives, (2) individual team retrospectives incorporating Nexus themes, (3) representatives reconvene to agree on shared improvement actions. This structure ensures both team-level and Nexus-level improvements.

Event Ownership

Owned / Facilitated By
NIT Scrum Master (facilitates all three parts)
Facilitate Part 1: representatives identify cross-Nexus issues affecting integration and collaboration
Support team Scrum Masters in Part 2: individual team retrospectives
Facilitate Part 3: representatives agree on shared improvement actions for the next Sprint
Ensure improvement items are concrete, owned, and tracked across Sprints

Who Should Be Present

Part 1: Team Representatives
Identify issues that span multiple teams — integration problems, dependency friction, shared process gaps
Part 2: Individual Teams
Standard team retrospective incorporating themes from Part 1. Identify team-level and Nexus-level improvements
Part 3: Team Representatives
Share team retro insights, agree on shared Nexus-level improvements, assign owners and actions

Preparation Checklist

01NIT SM: Gather Sprint data — integration success rates, dependency resolution time, cross-team blockers
02NIT SM: Review prior Nexus Retro improvement items and their completion status
03Team SMs: Prepare retrospective formats for their teams
04All: Reflect individually on cross-team collaboration during the Sprint

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Part 1 → Part 2 → Part 3 Flow

Part 1 surfaces cross-Nexus themes (30 min). Teams take these themes into their individual retros in Part 2. Part 3 reconvenes to synthesize team insights into shared actions. This creates a natural bottom-up intelligence pipeline.

Click to expand

Integration Health Check

In Part 1, use a simple red/yellow/green assessment across integration dimensions: CI/CD pipeline health, cross-team dependency management, DoD adherence, integration testing quality. This grounds the discussion in objective data.

Click to expand

Dot Voting on Cross-Nexus Issues

After Part 1 generates a list of cross-Nexus issues, each representative gets 3 votes to prioritize. The top 1–2 issues become the focus for Part 3 action planning.

Click to expand

Tips & Tricks

01
The three-part structure is essential — don’t skip parts or combine them
02
Part 1 informs Part 2 — team retros should address Nexus themes, not just team-internal issues
03
Part 3 produces shared commitments — not just observations. Every action needs an owner
04
Limit shared improvements to 1–2 per Sprint. More commitments means less actual change
05
Track Nexus Retro improvements across Sprints. If the same issues recur, solutions aren’t deep enough
06
Vary team retrospective formats to prevent retro fatigue while keeping the three-part Nexus structure
07
Shared Improvement Backlog
Maintain a visible Nexus improvement backlog. Review completion at the start of every Nexus Sprint Retrospective Part 1. Stale items signal that improvements aren’t being prioritized.
08
Integration Metrics Dashboard
Track and display integration health metrics over time: build success rates, integration test pass rates, dependency count per Sprint. Data makes the retrospective conversation concrete rather than subjective.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Teams

Team-level improvements owned by the team; Nexus-level issues elevated for shared resolution

NIT

Cross-Nexus improvement items with owners; insight into integration practice maturity; coaching priorities

The Nexus

1–2 concrete, shared improvement actions for the next Sprint; stronger cross-team trust

Goal

Identify cross-Nexus issues that individual teams can’t resolve alone

Goal

Each team identifies team-level improvements

Goal

The Nexus agrees on shared improvement actions with owners

Goal

Improvement items are concrete enough to execute in the next Sprint

Cross-Framework Definition
See Nexus Sprint Retrospective in the glossary
→