View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogSprint RetrospectiveStrategic, Tactical and Operational PlanningStrategy Execution Loop
| Criterion |  Delivery RAID Log |  Agile Sprint Retrospective |  Business Strategy Strategic, Tactical and Operational Planning |  Business Strategy Strategy Execution Loop |
|---|---|---|---|---|
Purposedifferent | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Low | Low | Medium | High |
Timedifferent | 30 min Setup, dann laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 90-180 min | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Scrum Team | 4-12 | 5-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Improvement actions, Team agreements | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementLearning | CadenceGovernanceExecution | ExecutionCadenceLearningGovernance |