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 Example Mapping |  Agile 4Ls Retrospective |  Agile Specification by Example |
|---|---|---|---|---|
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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30-60 min | 45–75 min | 60-90 min pro Feature |
Participantsdifferent | 5-12 | 3-7 | Team members involved | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Example Map, Acceptance Criteria, Open Questions | 4Ls Board, Learning Themes, Improvement Actions | Example Table, Acceptance Tests |
Tagsno overlap | ExecutionCadenceLearningGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RetrospectiveLearningReflectionTeam | AgileRequirementsExamplesBehavior-Driven Development |