methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitysame
LowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-90 min
Participantsdifferent
Scrum Team4-12
Formatsame
WorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsSailboat Board, Risks, Improvement Actions
Tags2 shared
RetrospectiveImprovementLearning
RetrospectiveTeamImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review