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 Responsibility Poker |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |
|---|---|---|---|
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. |
Complexitydifferent | Low | High | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Async |
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 |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
