# Sprint Retrospective

> The meeting at the end of each sprint where the team improves the way it works.

**Field:** Business & Startups  
**Category:** Agile Delivery  
**Also known as:** Retrospective, Retro

## Think of it like

It is like a team talk after a match. Not about the score. It is about how you played.

## Definition

The Sprint Retrospective is the last event of a sprint. The Scrum Team looks at how it worked, not at what it built. It asks what went well, what went wrong and why. Then it picks the most useful changes to try. Some may go straight into the next sprint's plan. It takes up to three hours for a one-month sprint.

## Example

Emma's team finds that half its bugs came from rushed code reviews. They agree that in the next sprint, no code goes in without a second reader.

## Why it matters

A team that never looks at how it works repeats the same mistakes. Small fixes each sprint add up fast.

## Common mistake

Listing problems and changing nothing. A retro is only done when the team picks a change and tries it.

## Three principles

- **How, not what.** Look at the way of working.
- **Pick a change.** Choose a few things to improve.
- **Every sprint.** Small fixes, made often.

## Related terms

- [Sprint](https://learn.benibix.com/term/business/sprint)
- [Sprint Review](https://learn.benibix.com/term/business/sprint-review)
- [Lessons Learned](https://learn.benibix.com/term/business/lessons-learned)
- [Scrum Team](https://learn.benibix.com/term/business/scrum-team)
- [Scrum Master](https://learn.benibix.com/term/business/scrum-master)

## Told apart from

- [Sprint Review vs Sprint Retrospective](https://learn.benibix.com/compare/sprint-review-vs-sprint-retrospective): People think the review and the retrospective are one meeting. The review looks at the product, with stakeholders in the room. The retrospective looks at how the team worked, and only the team is there.

## Taught in

- [Sprint Review vs Retrospective](https://learn.benibix.com/learn/business-agile/sprint-review-vs-retrospective): Agile and Scrum, 8/19

![A loop drawn left to right. The product backlog, a stack of cards, feeds sprint planning, up to 8 hours. That makes the sprint backlog. Then comes the sprint, one month or less, a large box in the accent colour with a small loop inside marked daily scrum, 15 minutes. The sprint ends in an increment. It is followed by the sprint review, up to 4 hours, and the sprint retrospective, up to 3 hours. An arrow runs from the retrospective back to the product backlog.](https://learn.benibix.com/diagrams/agile-scrum-cycle.svg)

---

Source: https://learn.benibix.com/term/business/sprint-retrospective
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-16
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
