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 |  Business Strategy Strategy Execution Loop |  Delivery RAID Log |  Product Discovery Product Kata |
|---|---|---|---|---|
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. | 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. | 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. | Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | Initial 3-6 h, then monthly or quarterly reviews | 30 min Setup, dann laufend | 1-2 Wochen je Loop |
Participantsdifferent | 3-10 (Scrum Team) | 5-12 | 1-3 maintaining, briefing for everyone | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Execution Loop, Review Cadence, Strategic Learning Log | RAID Log, Status Report Source | Direction, Current metric, Target metric, Experiment note, Learning report |
Tagsno overlap | AgileIterationCadence | ExecutionCadenceLearningGovernance | RiskTrackingStakeholdersGovernance | OutcomesDiscoveryLearningIterationCoaching |