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 |  Product Strategy DIBB |  Facilitation Stakeholder Salience Model |  Facilitation Alignment 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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-2 h | 60-90 min | 1-2 h |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | DIBB document, Belief list, Bet list, Learning report | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AgileIterationCadence | StrategyDecisionAssumptionsHypothesis | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |