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 4Ls Retrospective |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 45–75 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | Team members involved | 3-6 | 3-7 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
