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 Scrum with its method-specific working model.
Agile
Scrum
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.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.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
HighMediumLowHigh
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews1-4 Wochen je Sprint, laufend30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-123-10 (Scrum Team)1-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogProduct Backlog, Sprint Backlog, Increment, Sprint GoalRAID Log, Status Report SourcePrioritized 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
AgileIterationCadence
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods