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 |  Agile Specification by Example |  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. | 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. | 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 | Medium | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | ExecutionCadenceLearningGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
