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 Sprint Retrospective |  Agile Specification by Example |  Agile 4Ls Retrospective |
|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 60-90 min pro Feature | 45–75 min |
Participantsdifferent | Scrum Team | 3-6 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Example Table, Acceptance Tests | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementLearning | AgileRequirementsExamplesBehavior-Driven Development | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
