Demo of the work itself (this should be the vast majority of the meeting).Key decisions that were made during the iteration/sprint (this may include technical, market-driven, requirements, etc, and can be decisions made by the team, the product owner, the customers, or anyone else).The work the team committed to delivering.The customers should be reviewing the following data: The meeting is facilitated by the product owner but it is not uncommon to have the developers or delivery people run the meeting. The purpose of the meeting is for the team to show the customers and stakeholders the work they have accomplished over the sprint so that the entire Scrum team can receive feedback to fine-tune the product backlog and release plan. The sprint review occurs on the last day of the sprint. Additionally, the team should spend no more than one hour preparing for the review.
A two-week sprint would result in a two-hour review and a one-and-a-half hour retrospective. For example, a 30-day sprint would result in a four-hour review and a three-hour retrospective. 75 hours (45 minutes) for each week of sprint duration. For each week of sprint duration, apply one hour of meeting time for the sprint review. The sprint retrospective is focused on how the team worked together during the sprint. It starts with a customer review and demonstration and ends with discussion and updates to the product backlog and release plan. The sprint review is focused on the product increment created during the sprint. Both of these components occur on the last day of the sprint. Timing for Sprint Reviews & RetrospectivesĮach sprint ends with a sprint review and sprint retrospective.
0 kommentar(er)
