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 Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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
HighLowLowHigh
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews30 min Setup, dann laufend1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-121-3 maintaining, briefing for everyone3-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogRAID Log, Status Report SourceArchitecture Canvas, Goals, Constraints, Quality AttributesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ExecutionCadenceLearningGovernance
RiskTrackingStakeholdersGovernance
CanvasArchitectureAlignmentWorkshop
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods