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 Specification by Example |  Decision Making Cynefin Workshop |  Agile Example Mapping |
|---|---|---|---|---|
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 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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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 | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 60-180 min | 30-60 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 4-20 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | ComplexitySensemakingDecision | Behavior-Driven DevelopmentRequirementsExamplesRefinement |