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 PlanningSpecification by ExampleScrumStrategy Execution Loop
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Specification by Example |  Agile Scrum |  Business Strategy Strategy Execution Loop |
|---|---|---|---|---|
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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 90-180 min | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 4-12 | 3-6 | 3-10 (Scrum Team) | 5-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | CadenceGovernanceExecution | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | ExecutionCadenceLearningGovernance |