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 |  Agile Acceptance Criteria Workshop |  Decision Making OODA Loop |
|---|---|---|---|---|
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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-90 min | 20-40 min pro Story | 15-60 min je Zyklus |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 3-6 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Force Field Map, Change Levers, Risk Notes | Acceptance Criteria, Story Update | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | AgileIterationCadence | ChangeDecisionStrategy | AgileRequirementsRefinementBehavior-Driven Development | DecisionChangeLearningStrategy |