Chapter 2: Structured Conversation
This chapter introduces its plan to show how a software product team uses structured conversations in requirements workshops to discover a feature’s expected behavior.
After this chapter you will be able to
- Purpose of requirements workshops. Explain how a requirements workshop explores a user story’s scope and uses concrete examples to make it unambiguous, while allowing new details and unanswered questions to emerge.
- Collaborative challenge of understanding. Explain why attendees bring diverse perspectives and actively test their understanding of a user story with examples, rather than treating BDD as a tool or a Given/When/Then form to fill in.
- Pickup as the rule boundary. Explain how questioning the order-state wording leads the team to revise when an address change is allowed.
- Counterexamples and open questions. Describe how a case after pickup complicates the rule and how the team handles a question it cannot settle immediately.
- Deliberate and accidental discovery. Distinguish deliberate discovery in a requirements workshop from discoveries made after development has started, and explain why the timing matters.
- Examples exposing requirement gaps. Trace how concrete examples exposed gaps in the delivery-address rule, leading the team to refine the rule and identify further questions and behavior.
- Example Map Cards and Layout. Describe what the four card colors represent and how the cards are arranged to show a story, its rules, supporting examples, and blocking questions.
- Flexible Rules and Examples Discovery. Explain how a team can work from prepared rules to illustrative examples, or from examples to rules when a story is vague, without requiring a fixed order.
- Workshop Preparation and Facilitation. Describe how the product owner prepares for the workshop and why another team member facilitates it.
- Structured conversation definition. Explain what makes a requirements-workshop discussion a structured conversation and why structuring it is useful.
- Workshop participation and outcomes. Describe the properties of a structured requirements conversation, including who participates, how the workshop maintains momentum, and what counts as success.
- Active two-way collaboration. Distinguish active team collaboration from a meeting where the product owner explains requirements and everyone else listens.
- Conditions for wider participation. Explain how preparation and varied ways of taking part can help people contribute, rather than assuming they should simply ask more questions.
- Diverse perspectives in requirements workshops. Explain why business, development, and testing representatives discuss requirements together, what each perspective contributes, and why a Three Amigos meeting need not have exactly three people.
- Short workshop rationale. Explain why requirements workshops should generally last no more than 40 minutes, and how to structure a meeting that must run longer.
- Progressive workshop focus. Explain how a workshop can stay focused while its understanding develops: start with a known topic, capture learning continuously in a form everyone can read, and record unanswerable questions instead of discussing them fruitlessly.
- Criteria for reaching consensus. Explain how the group can tell it has reached consensus: everyone agrees with what the output says, agrees whether the feature is sufficiently understood, has captured the conversation’s knowledge, and has assigned responsibility for remaining questions.
- Concrete examples in discussion. Explain when and why a facilitator should ask for examples during an Example Mapping workshop.
- Questions that deepen discussion. Describe how a facilitator can use questions about examples to move past a superficial sense that everything is clear.
- Happy path before exceptions. Describe the order in which the facilitator should guide discussion of the overall process and exceptional cases.
What it builds on
- Discovery (chapter 1) · Discovery as a part of the BDD approach.
Section by section
Introduction
This chapter introduces its plan to show how a software product team uses structured conversations in requirements workshops to discover a feature’s expected behavior.
2.1 Where is my pizza?
Introduces a pizza delivery application and the customer feature that will serve as context for later sections.
2.2 A useful meeting
This section explains how a short, collaborative requirements workshop uses concrete examples to clarify a user story and why that work is more than filling in a BDD template.
- Purpose of requirements workshops: Explain how a requirements workshop explores a user story’s scope and uses concrete examples to make it unambiguous, while allowing new details and unanswered questions to emerge.
Why it matters: Examples help the team find gaps before it treats a story as ready to implement. - Collaborative challenge of understanding: Explain why attendees bring diverse perspectives and actively test their understanding of a user story with examples, rather than treating BDD as a tool or a Given/When/Then form to fill in.
Why it matters: Different perspectives and questions make it less likely that the team will mistake an assumption for an agreed requirement. - Focused sessions and Example Mapping: Describe the workshop format presented here and why the authors recommend Example Mapping to facilitate it, without claiming that this section teaches the mapping procedure.
Why it matters: A focused, adaptable meeting format gives the team a practical setting for clarifying stories together.
Key terms: requirements workshop, user story, concrete examples, scope, BDD, diverse perspectives, Given/When/Then, Example Mapping, requirements workshops, short, focused sessions
2.3 Collecting examples
A pizza-delivery workshop shows how concrete examples reveal a clearer address-change rule, unresolved questions, and an important edge case.
- Concrete examples for rules: Describe how the team uses a persona and a specific address-change situation to illustrate a rule, then checks the captured steps together.
Why it matters: A specific case makes it easier for the team to spot missing or ambiguous details. - Pickup as the rule boundary: Explain how questioning the order-state wording leads the team to revise when an address change is allowed.
Why it matters: The revised boundary says more precisely which address changes the team intends to allow. - Counterexamples and open questions: Describe how a case after pickup complicates the rule and how the team handles a question it cannot settle immediately.
Why it matters: Recording the difficult case lets the workshop move forward without pretending it has been solved. - State changes during an edit: Explain why the team adds an example in which pickup happens while a customer is entering a new address.
Why it matters: This edge case prevents the team from assuming that an order remains eligible throughout an edit.
Key terms: rule, example, persona, state diagram, picked up, rule card, example card, counterexample, red card, temporary workaround
2.4 Deliberate discovery
The section explains how discussing concrete examples in a requirements workshop brings important discoveries forward, before they disrupt development.
- Deliberate and accidental discovery: Distinguish deliberate discovery in a requirements workshop from discoveries made after development has started, and explain why the timing matters.
Why it matters: Finding gaps in understanding before implementation gives the team a chance to address them before they disrupt delivery. - Examples exposing requirement gaps: Trace how concrete examples exposed gaps in the delivery-address rule, leading the team to refine the rule and identify further questions and behavior.
Why it matters: A seemingly simple requirement can hide disagreements and edge cases that become visible when the team discusses examples.
Key terms: accidental discovery, deliberate discovery, requirements workshop, concrete examples, rule, state diagram, question card
2.5 Example Mapping in a nutshell
This section explains how Example Mapping uses a visible arrangement of stories, rules, examples, and questions to guide short requirements conversations.
- Example Map Cards and Layout: Describe what the four card colors represent and how the cards are arranged to show a story, its rules, supporting examples, and blocking questions.
Why it matters: The visible map helps everyone follow the requirements discussion and return to it after an interruption. - Flexible Rules and Examples Discovery: Explain how a team can work from prepared rules to illustrative examples, or from examples to rules when a story is vague, without requiring a fixed order.
Why it matters: The conversation can uncover requirements whether the initial story is well prepared or still vague. - Workshop Preparation and Facilitation: Describe how the product owner prepares for the workshop and why another team member facilitates it.
Why it matters: Separating these jobs leaves the product owner free to respond to the team’s discoveries while the workshop stays on track. - Useful Example Card Wording: Explain why example cards should capture important details and have referable titles without being written as Given/When/Then scenarios.
Why it matters: Cards remain useful in conversation without turning discovery into a wording exercise. - Recording Assumptions and Retaining Maps: Describe how to keep constraints and assumptions distinct on a map and how teams can preserve and share the completed map.
Why it matters: Important qualifications and workshop findings remain visible and available after the conversation ends. - AI Assistance With Human Review: Describe ways AI can assist the product owner and facilitator while stating who remains responsible for reviewing its output.
Why it matters: Assistance can reduce administrative work without handing responsibility for requirements to the tool.
Key terms: Example Mapping, user stories, rules, examples, questions, acceptance criteria, Product Owner (PO), candidate rules, facilitator, requirements workshop
2.6 How to establish structured conversations
Defines structured conversation for requirements workshops and identifies the properties that make those workshops focused and effective.
- Structured conversation definition: Explain what makes a requirements-workshop discussion a structured conversation and why structuring it is useful.
Why it matters: The structure gives a workshop a way to stay focused without requiring one particular technique. - Workshop participation and outcomes: Describe the properties of a structured requirements conversation, including who participates, how the workshop maintains momentum, and what counts as success.
Why it matters: These properties keep the right perspectives engaged and turn discussion into agreed examples.
Key terms: structured conversation, requirements workshop, facilitated exchange, collaborative, diverse perspectives, short, progressive focus, consensus, agreed concrete examples
2.6.1 Collaborative
Structured conversations work when the whole team exchanges ideas and the discussion is arranged so different people can participate.
- Active two-way collaboration: Distinguish active team collaboration from a meeting where the product owner explains requirements and everyone else listens.
Why it matters: A meeting can include everyone without giving everyone a part in discovering the requirements. - Conditions for wider participation: Explain how preparation and varied ways of taking part can help people contribute, rather than assuming they should simply ask more questions.
Why it matters: Making participation easier can surface important questions that would otherwise come up only after the meeting.
Key terms: collaboration, bi-directional communication, product owner, root causes, handout, colored cards
2.6.2 Diverse perspectives
The section explains how diverse human perspectives uncover requirement ambiguities early and how AI can add perspectives without replacing the team’s understanding.
- Diverse perspectives in requirements workshops: Explain why business, development, and testing representatives discuss requirements together, what each perspective contributes, and why a Three Amigos meeting need not have exactly three people.
Why it matters: Different viewpoints expose ambiguities before the team builds on conflicting assumptions. - AI perspectives with human oversight: Describe how focused AI agents can contribute to a discovery workshop, and explain why the team must not let AI control the meeting or accept its examples blindly.
Why it matters: AI suggestions can reveal gaps, but discussing and evaluating them is how the team learns what the requirement means.
Key terms: Three Amigos meetings, business goals, technical implications, corner cases, AI agents, example mapping, discovery workshop, ambiguous examples
2.6.3 Short
This section recommends short requirements workshops and explains why frequent, recurring sessions can work better than long meetings.
- Short workshop rationale: Explain why requirements workshops should generally last no more than 40 minutes, and how to structure a meeting that must run longer.
Why it matters: Shorter sessions make better use of participants’ attention and time. - Benefits of frequent meetings: Describe how recurring, frequent workshops reduce disruption, broaden shared ownership, and let discussions resume after unanswered questions are resolved.
Why it matters: A regular cadence makes it easier to involve more people and pick up questions later.
Key terms: requirements workshops, short, focused sessions, recurring meetings, frequent meetings, shared ownership, unanswerable questions
2.6.4 Progressive focus
This section explains how a workshop stays focused as participants build and record their understanding.
- Progressive workshop focus: Explain how a workshop can stay focused while its understanding develops: start with a known topic, capture learning continuously in a form everyone can read, and record unanswerable questions instead of discussing them fruitlessly.
Why it matters: A shared record helps the group see its progress without losing time on unresolved questions.
Key terms: progressive focus, example map, unanswerable questions
2.6.5 Consensus
This subsection defines when a structured conversation has reached consensus.
- Criteria for reaching consensus: Explain how the group can tell it has reached consensus: everyone agrees with what the output says, agrees whether the feature is sufficiently understood, has captured the conversation’s knowledge, and has assigned responsibility for remaining questions.
Why it matters: These checks help the group decide whether it can proceed without losing important information or leaving questions unowned.
Key terms: consensus, output, hidden/private knowledge, remaining question
2.6.6 Facilitation tips
This section gives facilitators four ways to keep Example Mapping discussions concrete, probing, orderly, and manageable for participants.
- Concrete examples in discussion: Explain when and why a facilitator should ask for examples during an Example Mapping workshop.
Why it matters: Asking for examples keeps the conversation grounded in the behavior the team is discussing. - Questions that deepen discussion: Describe how a facilitator can use questions about examples to move past a superficial sense that everything is clear.
Why it matters: A few probing questions can uncover distinctions that a quick agreement would miss. - Happy path before exceptions: Describe the order in which the facilitator should guide discussion of the overall process and exceptional cases.
Why it matters: Starting with the overall process gives the conversation a natural order before it branches into exceptions. - Pauses for silent writing: Explain when a facilitator might pause the conversation for silent writing and what that pause gives participants.
Why it matters: A short pause lets participants write and gather their thoughts without competing with the conversation.
Key terms: Example Mapping, examples, concrete data, positive/negative examples, outcomes, happy path, rule, corner cases, exceptional cases, special conditions
2.7 Summary
Where this is used later
- Is all that concrete essential? (chapter 3) · Assumes the requirements-workshop setting for collaborative discussion.
- (chapter intro) (chapter 3) · Introduces examples as cases that illustrate behavior.
- How hard is concrete? (chapter 3) · The collection of examples during structured conversations.
- Rules vs. examples (chapter 3) · Provides a rule and illustrating example whose distinction matters.
- Do we need more examples? (chapter 3) · Illustrates why considering another case can expose a gap in a rule.
- Illustrative scenarios (chapter 7) · The idea of deliberate discovery.
- Why not formulate during the discovery session? (chapter 9) · The later distinction between discovery and formulation builds on not drafting scenarios during the workshop.
- BDD in distributed teams (chapter 4) · Online maps provide a way for distributed teams to retain and share the discussion.
Concepts explained in this chapter
- exampleA concrete instance illustrating an expected behavior or a possible outcome of a rule.
- Example MappingExample Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
- business ruleA business constraint governing payment when a customer collects an order.
- example mapAn example map is a visual arrangement of examples and their associated rules for examining how a system should behave in different situations.
- discovery workshopA collaborative session for exploring and refining software requirements through structured conversation.
- collaborationCollaboration is a cooperative working relationship in which relevant participants jointly discover, formulate, and refine software behavior.
- structured conversationA structured conversation is a deliberately organized discussion that guides participants through clarifying expected software behavior.
- behavior-driven developmentAn activity that applies behavior-driven development principles during software development.
- concrete dataConcrete values representing the entities, states, or inputs involved in a scenario rather than abstract placeholders or general description.
- shared understandingA common interpretation of requirements and expected behavior held by the members of a team.
- requirementsA requirement is a statement of a stakeholder need, constraint, or expected system behavior that guides solution development.
- user storyA user story is a concise requirement description expressing desired software behavior from a user's perspective.
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.
