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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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 of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.
Complexitydifferent
HighMediumMediumLow
Timedifferent
45-90 min2–4 h review as a planning range; preparation and evaluation additional3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
3-10Designers, developers as users, and facilitation1 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLean 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 checksRisk Matrix, Top Risk List
Tagsno overlap
LeanEconomicsSequencePrioritization
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskAssessmentLean
RiskDecisionPrioritizationAssessment
Add more methods