Show your created value to get some new insights
In a typical sprint review (or demo) the team shows what they build to some stakeholders and project managers. Briefly, every story is shown and at the end of the session everybody says it was great and that was that. There is often no more outcome rather some critical remarks on very specific details ('that button looks too big for me...'). This is a useless session.
A Sprint Review should instead assure the Product Owner that he (or she) is delivering the most value. So, instead of focusing on the details of the developed software, the sprint review should focus on what kind of added value is delivered and what the PO is planning to add to the next sprint. A good review should at least give answer to the following two questions:
- Does the created new software deliver the requested business value?
- Are there new insights which can influence the priorities of the backlog?