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 Scrum | ![]() Business Strategy Balanced Scorecard | ![]() Product Strategy DIBB | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Halber Tag bis mehrere Wochen | 1-2 h | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Balanced Scorecard, Strategic Measures, Initiative Map | DIBB document, Belief list, Bet list, Learning report | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileIterationCadence | StrategyMetricsExecution | StrategyDecisionAssumptionsHypothesis | ChangeDecisionStrategy |



