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
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)
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowLowHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional15-30 min30-60 min2-6 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people33-73-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Lean 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 checksClarified Story, Test Examples, Open QuestionsExample Map, Acceptance Criteria, Open QuestionsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
CollaborationBehavior-Driven DevelopmentQualityRefinement
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskQualityOperationsRoot cause
Add more methods