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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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
LowHighLowLow
Timedifferent
45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope45-90 min45–75 min
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders4-12Team members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSailboat Board, Risks, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
AlignmentStakeholdersTeam
ArchitectureQualityRiskTradeoffsStakeholders
RetrospectiveTeamImprovement
RetrospectiveLearningReflectionTeam
Add more methods