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
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
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.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.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 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
LowLowHighLow
Timedifferent
15-30 min30 min Setup, dann laufend2-6 h20-40 min pro Story
Participantsdifferent
31-3 maintaining, briefing for everyone3-103-6
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Clarified Story, Test Examples, Open QuestionsRAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation ActionsAcceptance Criteria, Story Update
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
AgileRequirementsRefinementBehavior-Driven Development
Add more methods