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 Scrum with its method-specific working model.
Agile
Scrum
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-4 Wochen je Sprint, laufend20-40 min initial, dann laufend1-2 Tage1-2 h
Participantsdifferent
3-10 (Scrum Team)3-151-43-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalROAM Board, Owner ListArchitecture Document, Context View, Runtime View, Deployment ViewInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
AgileIterationCadence
RiskAgileTrackingAlignment
ArchitectureDocumentationCommunication
AlignmentArchitectureCanvas
Add more methods