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 Scrum |  Business Strategy Strategy Execution Loop |  Operations Gemba Walk |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | Initial 3-6 h, then monthly or quarterly reviews | 30-120 min | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 5-12 | 2-6 | 2-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Execution Loop, Review Cadence, Strategic Learning Log | Observation Notes, Improvement Ideas | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | AgileIterationCadence | ExecutionCadenceLearningGovernance | LeanObservationProcessOperations | LeanProblem solvingCoachingOperations |