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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.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.
Complexitydifferent
LowLowHighHigh
Timedifferent
45-90 min30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope1-6 Wochen
Participantsdifferent
3-102-8Evaluation team, architects, and relevant stakeholders4-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsFishbone Diagram, Cause Categories, Investigation BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
AutonomyRolesTeam
Root causeQualityOperations
ArchitectureQualityRiskTradeoffsStakeholders
QualityProblem solvingRoot cause
Add more methods