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 for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.
Complexitydifferent
LowHighHighHigh
Timedifferent
45-90 min2-6 h2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-103-83-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsFault Tree, Critical Paths, Cause Hypotheses, Control ActionsFMEA Table, Risk Priority, Mitigation ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
AutonomyRolesTeam
RiskRoot causeSafety
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods