liveBook · Manning

Structured conversation

As explained in Effective Behavior-Driven Development

A structured conversation is a deliberately organized discussion that guides participants through clarifying expected software behavior.

A structured conversation is a facilitated exchange of ideas that follows a predefined form. In a requirements workshop, it helps a team discover expected user-story behavior and build shared understanding before coding or testing. section 2.6 section 2.7

Effective workshop conversations are:

  • Collaborative, with active participation from everyone. section 2.6
  • Informed by business, development, and test perspectives. section 2.6
  • Short and fast-moving, with progress captured as the discussion unfolds. section 2.6
  • Directed toward consensus, measured through agreed concrete examples. section 2.6

Example Mapping is one way to conduct a structured conversation: concrete examples illustrate each rule, helping the team develop unambiguous terminology. section 2.7

How Effective Behavior-Driven Development covers it

How deep it goes
Specifies five workshop properties: active participation, diverse perspectives, brevity, progressive focus, and consensus.
Examples
Uses concrete examples to illustrate rules and help establish unambiguous terminology.
What you can do after
Understand expected user-story behavior through agreed concrete examples before writing code or tests.
How it connects
Connects requirements workshops and user stories with Example Mapping as a way to structure discussion.

Also explained in

Compare how 4 books explain structured conversation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.