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 Planning Poker.
Agile
Planning Poker
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
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 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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
Complexitydifferent
LowMediumLowLow
Timedifferent
2-5 min je Item30-90 min45-90 min1-2 h
Participantsdifferent
3-93-123-122-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesAffinity Size Map, Grouped Estimates, Unclear ItemsForce Field Map, Change Levers, Risk NotesDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
ChangeDecisionStrategy
StrategyDecisionAssumptionsHypothesis
Add more methods