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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
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.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.It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.
Complexitydifferent
HighMediumHighMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews1-4 Wochen je Sprint, laufendSeveral meetings plus preparation and analysis; total effort depends on scope90-180 min
Participantsdifferent
5-123-10 (Scrum Team)Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogProduct Backlog, Sprint Backlog, Increment, Sprint GoalPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPlanning Levels Map, Cadence Model, Planning Artifact Inventory
Tagsno overlap
ExecutionCadenceLearningGovernance
AgileIterationCadence
ArchitectureQualityRiskTradeoffsStakeholders
CadenceGovernanceExecution
Add more methods