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 ROAM Board |  Agile 4Ls 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 | 30-60 min | 20-40 min initial, dann laufend | 45–75 min |
Participantsdifferent | 3-12 | 3-12 | 3-15 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions | ROAM Board, Owner List | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection | RiskAgileTrackingAlignment | RetrospectiveLearningReflectionTeam |