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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Bucket System.
Agile
Bucket System
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.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.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-90 min2-5 min je Item45-90 min30-90 min
Participantsdifferent
3-123-93-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesForce Field Map, Change Levers, Risk NotesBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
ChangeDecisionStrategy
EstimationBacklogRelative sizing
Add more methods