How Example Mapping strengthens our software projects
What is Example Mapping?
Example Mapping is an agile way to make user stories clear and tangible.
A user story (or “user narrative”) is a requirement for software, formulated in everyday language. It is told from an end user's perspective to explain what a user wants to do and why. Typically, these stories follow the format:
As a [role], I want [action], therefore [benefit].
The complex requirements of a user story can be broken down into clearly structured components using the Example Mapping method:
- rules, which represent the acceptance criteria of the stories.
- concrete examples for the rules.
- open questions, which result from the Example Mapping process.
This creates transparency, promotes a common language within the team and ensures that all participants develop the same understanding of the desired behavior of a function.
Why we work with Example Mapping at Cap3
Project managers, developers, UX/UI designers and testers meet in our interdisciplinary teams. To achieve a common goal from many perspectives, structure is needed. Example Mapping provides exactly this structure and creates a common understanding between all departments — and thus the basis for precise and efficient implementation.
The rules and examples developed in Example Mapping are then incorporated into specific Gherkin scenarios. These serve as comprehensible, clearly formulated preliminary work for developers and at the same time make manual testing easier. Thanks to the uniform, easy-to-read Gherkin notation, testers can understand the use cases and carry out structured tests based on the same scenarios. This creates a consistent connection between technical description, technical implementation and quality assurance.
The most important benefits for us are:
- Common understanding: Requirements are explained using specific examples — understandable for all parties involved.
- Early clarification: Ambiguities or contradictions become visible before they cost time.
- Efficient communication: Discussions remain targeted and based on facts.
- Higher quality: Well-thought-out examples lead to more precise development and more meaningful tests.
How does an Example Mapping work?
- The User Story is written as briefly as possible on a card and placed at the top of the board on which the Example Mapping is carried out. It is a good idea to always work with the same color scheme for the maps.
- In the second step, known acceptance criteria are defined as rules, each on their own card, and placed on a line below the user story card.
- For each rule, examples which illustrate the rules are arranged below them.
- If questions come up while working out rules and examples that cannot be clarified immediately, they will be recorded on another card for a later date.
- It is typical of the Example Mapping process that further, previously undiscovered user stories arise in the course of the process. These are recorded separately for subsequent Example Mapping rounds.
It is recommended that you allow around 25 minutes to process a user story and, if necessary, work with a timer. At the end of the process, it is decided whether the story has now been worked out in detail enough and sufficiently understood by all parties involved to be implemented.
Typical hurdles that arise in the Example Mapping process can be that the user story is too big or there are too many unknowns. In this case, the user story should be split into several smaller user stories and open questions should be clarified.
The following Example Mapping was created as an example of an app for renting beach chairs.
Conclusion: Agile clarity that works
Example Mapping has established itself as an integral part of our agile software development at Cap3. The method strengthens communication, promotes common understanding and ensures that we can implement our projects in a structured, efficient and high-quality manner.
Sources:
https://scrumguide.de/user-story/
.png)
