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 for Communication Plan
Delivery
Communication Plan
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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.
Complexitydifferent
HighLowLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope45-90 minHalf day initial, dann laufend45-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-6Ein Team plus Stakeholder3-12
Formatdifferent
Workshop + asyncWorkshop + 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 Plan, Channel Matrix, Message CadenceTeam API DocumentExpectation Map, Alignment Notes, Agreements
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
CommunicationStakeholdersDeliveryPlanning
TeamAlignmentCommunicationService
AlignmentStakeholdersTeam
Add more methods