View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Responsibility PokerATAM (Architecture Tradeoff Analysis Method)RAID LogStakeholder Salience Model
| Criterion |  Facilitation Responsibility Poker |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Low | High | Low | Medium |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |