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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for DACI
Decision Making
DACI
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 RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
HighMediumLowLow
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung1-2 h30-60 min
Participantsdifferent
3-103-20 Reviewer3-102-10
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Canvas, Goals, Constraints, Quality AttributesDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
LeanEconomicsSequencePrioritization
ArchitectureDecisionAsyncGovernance
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernanceAlignment
Add more methods