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 Sailboat Retrospective |  Architecture arc42 |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-2 Tage | 45-90 min | 45–75 min |
Participantsdifferent | 4-12 | 1-4 | 4-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureDocumentationCommunication | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |