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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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
HighLowLowLow
Timedifferent
45-90 min15-45 min30-120 min1-2 Tage
Participantsdifferent
3-101-32-61-4
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsADR File, Decision Log, RationaleObservation Notes, Improvement IdeasArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
LeanEconomicsSequencePrioritization
ArchitectureRationaleDocumentationGovernance
LeanObservationProcessOperations
ArchitectureDocumentationCommunication
Add more methods