GuideRolesEventsWorkflow

LeSS Events

Sprint Review

In LeSS, there is one Sprint Review for the entire product — all teams together with real customers, users, and stakeholders. Teams demonstrate the integrated product increment, and the PO facilitates adaptive planning based on feedback.

Shared, whole-product · Timebox: ≤4 hours (1-month Sprint)

Overview

In LeSS, there is one Sprint Review for the entire product — all teams together with real customers, users, and stakeholders. Teams demonstrate the integrated product increment, and the PO facilitates adaptive planning based on feedback.

Event Ownership

Owned / Facilitated By
Product Owner (content) / Scrum Master (facilitation)
PO frames the review around product progress and strategic direction
SM facilitates the session, ensuring stakeholder voices are heard and feedback is captured
Teams demo their own work — showing the integrated, working product
PO uses feedback to adapt the Product Backlog ordering

Who Should Be Present

All Teams
Demo their completed work as part of the integrated product. Answer stakeholder questions directly
Product Owner
Frames progress, facilitates discussion, captures feedback, adapts the Product Backlog
Customers/Users/Stakeholders
Provide genuine feedback on the product increment. Share market context and emerging needs
Scrum Master
Facilitates the session, ensures all voices are heard, manages the timebox

Preparation Checklist

01Teams: Ensure the integrated increment is working and demo-ready
02PO: Prepare product progress context and discussion topics
03SM: Invite stakeholders, prepare facilitation plan
04Teams: Coordinate who demos what to avoid duplication

Facilitation Techniques

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

Bazaar / Science Fair Format

Set up stations for different feature areas. Stakeholders rotate between stations, interacting directly with the teams who built each capability. Great for many teams and many stakeholders.

Click to expand

Whole-Product Demo

Demo the product as a user would experience it — an end-to-end scenario that crosses multiple teams’ work. This demonstrates integration quality and whole-product thinking.

Click to expand

Tips & Tricks

01
One Sprint Review for the whole product — not separate reviews per team
02
Show the integrated product, not individual team outputs
03
Real customers and users should attend — not just internal stakeholders
04
The PO adapts the Product Backlog immediately based on feedback — don’t wait for the next planning session
05
This is a working session, not a presentation. If stakeholders aren’t interacting, the format needs to change
06
Immediate Backlog Adaptation
The PO should reorder the Product Backlog within 24 hours of the Sprint Review based on feedback. New insights should influence the very next Sprint’s priorities.

Success Takeaways by Role

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

Teams

Direct connection to customer reactions; pride in integrated product; understanding of what matters most to users

Product Owner

Rich feedback for backlog reordering; validated or challenged assumptions; stakeholder alignment

Customers/Stakeholders

Influence on product direction; confidence in development progress; understanding of trade-offs

Goal

Demonstrate the integrated product increment to real customers and stakeholders

Goal

Gather genuine, actionable feedback on the product

Goal

Adapt the Product Backlog based on new insights

Goal

Build trust through transparency and working software

Cross-Framework Definition
See Sprint Review in the glossary
→