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 Strategic, Tactical and Operational Planning |  Agile Specification by Example |  Agile Example Mapping |  Agile Scrum |
|---|---|---|---|---|
Purposedifferent | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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 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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 60-90 min pro Feature | 30-60 min | 1-4 Wochen je Sprint, laufend |
Participantsdifferent | 4-12 | 3-6 | 3-7 | 3-10 (Scrum Team) |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Product Backlog, Sprint Backlog, Increment, Sprint Goal |
Tagsno overlap | CadenceGovernanceExecution | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileIterationCadence |