One of the most important events in Scrum is the sprint review, or sprint demo. 0:00 This is when the team gathers to show off the work completed in the sprint. 0:05 Stakeholders or clients from outside the team are usually invited and 0:10 given the opportunity to see the team's progress and ask questions or 0:14 provide feedback on the direction of the work. 0:18 Do you remember how the Agile Manifesto declares the value of working software 0:20 over comprehensive documentation? 0:25 The sprint review centers around demonstrating 0:28 potentially shippable product. 0:30 The team demonstrates the result of each product backlog item, or 0:33 user story showing how it works in software. 0:36 The sprint review does not have to be a long meeting. 0:39 I prefer short sprint reviews of a half an hour or less. 0:43 I find that stakeholders are more happy to attend, 0:47 if they know the event will be brief and a good use of their time. 0:50 The product owner should also have an opportunity 0:53 to gather feedback from the stakeholders. 0:57 This can happen as stakeholders ask questions during the sprint review or 0:59 in followup conversations with the stakeholders. 1:03 The sprint review is generally a celebration of the team's successes and 1:05 a demonstration of working software. 1:10 However, transparency is valued, and the team should also acknowledge the work 1:13 the team committed to that did not get finished. 1:18 And the challenges they discovered. 1:20 This will help keep stakeholders up to date and informed, and 1:22 also help the team work together to make better estimates on future work. 1:26