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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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
HighMediumLow
Timedifferent
45-90 min1-3 h1-2 h
Participantsdifferent
3-103-123-10
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsKnowledge Map, Critical Knowledge Areas, Transfer PlanArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
LeanEconomicsSequencePrioritization
KnowledgeMappingRisk
CanvasArchitectureAlignmentWorkshop
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas