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 Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|
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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitysame | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Scrum Team | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementLearning | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
