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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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
Purposedifferent
When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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 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.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.
Complexitydifferent
LowHighHighLow
Timedifferent
30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h45–75 min
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders3-10Team members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFMEA Table, Risk Priority, Mitigation Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
RetrospectiveLearningReflectionTeam
Add more methods