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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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.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
LowLowHighLow
Timedifferent
30 min Setup, dann laufend15-30 min2-6 h30-60 min
Participantsdifferent
1-3 maintaining, briefing for everyone33-103-7
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceClarified Story, Test Examples, Open QuestionsFMEA Table, Risk Priority, Mitigation ActionsExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
RiskTrackingStakeholdersGovernance
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskQualityOperationsRoot cause
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods