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 |  Agile Starfish Retrospective |  Facilitation Team Charter |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | 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 team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 2-4 h | 45-90 min |
Participantsdifferent | 4-12 | 4-12 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | TeamAlignmentCollaboration | AlignmentStakeholdersTeam |