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 Specification by Example |  Product Strategy Impact Mapping |  Business Strategy Scenario Planning |
|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 60-90 min pro Feature | 45-90 min | 0.5-2 Tage |
Participantsdifferent | 3-6 | 3-8 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Impact Map, Outcome Hypotheses, Delivery Options | Scenario Set, Strategic Implications, Robust Options |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | OutcomesStrategyBehaviorPlanning | StrategyUncertaintyPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
