liveBook · Manning

Chapter 5: How to get the business involved

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

This introduction explains why business participation matters to BDD and why teams must demonstrate the value of collaboration in their own context.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction explains why business participation matters to BDD and why teams must demonstrate the value of collaboration in their own context.

Key terms: collaboration, business, delivery team, business representatives, value of collaborating, project context

5.1 Learn from your peers

This section lists commonly claimed BDD benefits and recommends learning from successful projects because those claims lack rigorous scientific proof.

Key terms: rigorous scientific evidence, successful BDD project, case studies, cycle time, rework/rejections, production issues, implementation costs

5.2 The one where the business is not involved

The section explains why BDD without business participation falls short, how a team can use it as a temporary step toward collaboration, and where AI can offer limited help.

Key terms: developer-only BDD, tester-only BDD, business stakeholders, Given/When/Then, scenarios, business examples, business-readable phrases, concrete example, full collaboration, AI as a product owner proxy

5.3 BDD is for solving problems

This section argues that business colleagues are more likely to engage with BDD when it is presented as a response to their actual problems rather than as a process to adopt.

Key terms: BDD, pain points, opportunities, Example Mapping, formulation, automation

5.3.1 The product owner is overloaded

This section explains why BDD can reduce an overloaded product owner’s workload despite requiring their time for collaboration.

Key terms: product owner, requirement workshops, Example Mapping, scenarios, classic agile development approach

5.3.2 Production issues are common

The section explains why frequent production issues matter, how BDD can help prevent some of them, and how careful root cause analysis can guide improvement.

Key terms: production issues, preparation phase, BDD, requirement analysis, detailed specification, stakeholders, delivery team members, root cause analysis, lack of specification, unclear specification

5.3.3 It is hard to get the product to a deliverable state

This section explains why completing a feature is not the same as making it releasable, and how scenario-sized work can help a team keep the application deliverable.

Key terms: releasable state, smallish tasks, continuous delivery (CD), short cycles, automation, rules, examples/scenarios, functional breakdown, work unit

5.3.4 It is hard to get customers engaged with the product

This section explains how BDD can help a team build a product users value by focusing on realistic behavior and involving UX experts early.

Key terms: user value, technical stories, realistic examples of application behavior, UX experts

5.3.5 Deadlines are often missed

This section explains why fixed scope makes missed deadlines hard to recover from and how Example Mapping can help a product owner adjust scope.

Key terms: estimate, scope, deadline, Example Mapping, rules, stories, product owner

5.3.6 Hard to get a good overview of the progress

This subsection explains why BDD scenario status gives stakeholders a more useful view of delivery progress than an arbitrary percentage completed.

Key terms: BDD approach, scenarios, passing, failing, not yet automated, transparent view of progress, overview of progress, early warning, corrective action, loss of trust

5.3.7 Introduction of new features causing unwanted side-effects

This section explains how requirement-linked automated scenarios help teams detect unwanted side-effects of changes and keep new features from becoming increasingly costly to deliver.

Key terms: unwanted side-effects, implementation cost, BDD, automated test coverage, automated scenarios, requirements, safety net

5.3.8 Not being able to react fast enough to market changes

The section connects rapid responses to market changes with low-cost, quality-preserving feature development and experimentation through scenarios.

Key terms: development model, unwanted side-effects, specification level, specification language, scenarios

5.3.9 “Bug vs. feature” debates within the team

The section explains why separate interpretations of requirements lead to “bug vs. feature” debates and how collaborative requirements workshops reduce them.

Key terms: bug vs. feature, shared understanding, collaborative requirements workshops

5.3.10 Changes regularly requested at the Sprint/feature reviews

This section explains why Sprint reviews provide valuable feedback, what recurring change requests may indicate, and how BDD can reduce avoidable misunderstandings.

Key terms: small increments, Sprint/feature reviews, detailed requirements, BDD, examples, ambiguities, scenarios, business-readable terminology

5.3.11 But my product owner never reads the scenarios

The section explains how to respond when a product owner helps create scenarios but does not use the living documentation.

Key terms: scenarios, living documentation, continuous integration pipeline, tags, retrospect

5.4 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 4: Who does what and when Chapter 6: What is formulation? →

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.