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.

Selected:Architecture Decision RecordFishbone DiagramRAID LogLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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)
Purposedifferent
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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-45 min30-60 min30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-32-81-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogRAID Log, Status Report SourceLean 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 checks
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
Add more methods