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 4Ls Retrospective | ![]() Agile ROAM Board | ![]() Facilitation Expectation Mapping | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 20-40 min initial, dann laufend | 45-90 min | 30-60 min |
Participantsdifferent | Team members involved | 3-15 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | ROAM Board, Owner List | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RiskAgileTrackingAlignment | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection |



