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 Sprint Retrospective |  Business Strategy Strategy Execution Loop |  Delivery RAID Log |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. | 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | Initial 3-6 h, then monthly or quarterly reviews | 30 min Setup, dann laufend | 20-45 min |
Participantsdifferent | Scrum Team | 5-12 | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Execution Loop, Review Cadence, Strategic Learning Log | RAID Log, Status Report Source | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveImprovementLearning | ExecutionCadenceLearningGovernance | RiskTrackingStakeholdersGovernance | LearningOperationsImprovement |