liveBook · Manning

Formulation

As explained in Effective Behavior-Driven Development

The behavior-driven development practice of expressing understood behavior as precise scenarios.

A team may agree that restricted customers should not be offered pay-on-collection, yet still leave a crucial question unanswered: what exactly should the system do? Formulation turns the concrete examples discussed during discovery into business-readable scenarios. Each scenario expresses expected behavior precisely enough to guide development and clearly enough for business and delivery people to review together. section 9.0 section 1.3.3

Discovery and formulation work at different speeds. In discovery, people capture examples quickly to uncover assumptions. Formulation is slower work with language: choose terms rooted in the domain, decide what each example needs to say, and make the result understandable to someone who missed the conversation. Combining the two can slow discovery and reduce participation. section 9.2.1 section 6.1

A practical path from examples to scenarios is:

  • Start with the story’s rules and concrete examples. Formulate before implementation begins, often as the first development task, and add the scenarios to source control. section 4.1 section 4.2.2
  • Work in a small group, often a tester and developer. When the team is establishing its language, formulating together can help; later, share the work across different pairs. section 4.1 section 9.2.6
  • Keep examples that add distinct value. Merge examples that differ only in incidental details, or leave an example unformulated if it helped discovery but would not strengthen the specification. section 9.7
  • Ask the product owner and delivery team to review the scenarios before work proceeds. Their feedback checks both the expected behavior and the business terminology. section 9.2.2 section 9.2.3

Choosing one useful scenario

Two examples of a restricted customer placing an order differed only in whether the customer was authenticated. The team judged that difference insignificant for the behavior at issue and combined the examples. Its scenario said: “Given a restricted customer / And they are authenticated / When they place an order for customer-collection / Then pay-on-collection should not be offered as a payment option.” The point is the unavailable payment option, not a separate scenario for every incidental variation. Review can still reveal that the wording needs changing. section 9.7

Scenarios commonly use Given, When and Then; Gherkin provides a format that can later connect them to automation. The format is not the goal. A scenario is valuable first because people can agree on what it means. Once automated, it can also help detect when the implementation and documented behavior diverge. Writing Gherkin alone does not establish that discovery, formulation, and review happened. section 1.3.3 section 6.6

How Effective Behavior-Driven Development covers it

How deep it goes
Explains a collaborative procedure for selecting, wording, and reviewing scenarios; defers detailed Gherkin syntax and automation.
Examples
Uses a restricted-customer payment scenario and the decision to merge examples differing only in authentication.
What it assumes
Builds on shared understanding from discovery rather than requiring prior knowledge of Gherkin or automation.
What you can do after
Practice/perform it by turning discovered examples into reviewed, business-readable scenarios before development begins.
How it connects
Connects discovery, user stories, ubiquitous language, Gherkin, automation, and living documentation.

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.