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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-45 min20-40 min initial, dann laufend30 min Setup, dann laufend1-3 Tage
Participantsdifferent
1-33-151-3 maintaining, briefing for everyone1-4
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleROAM Board, Owner ListRAID Log, Status Report SourceArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
DocumentationStakeholdersArchitecture
Add more methods