View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Agile Start Stop Continue | ![]() Operations Learning Review | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 30-60 min | 1-3 h | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations | RetrospectiveTeamImprovement |



