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 |  Business Strategy Scenario Planning |  Agile Example Mapping |  Product Strategy Impact Mapping |
|---|---|---|---|---|
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. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 60-90 min pro Feature | 0.5-2 Tage | 30-60 min | 45-90 min |
Participantsdifferent | 3-6 | 4-12 | 3-7 | 3-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Scenario Set, Strategic Implications, Robust Options | Example Map, Acceptance Criteria, Open Questions | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | StrategyUncertaintyPlanning | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OutcomesStrategyBehaviorPlanning |