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 |  Decision Making Constraint Analysis |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-90 min | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | AgileIterationCadence | ConstraintsDecisionPlanningOptions | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |