liveBook · Manning

Discovery workshop

As explained in Effective Behavior-Driven Development

A collaborative session for exploring and refining software requirements through structured conversation.

A delivery-address change sounds simple until the team asks when a change is still allowed. A discovery workshop brings the product owner, developers, and testers together to explore a user story before anyone writes code or tests. Its goal is shared understanding of the behavior to deliver, not merely agreement on the story’s wording. section 1.3.2 section 2.2

Keep the conversation short and focused:

  • Start with a user story and any candidate rules. Invite different perspectives so assumptions surface early. section 2.2
  • Give each rule concrete examples. Agree on unambiguous terms, and record questions the group cannot yet answer. section 2.2 section 2.7
  • Revise the story when the examples reveal a different scope or unexpected complexity. section 1.3.2

When can an address change?

If an order is being prepared, a customer’s new delivery address is accepted. If the order has already been collected, the request is rejected. Comparing these cases makes the rule clearer than the request “let customers change their address” alone. section 1.3.2

Example Mapping can keep rules, examples, and open questions visible while the team talks. Regular short workshops can prepare upcoming stories and give the product owner early feedback. Discovering disagreements together also reduces later rework and “bug versus feature” debates between developers and testers. section 2.7 section 4.2.1 section 5.3.9

How Effective Behavior-Driven Development covers it

How deep it goes
Explains workshop preparation, participants, rules, examples, and open questions; leaves questions unanswered when the group lacks the answer.
Examples
Contrasts accepted and rejected delivery-address changes and uses colored index cards to record workshop outputs.
What it assumes
Starts with a user story and candidate rules, then develops unambiguous terminology collaboratively rather than assuming it is settled.
What you can do after
Practice/perform short workshops that turn user-story rules into concrete examples and expose assumptions before implementation.
How it connects
Connects discovery workshops to BDD, user stories, structured conversations, Example Mapping, and backlog refinement.

Also explained in

Compare how 2 books explain discovery workshop →

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.