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 |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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 | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-10 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Process Map, Handoff List, Improvement Backlog | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AgileIterationCadence | ProcessOperationsImprovement | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |