methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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.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.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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitydifferent
HighLowLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope45-90 min60–90 min45-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-102-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsResponsibility Map, Role Agreements, Open QuestionsStakeholder Map, Engagement Plan, Risk NotesExpectation Map, Alignment Notes, Agreements
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
RolesResponsibilityTeamFacilitation
StakeholdersAlignmentFacilitationChange
AlignmentStakeholdersTeam
Add more methods