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
Paper illustration for Planning Poker.
Agile
Planning Poker
Story Splitting method illustration showing its working structure
Agile
Story Splitting
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.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 story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.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
MediumLowMediumLow
Timedifferent
30-90 min2-5 min je Item30-60 min15-60 min
Participantsdifferent
3-123-92-62-9
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesSmaller Stories, Acceptance Criteria, Split RationaleIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
BacklogIterationDelivery
EstimationEffortAgile
Add more methods