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 for Sailboat Retrospective
Agile
Sailboat Retrospective
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 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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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
MediumLowLowLow
Timedifferent
30-90 min45-90 min30-60 min2-5 min je Item
Participantsdifferent
3-124-123-123-9
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Bucketed Backlog, Relative Estimates, Split CandidatesSailboat Board, Risks, Improvement ActionsStart Stop Continue Board, Improvement ActionsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
EstimationBacklogRelative sizing
RetrospectiveTeamImprovement
RetrospectiveImprovementTeamReflection
EstimationAgileRelative sizingTeam
Add more methods