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 |  Decision Making Force Field Analysis |  Business Strategy Strategy Execution Loop |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-90 min | Initial 3-6 h, then monthly or quarterly reviews | Halber Tag bis mehrere Wochen |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 5-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Force Field Map, Change Levers, Risk Notes | Execution Loop, Review Cadence, Strategic Learning Log | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | AgileIterationCadence | ChangeDecisionStrategy | ExecutionCadenceLearningGovernance | StrategyMetricsExecution |