View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  Agile Specification by Example |  Operations Learning Review |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | 60-90 min pro Feature | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 3-6 | 3-10 | Scrum Team |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Example Table, Acceptance Tests | Learning Review Notes, System Factors, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | LearningOperationsImprovement | AgileRequirementsExamplesBehavior-Driven Development | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementLearning |