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 Affinity Estimation.
Agile
Affinity Estimation
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Ideal Days.
Agile
Ideal Days
Purposedifferent
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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 needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min1-3 h2-5 min je Item15-60 min
Participantsdifferent
3-123-103-92-9
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsProcess Map, Handoff List, Improvement BacklogRelative Estimates, Assumption Notes, Split CandidatesIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
EstimationBacklogRelative sizing
ProcessOperationsImprovement
EstimationAgileRelative sizingTeam
EstimationEffortAgile
Add more methods