Sprint Review and Sprint Retrospective

The last of a SCRUM Sprint typically ends with two major ceremonies, Sprint Review and Sprint Retrospective

• Sprint Review
• Sprint Retrospective

These two Sprints look at different aspects of the completing Sprint.

Video: Sprint Review & Sprint Retrospective

Sprint Review

This is also known as Sprint Demo. The Sprint Review is based on the “Inspect and Adapt” principle. Here the SCRUM team demonstrates the working code of what was achieved from the Sprint goals. This is an opportunity for stakeholders or customers to provide feedback on the work done. The feedback given can be taken as a Product Backlog item for the current Sprint or a future Sprint based on the priority.

The participants of Sprint Review typically include:

• The SCRUM Master
• Product Owner
• SCRUM Team
• Other interested Stakeholders

Sprint Retrospective

The Sprint Retrospective is also a ceremony that happens on the last day of the Sprint. This is also a timeboxed meeting whose purpose is to

• Identify what went well in the previous iteration
• Identify what did not go well in the rpevious iteration
• Create a plan with action items to address the first two points

Keep in mind that this is not a finger-pointing exercise. Everything that can help the SCRUM achieve further efficiency can be openly discussed. The concept of Sprint Retrospective evolved from the Japanese continuous improvement philosophy called “Kaizen” (meaning: change for good). The idea here is to take feedback from the team itself on how to improve further.