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 |  Agile Three Amigos |  Agile Specification by Example |  Operations 8D 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-30 min | 60-90 min pro Feature | 1-6 Wochen |
Participantsdifferent | 3-10 (Scrum Team) | 3 | 3-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | AgileIterationCadence | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | QualityProblem solvingRoot cause |