GuideRolesEventsWorkflow

Nexus Events

Nexus Sprint Review

The Nexus Sprint Review replaces individual team Sprint Reviews. The entire Nexus presents the Integrated Increment to stakeholders. This is one review for the whole product — demonstrating that the combined work of all teams creates integrated value.

Integrated product review · Timebox: ≤4 hours (1-month Sprint)

Overview

The Nexus Sprint Review replaces individual team Sprint Reviews. The entire Nexus presents the Integrated Increment to stakeholders. This is one review for the whole product — demonstrating that the combined work of all teams creates integrated value.

Event Ownership

Owned / Facilitated By
Product Owner (content) / NIT Scrum Master (facilitation)
PO frames the review around product progress and the Product Goal
NIT SM facilitates the session, ensures stakeholder engagement, and manages the timebox
Teams demo their portions of the Integrated Increment — showing how their work integrates
PO captures feedback and adapts the Product Backlog based on stakeholder input

Who Should Be Present

All Nexus Teams
Present and demo the Integrated Increment. Show how their work integrates with other teams’ work
Product Owner
Frames progress, facilitates discussion, captures feedback, adapts the Product Backlog
Stakeholders
Provide feedback on the Integrated Increment. Share market context and emerging needs
NIT
Demonstrates integration quality. Shows how the product works as a whole, not as separate pieces

Preparation Checklist

01NIT: Ensure the Integrated Increment is working and demo-ready in a realistic environment
02Teams: Prepare demo of their integrated contributions
03PO: Prepare product progress context and discussion topics
04NIT SM: Invite stakeholders, prepare facilitation plan

Facilitation Techniques

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

End-to-End Scenario Demo

Demo the product through a complete user scenario that crosses multiple teams’ work. This proves integration quality and shows the product as users experience it — not as developers built it.

Click to expand

Feedback Capture Matrix

Use a structured matrix: What impressed you / What concerned you / What questions do you have / What would you prioritize. Captures feedback in actionable categories.

Click to expand

Tips & Tricks

01
One review for the whole product — not separate demos per team
02
Show the Integrated Increment, not individual team outputs stitched together
03
If integration isn’t complete, show that transparently — hiding problems delays resolution
04
Stakeholders should interact with the product when possible, not just watch a demo
05
Capture feedback visibly and close the loop by showing how it influenced the backlog
06
Backlog Adaptation within 24 Hours
PO should reorder the Product Backlog based on Sprint Review feedback before the next Sprint Planning. New insights should influence priorities immediately.

Success Takeaways by Role

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

Teams

Validation that their work integrates and creates value; direct connection to stakeholder needs

Product Owner

Rich feedback for backlog adaptation; stakeholder alignment on product direction

NIT

Objective evidence of integration quality; feedback on integration improvements needed

Stakeholders

Confidence in product progress; influence on direction; understanding of trade-offs

Goal

Demonstrate the Integrated Increment as one working product

Goal

Gather stakeholder feedback that informs Product Backlog adaptation

Goal

Discuss progress toward the Product Goal

Goal

Build stakeholder confidence through working software

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