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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.
Complexitydifferent
MediumMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend1-3 Tage20-40 min initial, dann laufend
Participantsdifferent
3-10 (Scrum Team)1-43-15
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalArchitecture Views, Cross-view Notes, RationaleROAM Board, Owner List
Tagsno overlap
AgileIterationCadence
DocumentationStakeholdersArchitecture
RiskAgileTrackingAlignment
Add more methods

Often compared together

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

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping