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 for Delegation Poker.
Facilitation
Delegation Poker
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 of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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 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
LowLowLow
Timedifferent
45-90 min30-60 min20-40 min pro Story
Participantsdifferent
3-103-73-6
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsExample Map, Acceptance Criteria, Open QuestionsAcceptance Criteria, Story Update
Tagsno overlap
AutonomyRolesTeam
Behavior-Driven DevelopmentRequirementsExamplesRefinement
AgileRequirementsRefinementBehavior-Driven Development
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker