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 for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-90 minOngoing1-2 Tage15-45 min
Participantsdifferent
2-82-121-41-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesKanban board, WIP policies, Flow metricsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
ConstraintsDecisionPlanningOptions
FlowVisual managementDelivery
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods