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 Expectation Mapping |  Delivery RAID Log |  Agile Specification by Example |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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 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 | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 60-90 min pro Feature | 60-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Example Table, Acceptance Tests | Salience Diagram, Strategy per Class |
Tagsno overlap | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersFacilitationAlignmentGovernance |