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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowHighMediumLow
Timedifferent
15-45 min45-90 min1-3 h1-2 Tage
Participantsdifferent
1-33-104-101-4
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleRanked Backlog, Cost-of-Delay AssumptionsCurrent-state map, Future-state map, Bottleneck listArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
LeanEconomicsSequencePrioritization
LeanFlowWasteDelivery
ArchitectureDocumentationCommunication
Add more methods