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 LoopStrategic, Tactical and Operational PlanningScrumAfter-Action Review
| Criterion |  Business Strategy Strategy Execution Loop |  Business Strategy Strategic, Tactical and Operational Planning |  Agile Scrum |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 90-180 min | 1-4 Wochen je Sprint, laufend | 20-45 min |
Participantsdifferent | 5-12 | 4-12 | 3-10 (Scrum Team) | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Lessons learned, Action items, Event summary |
Tagsno overlap | ExecutionCadenceLearningGovernance | CadenceGovernanceExecution | AgileIterationCadence | LearningOperationsImprovement |