Example Mapping
Example Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
Effective Behavior-Driven Development
Example Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
- How it is used
- Structures short requirements workshops around a user story so participants can discover expected behavior together before coding or testing.
- How deep it goes
- Defines the four card types and gives facilitation prompts, while leaving implementation scenarios as a subsequent step.
- Examples
- Uses a delivery-address change story and checks involving address distance and order status.
- What you can do after
- Practice/perform a workshop that maps rules to examples, records blocking questions, and makes scope decisions more explicit.
Read how Effective Behavior-Driven Development explains Example Mapping →
Collaborative Software Design: How to facilitate domain modeling decisions
Example Mapping is a collaborative technique for organizing rules, examples, and questions to clarify requirements and discover acceptance criteria.
- How it is used
- Clarifies user stories and use cases by discovering acceptance criteria and constraints through structured example-based discussion.
- How deep it goes
- Explains a visual facilitation sequence from user story through rules and examples, without descending into implementation details.
- Examples
- Uses seat reservation outcomes, sticky notes, Miro boards, physical index cards, and group sessions shaped by cognitive bias.
- What you can do after
- Apply it via Miro or physical index cards to expose scenarios, constraints, and acceptance criteria collaboratively.
BDD in Action, Second Edition
Example Mapping is a collaborative BDD technique for exploring rules, examples, and questions about a requirement.
- How it is used
- Uses short collaborative sessions to discover and organize business rules, examples, counterexamples, and questions before implementation.
- How deep it goes
- Explores requirements breadth-first and superficially, deferring detailed examples and Given–When–Then formulation to a later phase.
- Examples
- Uses train-trip scheduling and frequent-flyer points to illustrate rules, examples, counterexamples, and acceptance criteria.
- What you can do after
- Apply it to rapidly enumerate rules and decide whether a User Story is understood enough to begin work or needs further discovery.
Read how BDD in Action, Second Edition explains Example Mapping →
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Example Mapping is a collaborative technique for exploring rules, examples, and questions in greater detail around a behavior or requirement.
- How it is used
- Uses collaborative mapping to uncover scenarios and edge cases around a behavior or requirement.
- How deep it goes
- Explains a focused workflow from event selection through scenario generation and concept splitting.
- Examples
- Uses order cancellation, warehouse departure, refunds, Order Canceled, and Cancelation Denied as concrete scenarios.
- What you can do after
- Apply it in a collaborative workshop to expose hidden scenarios and decide when concepts need separation.
What to know first
- scenarioA scenario is a specified or described situation, sequence of events, or set of conditions used to represent or examine behavior, processes, or possible outcomes.
- user storyA user story is a concise requirement describing a desired software capability or outcome from the perspective of a user or stakeholder.
- assumptionAn assumption is a proposition or condition provisionally accepted as true or applicable as a basis for reasoning, planning, modeling, or action.
- behavior-driven developmentBehavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
Related concepts
- business ruleuses · A business rule is a domain-specific constraint, policy, or decision criterion that governs valid data, behavior, decisions, or processes.
- user storyuses · A user story is a concise requirement describing a desired software capability or outcome from the perspective of a user or stakeholder.
- acceptance criteriaproduces · Acceptance criteria are verifiable conditions that a requirement, feature, or deliverable must satisfy to be considered acceptable or complete.
- discovery workshopused by · A discovery workshop is a collaborative, structured session for exploring and refining user needs, business problems, domain concepts, or software requirements.
- exampleproduces · An example is a concrete instance that illustrates expected behavior, a possible outcome, or an input-output relationship.
Questions about Example Mapping
What is Example Mapping?
Example Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
Which Manning books explain Example Mapping?
Effective Behavior-Driven Development, Collaborative Software Design: How to facilitate domain modeling decisions, BDD in Action, Second Edition and Architecture Modernization: Socio-technical alignment of software, strategy, and structure.
What should I know before learning Example Mapping?
Manning books that teach Example Mapping usually introduce scenario, user story, assumption and behavior-driven development first.
What is Example Mapping a kind of?
Example Mapping is a kind of breadth-first approach. A breadth-first approach examines a wide range of areas before narrowing attention to particular goals or solutions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.



