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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.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.When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h15-45 min60-90 min pro Feature1-2 Tage
Participantsdifferent
2-81-33-61-4
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Issue Map, Positions, Argument NotesADR File, Decision Log, RationaleExample Table, Acceptance TestsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
RationaleKnowledgeDecision
ArchitectureRationaleDocumentationGovernance
AgileRequirementsExamplesBehavior-Driven Development
ArchitectureDocumentationCommunication
Add more methods