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 Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.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.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
90-180 min2-6 hHalf daySeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-153-10Team-Leads plus ArchitectureEvaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Spotify Model Map, Action ListFMEA Table, Risk Priority, Mitigation ActionsInteraction Heat Map, Agreements per PairPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
RiskQualityOperationsRoot cause
TeamAlignmentCollaborationOrganization
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods