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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.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.
Complexitysame
LowLowLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter20-45 min30-60 min45–75 min
Participantsdifferent
Scrum Team1-83-10Team members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsOwnership Reflection, Action Commitment, Coaching NotesEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementLearning
ResponsibilityLeadershipTeam
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods