The Sprint Review gathering is a time boxed event in Scrum. The particular maximum duration is four hours for a four week sprint, and proportionately less for smaller Sprints. The Sprint Review is held in late the Run or iteration and is utilized to demonstrate the work that was done during the Sprint.

The Sprint Evaluation is conducted by any part of the team. People that may be present include the Scrum team and some other outside customers, stakeholders or serious people that the Item Owner might invite. Typically the Sprint Review generally includes an exhibition of the work done. The 'demo' though, is not the single or main reason for the review.

The atmosphere for a Sprint Review is one of collaboration. The item 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 the go back to the product backlog to be reprioritized. The team answers any questions about the work done.

This is an important time for they 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 discussing current business focus with the Product Proprietor. Items on the Item Backlog are discussed and the team considers what it 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 hard work. Any accolades or reward are given to the complete 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 responsibility for the outcome of the Sprint and any lessons learnt are for everybody.

The Sprint Review provides 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 at the end of 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 very 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 be familiar with success standards for every product backlog item. Any item that will not adhere to the definition of 'done' determined earlier is not included in the Sprint review. This specific item has to return 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 Adjust

Even though the daily standup is utilized to inspect a day's work, the Sprint Review is an important time for you to 'inspect' the steps taken throughout the whole Sprint period. They adjusts its workload and 'adapts' its velocity. Following experimenting for a few iterations, they gets a good idea of its velocity and can then be more accurate in their planning.