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
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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
MediumLowHighLow
Timedifferent
60-90 min pro Feature20-40 min initial, dann laufend1-6 Wochen30-60 min
Participantsdifferent
3-63-154-103-7
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Table, Acceptance TestsROAM Board, Owner List8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
RiskAgileTrackingAlignment
QualityProblem solvingRoot cause
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods