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 Sailboat 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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Process Map, Handoff List, Improvement Backlog | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | AgileIterationCadence | ProcessOperationsImprovement | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
