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 Scrum |  Agile Specification by Example |  Facilitation Alignment Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 1-2 h | 60–90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |