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