1. Home
  2. Training Library
  3. Sprint Review, Retrospective and Working at Scale

Sprint Review, Retrospective and Working at Scale

Contents

keyboard_tab
Facilitating Purposeful Agile Meetings
1
The Sprint Review
PREVIEW2m 49s

The course is part of this learning path

play-arrow
The Sprint Review
Overview
DifficultyBeginner
Duration13m
Students142
Ratings
5/5
starstarstarstarstar

Description

Course Description

This module outlines the sprint review and retrospective. It also focusses on how you can support your team and product owner with their product backlog refinement. Finally, you’ll learn about how you can scale scrum with a scrum of scrums.

Learning Objectives

The objectives of this course are to provide you with and understanding of: 

  • What the sprint review is 
  • What the sprint retrospective is 
  • Best practice for product backlog refinement
  • The extent of scrums scalability  

Intended Audience 

This course is aimed at Scrum Masters who want to improve their individual knowledge of facilitating scrum events in service to their Scrum team and their wider organization 

Prerequisites

There are no specific pre-requisites to study this course 

Feedback 

We welcome all feedback and suggestions - please contact us at qa.elearningadmin@qa.com to let us know what you think. 

Transcript

It is time to review the product increment that's being 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 the ensure that the review takes place and that we attendees know that the meeting is a collaborative one, helping to the 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 the 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
Students3379
Courses36
Learning paths9

Tony has over 20 years’ experience in Business Development, Business Change, Consulting and Project/Programme Management working with public, private and third sector organisations.

He has helped organisations to design and create process and procedures to align ways of working with corporate strategy. A highly motivated and detailed solution provider utilising a wide range of methods and frameworks to provide structure whilst promoting creativity and innovation.

As a confident and self-motivated professional with excellent communication skills Tony is able to bring people together and get them working as a team quickly.

Tony is an Agile and Scrum trainer with a vast knowledge spanning IT Systems, Business Change, Programme and Project Management. With excellent presentation skills and a solid background, he ensures that all clients gain maximum benefit from his training. He has successfully guided those new to the industry through their initial training, helped experienced staff as they progress in their careers and worked at Director level advising on best use and practice, as well as tailoring courses to fulfil the exact needs of clients.