What is a Sprint Review Meeting and who should attend this?

1.	What is a Sprint Review Meeting and who should attend this?
Answer» MANDATORY Attendees: Development team, Scrum Master and Product Owner Optional Attendees: Project Stakeholders When should review be done: The most common answer is to have review/demo at the end of the sprint. However, that works if the amount of user STORIES to be reviewed is small enough. For COMPLEX projects, where the stakes are high, it is recommended to have a regular cadence of review every week for the finished user stories. This reduces risk and allows the developer enough time to make corrections, if something is not found right in the review. For EXAMPLE, It is fine to have a regular cadence of doing TECHNICAL reviews every Tuesday at 3 PM and Demo of finished stories every Thursday at 11 AM in the morning. If there is nothing to be reviewed or demoed then that meeting can be cancelled. Duration: 45-60 minutes

Answer»

MANDATORY Attendees: Development team, Scrum Master and Product Owner
Optional Attendees: Project Stakeholders
When should review be done: The most common answer is to have review/demo at the end of the sprint. However, that works if the amount of user STORIES to be reviewed is small enough. For COMPLEX projects, where the stakes are high, it is recommended to have a regular cadence of review every week for the finished user stories. This reduces risk and allows the developer enough time to make corrections, if something is not found right in the review. For EXAMPLE, It is fine to have a regular cadence of doing TECHNICAL reviews every Tuesday at 3 PM and Demo of finished stories every Thursday at 11 AM in the morning. If there is nothing to be reviewed or demoed then that meeting can be cancelled.
Duration: 45-60 minutes

Discussion