The course is part of this learning path
Module 4 – The Scrum Events
This module introduces the five different events that happen in Scrum: Sprint Planning, the Daily Scrum, The Sprint, the Sprint Review and the Sprint Retrospective. This module is made up of Videos, followed by a quiz to help support your understanding.
- Sprint Planning
- The Daily Scrum
- The Sprint
- Sprint Review
- Sprint Retrospective
- Once the sprint is finished it's time to review the product increment that's been created. Let's talk about sprint reviews. A sprint review is held at the end of the sprint right before the Retro. The main purpose of the review is to inspect the item increments and adapt the product backlog based on the review. The attendees of the review should include the scrum team, the product owner, Dev team and scrum master, and the stakeholders of the product that have been invited by the PO. The Scrum Team and stakeholders review the work that was completed during the sprint. This should include live product demos to show the working state of the product increment. The review is an informal meeting. It shouldn't be about status. It's entirely about getting feedback on what has been done and should be done next. The review is a time-boxed meeting, meaning it shouldn't exceed the length of time assigned to it. For a one month Sprint, the time-box is four hours. If the Sprint is shorter adapt the Sprint review accordingly. A two week Sprint would be two hours for example. The Scrum Master must ensure that everyone in attendance adheres to the time-box. The Scrum Master has to ensure that the review takes place and that the attendees know that the meeting is a collaborative one helping to guide the development of future increments of the product. The Sprint review must also include the product owner explaining which backlog items are done and which ones aren't, the Dev team explaining what went well and what didn't go so well in the Sprint, the product owner being able to project what items will meet projected delivery dates and which ones won't based on current outputs, the entire group collaborating on what should happen next. This provides valuable information that can help direct the Sprint planning session. External factors should also be considered. For example, has there been a major shift in the marketplace that may affect the product, has there been a change in direction in the organization that may affect the product? These externalities may affect direction of the product and need to be considered. Finally the overall product timeline needs to be considered. Alongside the budget, potential capabilities and marketplace of the product. The main output of the review is a refreshed product backlog that reflects what is needed in the following and upcoming Sprints. This helps guide the development team on future Sprints, and ensures that the Scrum team as well as the product stakeholders are all clear on the development plan of the product.
About the Author
Paul Williams is a Senior Learning Consultant for QA, based in Manchester, UK. He is a member of the Agile, Lean & DevOps Trainer Team.