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 T-Shirt Sizing.
Agile
T-Shirt Sizing
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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 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.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-45 min20-40 min initial, dann laufend2-5 min je Item30-90 min
Participantsdifferent
2-123-153-93-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Size Buckets, Rough Backlog Map, Split CandidatesROAM Board, Owner ListRelative Estimates, Assumption Notes, Split CandidatesAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
EstimationAgileRoadmap
RiskAgileTrackingAlignment
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
Add more methods