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:Request for CommentsRAID LogFishbone DiagramLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 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.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.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.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
MediumLowLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30 min Setup, dann laufend30-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-20 Reviewer1-3 maintaining, briefing for everyone2-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncAsyncWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogLean 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
ArchitectureDecisionAsyncGovernance
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
ArchitectureQualityRiskAssessmentLean
Add more methods