View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Stakeholder Mapping |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | Medium | Low |
Timedifferent | 60–90 min | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 2-8 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Stakeholder Map, Engagement Plan, Risk Notes | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | StakeholdersAlignmentFacilitationChange | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
