The Sprint Review conference is a time boxed event in Scrum. Typically 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 Sprint or iteration and is employed to demonstrate the work that was done during the Sprint.
The Sprint Overview is conducted by any team member. People that may be present are the Scrum team and every other exterior customers, stakeholders or fascinated people that the Product Owner might invite. Typically the Sprint Review generally contains an indication of the work done. The 'demo' though, is not the only or main reason for 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 Short 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 item 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 priorities with the Product Owner. Items on the Merchandise Backlog are discussed and the team considers what could take on in the next sprint. This specific lays some groundwork for the next planning conference.
The work done in the Short is showcased as a group, be it natural or processed effort. Any accolades or reward are given to the entire team and not to any individual. Similarly, this is not used as a finger pointing opportunity in case of any remaining backlog items. The team assumes collective duty for the outcome of the Sprint and any lessons learnt are for all.
The Sprint Review provides a valuable possibility 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 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 understand the success standards for every product backlog item. Any object it does 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 open up defects.
Inspect and Adjust
Even though the daily standup is employed to examine a day's work, the Sprint Review is an important time and energy to 'inspect' the steps taken during the whole Sprint period. They adjusts its workload and 'adapts' its velocity. Following experimenting for a few iterations, they gets a good idea of the velocity and can then be more accurate in their planning.