View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Planning Poker |  Decision Making Force Field Analysis |  Agile 4Ls Retrospective |
|---|---|---|---|
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. |
Complexitysame | Low | Low | Low |
Timedifferent | 2-5 min je Item | 45-90 min | 45–75 min |
Participantsdifferent | 3-9 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Force Field Map, Change Levers, Risk Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | EstimationAgileRelative sizingTeam | ChangeDecisionStrategy | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
