Nexus Events

Nexus Sprint Retrospective

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