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 GAP Analysis |  Business Strategy PESTLE Analysis |  Agile Example 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 1-3 h | 30-60 min |
Participantsdifferent | 3-6 | 2-8 | 2-10 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Gap Matrix, Action Plan, Risk Notes | PESTLE Map, External Risks, Strategic Questions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | StrategyAnalysisPlanning | StrategyMarketAnalysis | Behavior-Driven DevelopmentRequirementsExamplesRefinement |