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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
LowMediumMediumLow
Timedifferent
20-40 min initial, dann laufend1-3 Wochen vom Draft bis zur Entscheidung3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
3-153-20 Reviewer1 or a small team; particularly suitable for 3–4 people2-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
RiskAgileTrackingAlignment
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskAssessmentLean
DecisionRolesGovernanceAlignment
Add more methods