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 |  Delivery RAID Log |  Agile ROAM Board |  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. | 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 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 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 | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 30-60 min |
Participantsdifferent | Team members involved | 1-3 maintaining, briefing for everyone | 3-15 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | RAID Log, Status Report Source | ROAM Board, Owner List | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | RetrospectiveImprovementTeamReflection |