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
Paper illustration for T-Shirt Sizing.
Agile
T-Shirt Sizing
Paper illustration for Working Agreements.
Agile
Working Agreements
Paper illustration for Bucket System.
Agile
Bucket System
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 effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes.When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
2-5 min je Item15-45 min45-90 min30-90 min
Participantsdifferent
3-92-123-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesSize Buckets, Rough Backlog Map, Split CandidatesWorking Agreements, Team Norms, Review CadenceBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationAgileRoadmap
TeamCollaborationAgile
EstimationBacklogRelative sizing
Add more methods