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 |  Facilitation Lean Coffee |  Operations After-Action Review |
|---|---|---|---|
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 a group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-90 min | 20-45 min |
Participantsdifferent | Scrum Team | 3-20 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Prioritized Topics, Discussion Notes, Action Items | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveImprovementLearning | FacilitationAutonomyDialogue | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
