View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopScrumSpecification by ExampleStrategic, Tactical and Operational Planning
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Scrum |  Agile Specification by Example |  Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 90-180 min |
Participantsdifferent | 5-12 | 3-10 (Scrum Team) | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | CadenceGovernanceExecution |