The method helps clarify backlog work, sprint work, and team flow concretely. It sorts work by value, risk, and deliverability. The result is captured as an example map, acceptance criteria, and open questions.
Example Mapping
Turns backlog work, sprint work, and team flow into a tangible result by noting the story, collecting rules, and checking scope.
Which concrete examples show this story is complete, and what rule connects them?
The team follows the steps: note the story, collect rules, assign concrete examples, mark open questions, and check scope. Each step is captured visibly. At the end, an example map, acceptance criteria, and open questions are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Note the story
- 2Collect rules
- 3Assign concrete examples
- 4Mark open questions
- 5Check scope
The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- BDD discovery
- Backlog refinement
- Complex stories
Not good for
- Strategic portfolio work
- Very large roadmaps
Deep dive
Example Mapping follows a clear working logic: note the story, collect rules, assign concrete examples, mark open questions, and check scope. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. The result is an example map, acceptance criteria, and open questions that make decisions, learning, or further planning actionable.
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30-60 min with 3-7 people and use the format in a facilitated workshop. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Example Mapping Working TemplateCompact working template for Example Mapping with context, input, output artifacts, and next step.checklist
example-mapping-working-template.md
Compact working template for Example Mapping with context, input, output artifacts, and next step.
Example Mapping Checklist
- Goal and context clarified
- Input material gathered
- Participants and roles named
- Execution prepared according to the runsheet
- Output artifacts created
- Example Map updated
- Acceptance Criteria updated
- Open Questions updated
- Open questions documented
- Next step set with owner and date
When to choose differently
Short decision aid for existing alternatives.
Statt Example Mapping, wenn ihr Produkt, Entwicklung und Test früh an derselben Story ausrichten wollt.
Similar methods
All methodsMoves 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".
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".
Turns backlog, sprint work, and team flow into a tangible result by bringing a story, checking business intent, and agreeing on next steps.
Statt Example Mapping, wenn ihr Produkt, Entwicklung und Test früh an derselben Story ausrichten wollt.
Turns backlog, sprint work, and team flow into a tangible result by identifying oversized stories, finding the smallest value slice, and reprioritizing.
Turns backlog, sprint work, and team flow into a tangible result by setting the timeframe, collecting liked and learned items, and selecting actions.
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".