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:Example MappingLASR (Lightweight Approach for Software Reviews)Fishbone DiagramAcceptance Criteria Workshop
Criterion
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
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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
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.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 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.When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-60 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min20-40 min pro Story
Participantsdifferent
3-71 or a small team; particularly suitable for 3–4 people2-83-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsLean 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 checksFishbone Diagram, Cause Categories, Investigation BacklogAcceptance Criteria, Story Update
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ArchitectureQualityRiskAssessmentLean
Root causeQualityOperations
AgileRequirementsRefinementBehavior-Driven Development
Add more methods