Purpose
Helps clarify backlog, sprint work, and team flow in concrete terms. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.
Agile
Acceptance Criteria Workshop
Moves backlog, sprint work, and team flow toward a concrete result through "pin the story summary to the whiteboard", "write the happy path as Given-When-Then", and "copy the criteria into the story tool".
Which concrete, testable criteria describe the happy path, edge cases, and negative paths of this story so clearly that all three roles share the same Definition of Done?
LowWorkshop20-40 min pro Story
How it works
The team follows the steps "pin the story summary to the whiteboard", "write the happy path as Given-When-Then", "add edge cases as additional scenarios", "add negative paths", "read the criteria aloud and walk through them", and "copy the criteria into the story tool". Each step is made visible. At the end, Acceptance Criteria and a Story Update are available so decisions, tests, or actions can continue directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Pin the story summary to the whiteboard
- 2Write the happy path as Given-When-Then
- 3Add edge cases as additional scenarios
- 4Add negative paths
- 5Read the criteria aloud and walk through them
- 6Copy the criteria into the story tool
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Refinement
- Story handoff
- Cross-functional teams
Not good for
- Very simple, clear stories
Deep dive
In detail
The Acceptance Criteria Workshop is a focused follow-up format to Example Mapping and Specification by Example. For each story, the moderator guides rounds that produce concrete, testable criteria, often in Given-When-Then format. The result bridges discovery and implementation and reduces follow-up questions.
Facilitation
Write the criteria where everyone can see them. Keep each round focused on one story. Do not accept vague criteria such as fast or simple.
Output artifacts
Acceptance CriteriaStory-Update
Artifact templates
Acceptance Criteria Workshop Working TemplateCompact working template for Acceptance Criteria Workshop with context, input, output artifacts, and next step.checklist
Acceptance Criteria Workshop Working TemplateCompact working template for Acceptance Criteria Workshop with context, input, output artifacts, and next step.
checklistacceptance-criteria-workshop-working-template.md
Compact working template for Acceptance Criteria Workshop with context, input, output artifacts, and next step.
Acceptance Criteria Workshop Checklist
- Goal and context clarified
- Input material gathered
- Participants and roles named
- Execution prepared according to the runsheet
- Output artifacts created
- Acceptance Criteria updated
- Story updated
- Open questions documented
- Next step set with owner and date
When to choose differently
Short decision aid for existing alternatives.
Example Mapping
Statt Acceptance Criteria Workshop, wenn Regeln, Beispiele und offene Fragen gemeinsam sortiert werden sollen, bevor Kriterien formuliert werden.
Similar methods
All methodsAgile
Specification by Example
Moves backlog, sprint work, and team flow toward a concrete result through "briefly present the story or feature", "collect examples rule by rule", and "hand over the examples as acceptance tests".
Agile
Example Mapping
Turns backlog work, sprint work, and team flow into a tangible result by noting the story, collecting rules, and checking scope.
Statt Acceptance Criteria Workshop, wenn Regeln, Beispiele und offene Fragen gemeinsam sortiert werden sollen, bevor Kriterien formuliert werden.
Agile
Three Amigos
Turns backlog, sprint work, and team flow into a tangible result by bringing a story, checking business intent, and agreeing on next steps.
Agile
Story Splitting
Turns backlog, sprint work, and team flow into a tangible result by identifying oversized stories, finding the smallest value slice, and reprioritizing.
Agile
Ideal Days
Moves backlog, sprint work, and team flow toward a concrete result through "explain the ideal day unit", "calibrate with a reference item", and "do not confuse it with calendar days".
Agile
Planning Poker
Turns backlog, sprint work, and team flow into a tangible result by presenting the item, clarifying questions, and discussing deviations before estimating again.