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 |  Delivery RAID Log |  Business Strategy Strategy Execution Loop |  Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30 min Setup, dann laufend | Initial 3-6 h, then monthly or quarterly reviews | 90-180 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 maintaining, briefing for everyone | 5-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | RAID Log, Status Report Source | Execution Loop, Review Cadence, Strategic Learning Log | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | AgileIterationCadence | RiskTrackingStakeholdersGovernance | ExecutionCadenceLearningGovernance | CadenceGovernanceExecution |