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 Planning Poker.
Agile
Planning Poker
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.
Complexitydifferent
LowLowMedium
Timedifferent
45–75 min2-5 min je Item30-90 min
Participantsdifferent
Team members involved3-93-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsRelative Estimates, Assumption Notes, Split CandidatesAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
Add more methods

Often compared together

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