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 Starfish Retrospective |  Architecture Views and Beyond |  Agile Start Stop Continue |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 Tage | 30-60 min | 45-90 min |
Participantsdifferent | 4-12 | 1-4 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Architecture Views, Cross-view Notes, Rationale | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | DocumentationStakeholdersArchitecture | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |