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 4Ls Retrospective |  Agile Affinity Estimation |  Decision Making Force Field Analysis |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 30-90 min | 45-90 min | 2-5 min je Item |
Participantsdifferent | Team members involved | 3-12 | 3-12 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Affinity Size Map, Grouped Estimates, Unclear Items | Force Field Map, Change Levers, Risk Notes | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | RetrospectiveLearningReflectionTeam | EstimationBacklogRelative sizing | ChangeDecisionStrategy | EstimationAgileRelative sizingTeam |