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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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
MediumMediumLowHigh
Timedifferent
Ongoing60-120 min60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-202-84-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
CollaborationEngineeringIncident
Theory of ConstraintsAssumptionsSystems thinking
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods