View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Pre-Mortem | ![]() Decision Making Constraint Analysis | ![]() Agile Example Mapping | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20–45 min | 30-90 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | Small cross-functional group | 2-8 | 3-7 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | RiskDecisionFailurePlanning | ConstraintsDecisionPlanningOptions | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |



