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 Bucket System.
Agile
Bucket System
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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 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.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Complexitydifferent
LowMediumLowMedium
Timedifferent
2-5 min je Item30-90 min45-90 min15-60 min je Zyklus
Participantsdifferent
3-93-123-121-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesBucketed Backlog, Relative Estimates, Split CandidatesForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods