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 Affinity Estimation.
Agile
Affinity Estimation
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 Planning Poker.
Agile
Planning Poker
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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min30-90 min30-60 min2-5 min je Item
Participantsdifferent
Team members involved3-123-123-9
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsAffinity Size Map, Grouped Estimates, Unclear ItemsStart Stop Continue Board, Improvement ActionsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
RetrospectiveLearningReflectionTeam
EstimationBacklogRelative sizing
RetrospectiveImprovementTeamReflection
EstimationAgileRelative sizingTeam
Add more methods