Skip to content
BENIBIX Learn

Sprint Retrospective

Business📋 Agile DeliveryScrum

Also known as Retrospective, Retro

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

Think of it like

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

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.

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.
The retrospective closes the loop. What the team learns about itself feeds the next sprint.

Common mistake

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

Key takeaways

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

Compare

Learn it properly