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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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
Purposedifferent
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.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.
Complexitydifferent
HighLowMediumLow
Timedifferent
45-90 min1-2 h1-3 Wochen vom Draft bis zur Entscheidung1-2 h
Participantsdifferent
3-103-83-20 Reviewer3-10
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsInception Canvas, Risks, Goal List, Open QuestionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
LeanEconomicsSequencePrioritization
AlignmentArchitectureCanvas
ArchitectureDecisionAsyncGovernance
CanvasArchitectureAlignmentWorkshop
Add more methods