Key People not Attending the Sprint Review

It goes without saying that the Product Owner and the team must attend the meeting. Occasionally, with teams that are new to agile, there may be a tendency to see the review as a waste of time. In these situations, the Scrum Master needs to step in and help to create the sense of giving a rhythm to the sprint. The sprint review enhances this rhythm by providing a kind of endpoint where everybody gets together to establish what has been accomplished and celebrate what has been achieved.

The Sprint Review

In Agile software development, the Sprint Review Meeting is a demonstration meeting held at the end of every sprint. In it, the Scrum team showcases new features finished in the sprint. To some, this may seem excessive or unnecessary. Why have a review meeting after every sprint when you can just have one big review meeting at the end of the project? However, having a sprint review meeting at the end of every sprint yields several benefits.

The biggest benefit of the sprint review meeting is that it keeps all parties informed. Even roles who did not directly work on the project get regular updates. Stakeholders see features in action, within weeks after they are finished. Instead of going months or even years without new features, they see the fruits of new development often. In turn, developers and other scrum team roles see stakeholder reaction to their hard work. This can help steer future development.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course: