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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Purposedifferent
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.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.
Complexitydifferent
MediumHighLowHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-90 min1-2 h90-180 min
Participantsdifferent
3-20 Reviewer3-103-83-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRanked Backlog, Cost-of-Delay AssumptionsInception Canvas, Risks, Goal List, Open QuestionsCoD Table, Prioritization Sequence
Tagsno overlap
ArchitectureDecisionAsyncGovernance
LeanEconomicsSequencePrioritization
AlignmentArchitectureCanvas
PrioritizationDeliveryEconomicsDecision
Add more methods