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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration for Planning Poker.
Agile
Planning Poker
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 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 a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.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
MediumMediumMediumLow
Timedifferent
30-90 min30-60 min1-4 Wochen je Sprint, laufend2-5 min je Item
Participantsdifferent
3-122-63-10 (Scrum Team)3-9
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationaleProduct Backlog, Sprint Backlog, Increment, Sprint GoalRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
EstimationBacklogRelative sizing
BacklogIterationDelivery
AgileIterationCadence
EstimationAgileRelative sizingTeam
Add more methods