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
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 Open Space Technology.
Facilitation
Open Space Technology
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.When a complex topic does not yet have a fitting agenda, Open Space Technology hands topic ownership back to the participants. The format suits questions that only move forward when real interest determines the order.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.
Complexitydifferent
LowHighLow
Timedifferent
45–75 min0.5-2 TageUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
Team members involved20-500+Scrum Team
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsSession Marketplace, Proceedings, Action TopicsImprovement actions, Team agreements
Tagsno overlap
RetrospectiveLearningReflectionTeam
FacilitationLarge groupAutonomy
RetrospectiveImprovementLearning
Add more methods

Often compared together

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

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 for Sailboat Retrospective
Agile
Sailboat Retrospective