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 Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Purposedifferent
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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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 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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
60-90 min pro Feature20-40 min initial, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
3-63-151 or a small team; particularly suitable for 3–4 people3-7
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Table, Acceptance TestsROAM Board, Owner ListLean 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 Map, Acceptance Criteria, Open Questions
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
RiskAgileTrackingAlignment
ArchitectureQualityRiskAssessmentLean
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods