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:WSJFRequest for CommentsRAID LogLASR (Lightweight Approach for Software Reviews)
Criterion
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
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
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
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.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
HighMediumLowMedium
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-103-20 Reviewer1-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAID 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
LeanEconomicsSequencePrioritization
ArchitectureDecisionAsyncGovernance
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
Add more methods