liveBook · Manning

Chapter 9: A new user story

What you will learn in chapter 9 of Effective Behavior-Driven Development

The chapter introduces a pay-on-collection requirement that the team will use as it formulates examples into scenarios.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduces a pay-on-collection requirement that the team will use as it formulates examples into scenarios.

Key terms: pay-on-collection, restricted customers

9.1 Write it upwards

The section introduces “write it upwards”: formulate a scenario from its outcome backward so each part has a clear causal connection and unnecessary context can be removed.

Key terms: write it upwards, outcome, context statements, causal connection

9.2 Too many cooks

This section illustrates why collaboratively wording a discovered example can be difficult, then raises questions about who should formulate it.

Key terms: formulating, concrete examples, discovery, expected outcome

9.2.1 Why not formulate during the discovery session?

This section explains why discovery and formulation should be separate practices.

Key terms: discovery, concrete examples, shared understanding, formulation

9.2.2 Shouldn’t the whole team formulate together?

This section explains why a subset of the team can formulate scenarios, provided the whole team reviews and owns them.

Key terms: formulation, shared language, ubiquitous language, collective ownership, asynchronous reviewing, constructive feedback, reviewed and accepted, product owner, delivery team

9.2.3 Don’t the product owners (POs)/business analysts (BAs) own the specifications?

The section explains how PO/BA review of scenarios written by the delivery team confirms shared understanding while leaving specification responsibility with the PO/BA.

Key terms: PO/BA, delivery team, scenarios, concrete examples, business terminology, shared understanding

9.2.4 Shouldn’t the developers/testers focus on the implementation?

This subsection explains why developers and testers should help write scenarios rather than focus only on implementation.

Key terms: business context, business requirements, business terminology, scenarios

9.2.5 Isn’t it more efficient for one person to do it?

Formulation benefits from a pair with complementary perspectives, followed by detailed review of the scenarios by other disciplines.

Key terms: formulation, business perspective, technical perspective, scenarios, other disciplines

9.2.6 Should the same people always do the formulation?

The section explains why formulation should be shared across the team and how choosing formulators and reviewing their work supports learning.

Key terms: formulation, shared ownership, specification, constructive feedback

9.3 Quotation marks

The section explains why quotation marks in scenarios offer little automation benefit when they make the text harder to read.

Key terms: quotation marks, readability, scenario, step definition snippets, scenario automation tools

9.4 There’s no “I” in “Persona”

This section explains how to name actors unambiguously in scenarios, when to use a role instead of a persona, and how step wording conveys sequence and expected outcomes.

Key terms: first person “I”, third person, role, persona, role description, customer, Given, When, Then, past tense

9.5 Does repetition matter?

This section explains how to choose between repeated names and pronouns in scenarios while preserving readability, clarity, and the integrity of an approved specification.

Key terms: they, repetition, pronoun, readability, business-readable, Gherkin, automation framework, linguistic shortcuts, formulated scenario, reviewed and approved

9.6 Moving shared context into a background

This section explains how Gherkin Backgrounds share scenario context and why removing repetition can make scenarios harder to read and maintain.

Key terms: Background, shared context, feature, rule, DRY, DAMP, readability, maintenance

9.7 Unformulated examples

The section explains why examples collected during discovery may be combined or left out of the formulated specification without losing their value.

Key terms: concrete examples, example mapping, formulation, scenario, specification, unformulated examples, programmer tests, scenarios

9.8 Commenting in feature files

Explains how Gherkin comments and text descriptions work, when to use each, and why feature files should rarely need either.

Key terms: line comment, block comments, #, textual descriptions, block keyword, Gherkin keyword, tag, comments, text descriptions, feature files

9.9 Setting the context

This section shows how to keep scenarios brief and clear by leaving ordinary context implicit, stating exceptional context, and comparing alternative wordings when the team disagrees.

Key terms: implicit context, Given steps, restricted customer, BRIEF principles, write it upwards, essential context

9.10 Stay focused on illustrating the rule

This section shows how to formulate a concise blocklist scenario that illustrates the customer-restriction rule without also specifying unresolved email and phone matching rules.

Key terms: rule, scenario, restricted, blocklist, matching rules, question cards, requirement workshop, exact, character-for-character matching, scenario outline, example map

9.11 Formulation gets faster

The section shows how consistent, readable phrasing makes later scenarios quicker to formulate, while warning against sacrificing clarity for step reuse.

Key terms: formulating, ubiquitous language, steps, step reusability, readability, consistency, action-like steps, Restrictions are independent of authentication status, restricted customer, contact details

9.12 Incremental specification

The section explains how high-level scenarios can guide functionality delivered in small increments, and why similarly small steps help control risks when using AI to generate code.

Key terms: small increments, low fidelity, high fidelity, high level scenario, implementation details, rules and scenarios, automation code, context window, small, controlled steps, scenarios

9.13 Documenting with a tag

This section explains how Gherkin tags document information outside a scenario’s expected behavior, using @manual to mark a scenario the team has chosen not to automate.

Key terms: Gherkin tag, feature file, step text, feature, rule, scenario, scenario outline, examples block, case sensitive, implicitly applied

9.14 Who does what and when

This section explains when formulated scenarios should be reviewed and who should review them before the team relies on them.

Key terms: scenarios, review, automation, production code, formulation, example mapping, business readable terminology, PO, product specification

9.15 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 8: Formulating a feature Chapter 10: Organizing the documentation →

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.