View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Agile Specification by Example |  DevOps Game Day |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 45-90 min | 60-90 min pro Feature | Halber Tag | 30-60 min |
Participantsdifferent | 2-5 | 3-6 | 5-20 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Example Table, Acceptance Tests | Simulation Notes, Gaps List, Updated Runbooks | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | LeanProblem solvingCoachingOperations | AgileRequirementsExamplesBehavior-Driven Development | ResilienceOperationsIncident | Behavior-Driven DevelopmentRequirementsExamplesRefinement |