View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Specification by Example |  Agile Scrum |  Product Discovery Product Kata |
|---|---|---|---|---|
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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | 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 | High | Medium | Medium | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | 1-2 Wochen je Loop |
Participantsdifferent | 5-12 | 3-6 | 3-10 (Scrum Team) | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Direction, Current metric, Target metric, Experiment note, Learning report |
Tagsno overlap | ExecutionCadenceLearningGovernance | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | OutcomesDiscoveryLearningIterationCoaching |