Example Mapping (BDD)
Clarify your user stories with rules and concrete examples.
Example Mapping is a Behavior-Driven Development (BDD) technique that helps clarify a user story by breaking it down into rules, examples, and questions. This game promotes team alignment and task prioritisation during refinement sessions. By structuring discussions around these elements, it helps avoid misunderstandings and surprises during development.
Walkthrough
- 1
Introduction
5 minThe facilitator briefly explains the concept of Example Mapping and its objective: to clarify user stories by identifying rules, examples, and questions. They emphasise the importance of this technique for improving communication and avoiding misunderstandings during development.
Tip — Use a concrete example from your project to illustrate the concept and capture participants' attention.
- 2
Presentation of User Stories
10 minThe facilitator asks the team to select one or more user stories to clarify. Each story is written on a yellow card. The facilitator invites participants to read and understand the chosen story, ensuring that everyone shares the same understanding.
Tip — Choose user stories that are complex enough to benefit from the exercise, but not too complex to overwhelm the team.
- 3
Identification of Rules
15 minParticipants collaboratively identify the business rules associated with the user story and note them on blue cards. The facilitator encourages discussions and clarifies the rules if necessary. The rules should be specific and verifiable.
Tip — Encourage the team to focus on one rule at a time to avoid losing track of the discussion.
- 4
Creation of Examples
20 minFor each identified rule, participants propose concrete examples and note them on green cards. These examples should illustrate how the rules apply in real situations. The facilitator ensures that each example is clear and relevant.
Tip — Use real scenarios or known use cases to help generate relevant examples.
- 5
Collection of Questions
10 minParticipants formulate questions about any grey areas or uncertainties regarding the user story and note them on red cards. The facilitator encourages the team to ask all necessary questions to clarify ambiguities.
Tip — Reassure the team that all questions are valid and contribute to improving the clarity and quality of the story.
- 6
Summary and Conclusion
10 minThe facilitator summarises the identified rules, examples, and questions. They discuss with the team the next steps to address outstanding questions and integrate the rules and examples into the user story documentation. The team decides on actions to take to clarify remaining points.
Tip — Take photos of the cards to integrate them into the team's project management tools.
Variants
- Use digital tools to conduct the exercise remotely by sharing virtual boards.
- Add a step for prioritising rules and examples to better manage complex user stories.
- Hold a follow-up session to address outstanding questions identified during the exercise.
Debrief guide
- What have we learned about the user story using Example Mapping?
- Which rules or examples were the most surprising or unexpected?
- How has this technique influenced our collective understanding of the story?
- What questions remain open and how can we address them?
- How can we integrate this technique into our regular refinement processes?
- What adjustments could we make for our next Example Mapping session?