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 8D Problem Solving.
Operations
8D Problem Solving
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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 h1-6 WochenSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-103-84-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsFault Tree, Critical Paths, Cause Hypotheses, Control Actions8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanPrioritized 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
QualityProblem solvingRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods