View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery User Story Mapping |  Delivery Shape Up |  Agile Affinity Estimation |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 30-90 min | 2-5 min je Item |
Participantsdifferent | 4-10 | 2-4 pro Pitch | 3-12 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Story Map, Release Slices, Backlog Candidates | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Affinity Size Map, Grouped Estimates, Unclear Items | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | BacklogJourneyPlanningMVP | PlanningDeliveryAutonomy | EstimationBacklogRelative sizing | EstimationAgileRelative sizingTeam |