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 Example Mapping |  Facilitation Stakeholder Salience Model |  Agile Specification by Example |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 60-90 min | 60-90 min pro Feature | 60–90 min |
Participantsdifferent | 3-7 | 3-6 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Salience Diagram, Strategy per Class | Example Table, Acceptance Tests | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | StakeholdersFacilitationAlignmentGovernance | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersAlignmentFacilitationChange |