Sprint Retrospective

Scrum Events: Sprint Retrospective

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.

The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

By Scrum Guide

The Sprint Retrospective needs special software like Jira, Trello board, Microsoft Planner, or anything available to conduct the sprint retrospective because we need to create an interactive board so everyone can participate.There are many ways to conduct a sprint retrospective. There are the 3 questions that we will go over in this video. There is the Plus-minus-delta retrospective, there is the tune and adjust, etc…
The Sprint Retrospective happens just after the sprint review is over. And it is timeboxed depending on how many weeks a sprint is. So this meeting will happen every time on the same day and time. So that means the Scrum Master should create the Sprint Retrospective meeting for the next 3 months in advance. Just by going over the organization calendar and invite the participants and make it recurring every 2 weeks. 

​