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
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Story Splitting method illustration showing its working structure
Agile
Story Splitting
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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-90 min2-5 min je Item1-4 Wochen je Sprint, laufend30-60 min
Participantsdifferent
3-123-93-10 (Scrum Team)2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesProduct Backlog, Sprint Backlog, Increment, Sprint GoalSmaller Stories, Acceptance Criteria, Split Rationale
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
AgileIterationCadence
BacklogIterationDelivery
Add more methods