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 ROAM Board | ![]() Agile Three Amigos | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 |
Timedifferent | 20-40 min initial, dann laufend | 15-30 min | 60-90 min |
Participantsdifferent | 3-15 | 3 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ROAM Board, Owner List | Clarified Story, Test Examples, Open Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskAgileTrackingAlignment | CollaborationBehavior-Driven DevelopmentQualityRefinement | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






