View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategic, Tactical and Operational PlanningExample MappingThree AmigosSpecification by Example
| Criterion | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Agile Example Mapping | ![]() Agile Three Amigos | ![]() Agile Specification by Example |
|---|---|---|---|---|
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 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | 90-180 min | 30-60 min | 15-30 min | 60-90 min pro Feature |
Participantsdifferent | 4-12 | 3-7 | 3 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | CadenceGovernanceExecution | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development |



