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 Planning Poker.
Agile
Planning Poker
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitysame
LowLowLow
Timedifferent
2-5 min je Item45–75 min30-60 min
Participantsdifferent
3-9Team members involved3-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split Candidates4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tags1 shared
EstimationAgileRelative sizingTeam
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

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

Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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 Starfish Retrospective
Agile
Starfish Retrospective