Sprint Review Meeting in Agile

Posted by BuyPhen375 on August 12th, 2017

The Sprint Review meeting is a time boxed event in Scrum. The maximum duration is four hours for a four week sprint, and proportionately less for smaller Pointe. The Sprint Review is held at the end of the Short or iteration and can be used to demonstrate the task that was done during the Sprint.

The Sprint Evaluation is conducted by any team member. People that may be present are the Scrum team and any other external customers, stakeholders or fascinated people that the Item Owner might invite. The Sprint Review generally contains a demonstration of the work done. The 'demo' though, is not the single or main aim of the review.

The atmosphere for a Sprint Review is one of collaboration. The merchandise Owner identifies which features were completed. The team reviews how much work it was able to handle, whether the Run backlog was cleared, and exactly what is remaining. The team discusses any pending items and these go back to the product backlog to be reprioritized. The team answers any questions about the work done.

This is an important time for the team members to interact with the Product Owner and understand what is occurring with the product. Part of the Sprint Review may also be used for reordering the Product Backlog and  sprint discussing current business focus with the Product Owner. Items on the Product Backlog are discussed and the team considers what could take on in the next Sprint. This particular lays some groundwork for the next planning meeting.

Unique Aspect

The work done in the Run is showcased as a group, be it natural or processed effort. Any accolades or praise are given to the whole team and not to any individual. Similarly, this is not used as a finger pointing opportunity in case of any remaining backlog items. Typically the team assumes collective duty for the outcome of the Sprint and any lessons learnt are for everybody.

The Sprint Review offers a valuable chance to the team to self-organize and realize their potential. If the team could fulfil the Sprint backlog easily with time left in late the Sprint, it realizes it can take on some more hours in the next Sprint. If the team is not able to finish the items on the backlog, it considers taking up less items the next time, or adding some more buffer for contingencies.

Is it 'done'?

An important part the Scrum Master plays is ensuring that they and the Product Owner understand the success standards for every single product backlog item. Any object that will not adhere to the definition of 'done' made the decision earlier is not supplied in the Sprint review. This item has to get back to the product backlog to be reprioritized. A typical example would be an item that is coded but not tested or an item with available defects.

Inspect and Adapt

As the daily standup can be used to examine a day's work, the Sprint Review is an important time to 'inspect' the steps taken through the whole Sprint period. They adjusts its workload and 'adapts' its velocity. After experimenting for a few iterations, the team gets a good idea of the velocity and can then be more accurate in their planning.