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 a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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.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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.
Complexitysame
LowLowLowLow
Timedifferent
15-30 min30-60 min45-90 min20-40 min pro Story
Participantsdifferent
33-73-123-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Clarified Story, Test Examples, Open QuestionsExample Map, Acceptance Criteria, Open QuestionsExpectation Map, Alignment Notes, AgreementsAcceptance Criteria, Story Update
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
Behavior-Driven DevelopmentRequirementsExamplesRefinement
AlignmentStakeholdersTeam
AgileRequirementsRefinementBehavior-Driven Development
Add more methods