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 Example Mapping |  Agile Sprint Retrospective |  Agile 4Ls Retrospective |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | Scrum Team | Team members involved | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam | AgileRequirementsRefinementBehavior-Driven Development |