View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Force Field Analysis | ![]() Agile Sprint Retrospective | ![]() Decision Making Delphi Method | ![]() Product Strategy DIBB |
|---|---|---|---|---|
Purposedifferent | 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 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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-4 Wochen | 1-2 h |
Participantsdifferent | 3-12 | Scrum Team | 6-30 Experten | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Improvement actions, Team agreements | Expert Forecast, Consensus Range, Assumption Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | ChangeDecisionStrategy | RetrospectiveImprovementLearning | ForecastingExpertsDecisionStrategy | StrategyDecisionAssumptionsHypothesis |



