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 4Ls Retrospective |  Delivery RAID Log |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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-90 min | 45–75 min | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 3-12 | Team members involved | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | 4Ls Board, Learning Themes, Improvement Actions | RAID Log, Status Report Source | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | AlignmentStakeholdersTeam | RetrospectiveLearningReflectionTeam | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementTeamReflection |