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 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)
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
HighHighLowMedium
Timedifferent
2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope45–75 min1-3 h
Participantsdifferent
3-10Evaluation team, architects, and relevant stakeholdersTeam members involved3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
FMEA 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 investigations4Ls Board, Learning Themes, Improvement ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
RetrospectiveLearningReflectionTeam
LearningRetrospectiveIncidentOperations
Add more methods