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 Specification by Example |  Facilitation Alignment Mapping |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 1-2 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-6 | 4-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Alignment Map, Open Issues, Decision Questions | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AlignmentStakeholdersStrategyFacilitation | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |