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
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min45–75 min30-90 min30-60 min
Participantsdifferent
3-12Team members involved3-123-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear Items4Ls Board, Learning Themes, Improvement ActionsPostmortem Doc, Action Items, TimelineEmotion Board, Themes, Action Items
Tagsno overlap
EstimationBacklogRelative sizing
RetrospectiveLearningReflectionTeam
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveTeamReflection
Add more methods