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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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.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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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
LowLowLowMedium
Timedifferent
2-5 min je Item45-90 min45–75 min15-60 min je Zyklus
Participantsdifferent
3-93-12Team members involved1-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesForce Field Map, Change Levers, Risk Notes4Ls Board, Learning Themes, Improvement ActionsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
EstimationAgileRelative sizingTeam
ChangeDecisionStrategy
RetrospectiveLearningReflectionTeam
DecisionChangeLearningStrategy
Add more methods