Sprint Review

Sprint review is an informal meeting held at the end of the Sprint where the increment is presented to promote the collaboration and obtain the customer’s feedback on the developed product. It is mainly conducted to ‘Inspect’ the Increment and ‘Adapt’ the Product Backlog if required.

What is the purpose of the Sprint Review?

While developing a product in Scrum, it is mandatory to deliver a potentially shippable product increment at the end of every Sprint. A potentially shippable product means the team has constructed a coded, tested and usable chunk of software.

For this reason, a Sprint Review meeting is held at the end of each Sprint. During this meeting, the Scrum team demonstrates what they achieved during a sprint. Basically, the Sprint Review appears as a demo of the new features.

Who all attends the Sprint Review?

The Scrum team and the stakeholders collaborate during a Sprint Review and discuss what was done in the last Sprint and what more changes are required in the product. Based on this review, all the participants collaborate and decide on the things that could be done to get an optimized value.

What is the duration of the Sprint Review?

Sprint review does not have a fixed time frame. This meeting lasts at most for 4 hours for a one-month Sprint. The duration can be shorter for shorter sprints. The Scrum Master facilitates the event and makes sure the participants understand the purpose of the event. The Scrum Master keeps this event time-boxed.

What happens in a Sprint Review?

A Sprint Review includes the following events:

• Attendees include the Scrum Team and key stakeholders if invited by the Product Owner;
• The Product Owner discusses the ‘done’ and ‘what has not been done’ items of the Product Backlog,
• The Development team explains what went well during a Sprint, what obstacles they faced, and how they resolved those problems
• The Development team elaborates the ‘done’ work, and justifies the Increment,
• The Product Owner discusses the Product Backlog. He or she projects likely target and delivery dates based on progress to date (if needed)
• The team collaborates and plans for the next Sprint goal. In this case, Sprint Review helps with the valuable inputs for the upcoming Sprint Planning,
• The team does a research on the marketplaces and decides on the next to-do product accordingly. Also, the team estimates the budget, potential capabilities, timeline, and marketplaces for the upcoming releases based on the functionality of the product.

Output of the Sprint Review

Thus, keeping all these factors in mind, a revised Product Backlog is the result at the end of the Sprint review. The revised Product Backlog consists of the probable Product Backlog items for the next Sprint. Also, the Product Backlog can be adjusted according to the new market demands.