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
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
Three Amigos method illustration showing its working structure
Agile
Three Amigos
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 Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
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.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.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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests.
Complexitydifferent
LowLowMediumMedium
Timedifferent
30-60 min15-30 min3–4 h for initial assessment; preparation and deeper analysis additional60-90 min pro Feature
Participantsdifferent
3-731 or a small team; particularly suitable for 3–4 people3-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsClarified Story, Test Examples, 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 checksExample Table, Acceptance Tests
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
CollaborationBehavior-Driven DevelopmentQualityRefinement
ArchitectureQualityRiskAssessmentLean
AgileRequirementsExamplesBehavior-Driven Development
Add more methods