• The main objective is to gather practical feedback from the gathered  Stakeholders.
• The review is done by the Product owner vis-a-*** the Sprint goals identified. 
• Items from the Product Backlog are also discussed *** prioritized.
• Discuss the next Sprint

• Align the goals and outcomes of Sprint.
• The demo is conducted to fit-the-purpose
• Engagement from the team to discuss the entire Sprint – issues and challenges faced; technical limitations or any other factor that did not allow the team to function optimally.

However, if the Sprint is shorter than a month, then the duration of the Sprint Review is shorter.

• He is the main organizer of the meeting.
• He is responsible for briefing everyone about the work that has been done by the Development team in Sprint;
• The Product Owner then addresses the Product Backlog – discussions related to current market trends and customer requirements are done.
• Each item of the Product Backlog is discussed and prioritized for the next Sprint.
• Simultaneously, budgets and timelines are reviewed and finalized.

• Evaluate the acceptance criteria of the deliverable;
• Ensure that the deliverable meets the Sprint Goal;
• Give feedback 
• Accept the delivery or reject it;
• Plan for the next Sprint;
• Take  questions from members present;
• Give suggestions. 
• Engage in constructive criticism, if required.

#2 – The Development Team then talks about their experience during the Sprint; what all went off well and what did not; the problems that crept up during the Sprint; and the way these were resolved.

#3 – Next, the Development Team carries out a demonstration to show everyone what has been ‘done’.

#4 – The Development Team will then answer questions from those present about increments.

#5 – Next, the Product Owner takes over and discusses the current status of the Product Backlog.

#6 – If required, the Product Owner revisits the target and the timeline depending on the present status of product development.

#7 – now, the discussion opens for everyone. They decide on the next course of action. The objective is to offer inputs and insights for the upcoming Sprint Planning exercise.

#8 – The Sprint Review is also about reviewing the potential user or the market to understand if there are changes in their need and preferences, depending on which the next to-do gets decided.

#9 – Finally the schedule, budget, user, and potential capabilities are reviewed vis-a-vis the next functionality to be released.

#2 – It is the ultimate test time when the Development Team needs to show off everyone presents the value-driven features developed.

#3 – The purpose should be to make the demo as interesting and engaging as possible; and avoid making it boring and unfocused.

#4 – The team gathers around to demonstrate what has been ‘done’ to tell everyone if the developed product meets the acceptance criteria.

#5 – Since the entire Sprint Demo is focused on the actual demo, there are lots ** preparations to be done. It is important to use test data and tools to be one hundred percent sure of the criteria being met.

#6 – The demo should be about narrating a story. That is why great Sprint Demos are about carrying for the demonstration using realistic user problems.

#7 – The purpose of the Sprint Demo is about showing how user problems get solved using the product. It should not merely to show-for the features and functionality of the product.

#8 – One of the main elements of the Sprint Demo is to show how the product adds value. Hence, the demo is ideally kept short, covering a few acceptance criteria at one time.

• Form a revised Product Backlog, and
• Preparing for the next Sprint by defining the likely items from the Product Backlog.
• Possible readjustment of the Product Backlog to address newer opportunities.

• A demo of the work done in a Sprint is shown to internal Stakeholders.
• Keeping everyone updated on the progress of the product.
• The feedback from internal Stakeholders and team members

It is also the best way to let across different departments and roles know what to expect from the product – it is the right platform to formally share information with cross-functional teams.

• Though the Product Owner is the key initiator and coordinator, however, this is about collaborative efforts between individual team members.
• The points of discussion should be pre-decided and refined to use time well.
• Only relevant people should be called in for the review.
• It is good to stay focused on the topic.
• Sprint Reviews are good for a healthy Scrum Team.

• This is a must-have practice in all forward-looking Agile organizations. It is good to earmark a date, book a room; send emails to all concerned, and prepare for the demo.
• Sprint Demos should be about sharing information across teams. It is good to make it a part of the organizational culture on a regular basis.
• Sprint Demos should be kept short and focused. Instead of covering all acceptance criteria in one go, the demo should be made interesting by focusing on value-additions.
• It is important to prepare the practice for the demo so that the Sprint Demo goes well.