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 Shape Up with its method-specific working model.
Delivery
Shape Up
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.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.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-Down1-2 h1-2 Tage15-45 min
Participantsdifferent
2-4 pro Pitch3-101-41-3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
PlanningDeliveryAutonomy
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods