Table of contents
Overview
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 the following:
- 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.
Participants
- All members of Scrum Team
- Scrum Master
- Product Owner (optional)
Outcomes
- Identified improvements that it will implement in the next Sprint.
- To improve its process and practices to make it more effective and enjoyable.
- To increase product quality by improving work processes.
- To adapt the definition of “Done” if appropriate.