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 illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Bucket System.
Agile
Bucket System
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 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 large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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 Feature45-90 min30-90 min30-60 min
Participantsdifferent
3-63-123-123-7
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Example Table, Acceptance TestsExpectation Map, Alignment Notes, AgreementsBucketed Backlog, Relative Estimates, Split CandidatesExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
AlignmentStakeholdersTeam
EstimationBacklogRelative sizing
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods