View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Agile Start Stop Continue |  Agile Sprint Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | Scrum Team | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam |