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 Bucket System.
Agile
Bucket System
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
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 large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min30-60 min2-5 min je Item45–75 min
Participantsdifferent
3-123-123-9Team members involved
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Bucketed Backlog, Relative Estimates, Split CandidatesStart Stop Continue Board, Improvement ActionsRelative Estimates, Assumption Notes, Split Candidates4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
EstimationBacklogRelative sizing
RetrospectiveImprovementTeamReflection
EstimationAgileRelative sizingTeam
RetrospectiveLearningReflectionTeam
Add more methods