View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy PESTLE Analysis | ![]() Agile Example Mapping | ![]() Business Strategy SWOT Analysis | ![]() Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 2-10 | 3-7 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | PESTLE Map, External Risks, Strategic Questions | Example Map, Acceptance Criteria, Open Questions | SWOT matrix, Strategic options, Action list | Example Table, Acceptance Tests |
Tagsno overlap | StrategyMarketAnalysis | Behavior-Driven DevelopmentRequirementsExamplesRefinement | StrategyAnalysisMarketPositioning | AgileRequirementsExamplesBehavior-Driven Development |



