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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Learning Review.
Operations
Learning Review
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
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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-60 min1-3 h45–75 min
Participantsdifferent
Scrum Team3-103-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsEmotion Board, Themes, Action ItemsLearning Review Notes, System Factors, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tags1 shared
RetrospectiveImprovementLearning
RetrospectiveTeamReflection
LearningRetrospectiveIncidentOperations
RetrospectiveLearningReflectionTeam
Add more methods