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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.
Complexitydifferent
HighLowMediumLow
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews20-40 min initial, dann laufend1-4 Wochen je Sprint, laufend30 min Setup, dann laufend
Participantsdifferent
5-123-153-10 (Scrum Team)1-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogROAM Board, Owner ListProduct Backlog, Sprint Backlog, Increment, Sprint GoalRAID Log, Status Report Source
Tagsno overlap
ExecutionCadenceLearningGovernance
RiskAgileTrackingAlignment
AgileIterationCadence
RiskTrackingStakeholdersGovernance
Add more methods