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)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
HighMediumLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope60-120 min30-60 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanEmotion Board, Themes, Action Items
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationStakeholdersCanvas
RetrospectiveTeamReflection
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue