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 for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
MediumLowLowLow
Timedifferent
45-90 min20-40 min initial, dann laufend1-2 h30 min Setup, dann laufend
Participantsdifferent
3-83-153-101-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsROAM Board, Owner ListArchitecture Canvas, Goals, Constraints, Quality AttributesRAID Log, Status Report Source
Tagsno overlap
Systems thinkingFramingStakeholders
RiskAgileTrackingAlignment
CanvasArchitectureAlignmentWorkshop
RiskTrackingStakeholdersGovernance
Add more methods