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 |  Architecture Architecture Decision Record |  Product Discovery Product Kata |  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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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 | 15-45 min | 1-2 Wochen je Loop | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 | 3-10 | 5-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | ADR File, Decision Log, Rationale | Direction, Current metric, Target metric, Experiment note, Learning report | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | AgileIterationCadence | ArchitectureRationaleDocumentationGovernance | OutcomesDiscoveryLearningIterationCoaching | ExecutionCadenceLearningGovernance |