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 Sprint Retrospective |  Decision Making Force Field Analysis |  Product Strategy DIBB |
|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitysame | Low | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 1-2 h |
Participantsdifferent | Scrum Team | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | RetrospectiveImprovementLearning | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
