liveBook · Manning

Scenario review

As explained in Effective Behavior-Driven Development

A collaborative examination of behavior scenarios to identify ambiguity, omissions, or errors and establish agreement before implementation.

A scenario can be easy to read and still describe the wrong behavior. Scenario review gives the people who will build a feature and the people who understand the business a chance to check it together. They ask whether each scenario matches the expected behavior, uses familiar business terms, and expresses the understanding reached when the examples were discovered. section 9.14 section 4.1

A restriction that needs agreement

Consider customers who place pay-on-collection orders but never collect them. A proposed change would mark those customers as restricted and stop offering them pay-on-collection. After a small group turns the discovered examples into scenarios, reviewers need to check that the scenarios express the behavior the product owner expects. That check belongs before the team relies on the scenarios for automation or production code. section 9.0 section 9.14

Make the review a real part of the work:

  • Review scenarios soon after they are written, and review changed scenarios when stakeholder agreement needs checking. section 9.14 section 4.1
  • Ask the product owner to confirm that the scenarios reflect their expectations. Involve the delivery team, especially when entering a new functional area. section 9.14
  • If a subset of the team writes the scenarios, give everyone else time to read them and offer constructive feedback. Do not let asynchronous review become a checkbox. section 9.2.2

Ideally, the product owner and delivery team accept a story’s scenarios before work begins. Where formal approval is required, plan it so the team is not left waiting. Automated or AI-assisted checks may spot language, structure, or consistency problems before human review, but they cannot replace people applying domain knowledge to the final specification. section 9.2.2 section 4.2.2

How Effective Behavior-Driven Development covers it

How deep it goes
Specifies review timing, participants, acceptance, and asynchronous feedback, but provides no formal review checklist.
Examples
Uses uncollected pay-on-collection orders and proposed customer restrictions as the requirement whose scenarios need review.
What it assumes
Assumes examples have been discovered and formulated as business-readable scenarios; establishes shared language with the team when it is new.
What you can do after
Practice/perform scenario review by seeking product-owner and team agreement on behavior and terminology before implementation.
How it connects
Links example mapping and scenario formulation to shared business terminology, product-owner approval, and implementation.

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.