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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.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.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
LowHighHighHigh
Timedifferent
30 min Setup, dann laufendInitial 3-6 h, then monthly or quarterly reviews2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone5-123-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceExecution Loop, Review Cadence, Strategic Learning LogFMEA Table, Risk Priority, Mitigation ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskTrackingStakeholdersGovernance
ExecutionCadenceLearningGovernance
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods