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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.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
HighLowLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope30-60 min30-60 min45–75 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-122-8Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsStart Stop Continue Board, Improvement ActionsFishbone Diagram, Cause Categories, Investigation Backlog4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
RetrospectiveImprovementTeamReflection
Root causeQualityOperations
RetrospectiveLearningReflectionTeam
Add more methods