View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Lean Coffee |  Agile Example Mapping |  Facilitation Responsibility Poker |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | When a group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | Low | Low | Low | Low |
Timedifferent | 30-90 min | 30-60 min | 45-90 min | 20-40 min pro Story |
Participantsdifferent | 3-20 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized Topics, Discussion Notes, Action Items | Example Map, Acceptance Criteria, Open Questions | Responsibility Map, Role Agreements, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | FacilitationAutonomyDialogue | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RolesResponsibilityTeamFacilitation | AgileRequirementsRefinementBehavior-Driven Development |