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 of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Bucket System.
Agile
Bucket System
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.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.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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
LowLowHighMedium
Timedifferent
2-5 min je Item45-90 minHalf day30-90 min
Participantsdifferent
3-93-123-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesForce Field Map, Change Levers, Risk NotesLeverage Map, Action StrategyBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
EstimationAgileRelative sizingTeam
ChangeDecisionStrategy
Systems thinkingChangeStrategy
EstimationBacklogRelative sizing
Add more methods