The review meeting is a critical ceremony for the team and for the initiative that is underway. Do it right and you'll get all the valuable feedback you need (accepted backlog items, corrections, etc). Do it wrong and you'll get angry and frustrated business stakeholders and no objective feedback that helps you determine where to move next. Too many review meetings fail almost before they start. This is because business stakeholders expectations are not properly managed. The lack of focus on the critical goal - validate items against objective acceptance criteria - brings a sort of a chaos inside the demo, with the users not knowing exactly what to validate. This leads to a lot of waste, especially if you have all the users trying the application. A lot of times, the team doesn't do a proper wrap-up, allowing backlog items to remain in an "almost done" status, just because someone didn't ask directly to the business stakeholders and Product Owner to accept that the Work item is complete and accepted. Within this presentation I'll share an effective way to structure your review meeting, and I'll provide some tools and techniques that will help you maintain the team on the right track, creating what is more important!