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 Scrum |  Operations Process Mapping |  Operations Learning Review |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 1-3 h | 20-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-10 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Process Map, Handoff List, Improvement Backlog | Learning Review Notes, System Factors, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | AgileIterationCadence | ProcessOperationsImprovement | LearningRetrospectiveIncidentOperations | LearningOperationsImprovement |