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
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 for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration of a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
Purposedifferent
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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional3–4 h for initial assessment; preparation and deeper analysis additional30-60 min15-30 min
Participantsdifferent
Designers, developers as users, and facilitation1 or a small team; particularly suitable for 3–4 people1-61-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized 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 checksPareto Chart, Top Causes, Focus ListEisenhower Matrix, Action List, Delegation Notes
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskAssessmentLean
PrioritizationQualityFocusRoot cause
PrioritizationFocusTasks
Add more methods