Chapter 5: How to get the business involved
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
- Business and delivery collaboration. Explain why BDD collaboration must include business representatives as well as technical delivery staff.
- Contextual proof of value. Explain how the introduction proposes gaining business engagement: show the value of real collaboration, while adapting the approach to the project context.
- Evidence and peer experience. Explain why the section recommends talking to people who have worked on successful BDD projects rather than treating BDD's claimed benefits as scientifically proven.
- Business collaboration in BDD. Explain why developer-only or tester-only BDD can improve testing but does not deliver the main benefits of BDD, and why BDD tools alone do not make an approach BDD.
- Path toward business involvement. Describe how a team without business participation can treat its current practice as temporary and use business-readable examples and regular contact to work toward collaboration.
- Problem-first business engagement. Explain why a conversation with business colleagues about BDD should start with pain points or opportunities in the current process, rather than with Example Mapping, formulation, automation, or the BDD process itself. Describe how identifying those challenges provides a reason to try a different approach.
- Product owner workload tradeoff. Explain how early collaboration in BDD can reduce a product owner’s overall workload, contrasting it with work they do in a classic agile approach.
- BDD prevention of production issues. Explain how BDD can contribute when production issues are common, and identify the benefit the section says is easiest to measure.
- Evidence based root cause analysis. Describe how AI-assisted root cause analysis can inform a response to production incidents and what safeguard it needs when evidence is insufficient.
- Scenarios as deliverable work units. Distinguish technical-task slicing from a functional breakdown by rules and scenarios, and explain how completing release-related tasks for each scenario helps keep the application releasable.
- User value through BDD examples. Explain why a good-quality product may still fail to engage users, and how BDD can help align it with their viewpoint.
- Rule Based Scope Flexibility. Describe how Example Mapping can flag a story for splitting and how its rules let a product owner defer lower-priority behavior to deliver as much value as possible by the deadline.
- Scenario Based Progress Visibility. Explain how passing, failing, and not-yet-automated scenarios show stakeholders which behaviors the application supports, and why this is more useful than an arbitrary percentage of work completed.
- Automated scenarios as safety net. Explain how BDD's requirement-linked automated tests and scenarios help a team respond to unwanted side-effects of changes.
- Low-Cost, Quality-Preserving Change. Explain why responding to market changes requires a development model that keeps the cost of new features low without sacrificing application quality, and how this relates to unwanted side-effects.
- Specification-Level Scenario Experiments. Describe how product owners and business analysts can experiment at the specification level by speculatively writing and running new scenarios to investigate system behavior.
- Bug versus feature debates. Explain how developers writing application code and testers writing test cases independently can create “bug vs. feature” debates, and how working together on requirement details reduces those conflicts.
- Review feedback and recurring changes. Explain why stakeholders need to see a feature in action to give real feedback, while distinguishing useful review feedback from a pattern of changes that may signal insufficient discovery of detailed requirements.
- BDD support for requirement clarity. Describe how focusing on examples and writing scenarios in business-readable terminology help clarify detailed requirements before review.
- Accessible and findable scenarios. Explain why a product owner who does not read scenarios may face a publishing or findability problem, and describe how to make the living documentation easier to access and search.
What it builds on
- Collaborative (chapter 2) · Earlier discussion of collaborative structured conversations.
- BDD is a bridge (chapter 1) · The role of BDD in connecting business needs and software delivery.
- Collecting examples (chapter 2) · The use of examples to clarify requirements.
- BDD in agentic software development (chapter 4) · The context of AI use in software development.
- The BDD approach (chapter 4) · The earlier description of the BDD approach provides a contrast to explaining BDD through a business problem.
- Testing (chapter 1) · The earlier discussion of the relationship between BDD and testing.
- Aligning tasks to scenarios (chapter 4) · The use of scenarios to align and organize work in Scrum.
- Example Mapping in a nutshell (chapter 2) · The introduction to Example Mapping as a way to identify rules and examples.
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.
- Business and delivery collaboration: Explain why BDD collaboration must include business representatives as well as technical delivery staff.
Why it matters: Business involvement is part of the collaboration this chapter considers essential to BDD. - Contextual proof of value: Explain how the introduction proposes gaining business engagement: show the value of real collaboration, while adapting the approach to the project context.
Why it matters: The business has a stronger reason to participate when collaboration proves useful on its own project.
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.
- Evidence and peer experience: Explain why the section recommends talking to people who have worked on successful BDD projects rather than treating BDD's claimed benefits as scientifically proven.
Why it matters: Firsthand project experience can inform your judgment without turning a claim into a proven result. - Commonly claimed BDD benefits: State the kinds of benefits typically attributed to BDD in this section, without presenting them as proven outcomes.
Why it matters: These are the specific claims the section asks you to evaluate through others' experience.
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.
- Business collaboration in BDD: Explain why developer-only or tester-only BDD can improve testing but does not deliver the main benefits of BDD, and why BDD tools alone do not make an approach BDD.
Why it matters: It helps distinguish business collaboration from merely using BDD-style automation. - Path toward business involvement: Describe how a team without business participation can treat its current practice as temporary and use business-readable examples and regular contact to work toward collaboration.
Why it matters: It gives a team a practical starting point without treating the absence of business participation as the desired end state. - Limits of an AI proxy: Explain what temporary help AI can provide with team-only scenarios and why its suggestions still need human validation.
Why it matters: It keeps a useful aid from being mistaken for the business’s actual judgment.
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.
- Problem-first business engagement: Explain why a conversation with business colleagues about BDD should start with pain points or opportunities in the current process, rather than with Example Mapping, formulation, automation, or the BDD process itself. Describe how identifying those challenges provides a reason to try a different approach.
Why it matters: Starting with a problem gives business colleagues a reason to consider BDD, rather than asking them to adopt a process for its own sake.
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.
- Product owner workload tradeoff: Explain how early collaboration in BDD can reduce a product owner’s overall workload, contrasting it with work they do in a classic agile approach.
Why it matters: The case for involving a busy product owner depends on the work that collaboration can replace or prevent.
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.
- Cost of production issues: Explain why a production issue is more damaging than catching the same issue during preparation.
Why it matters: These costs make frequent production issues worth addressing promptly. - BDD prevention of production issues: Explain how BDD can contribute when production issues are common, and identify the benefit the section says is easiest to measure.
Why it matters: It gives the team a concrete reason to involve the business in BDD: preventing misunderstandings before they become production bugs. - Evidence based root cause analysis: Describe how AI-assisted root cause analysis can inform a response to production incidents and what safeguard it needs when evidence is insufficient.
Why it matters: Sound evidence helps a team decide whether specification problems warrant BDD and whether its changes are helping.
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.
- Implementation versus release readiness: Explain why a feature that can be demonstrated may still not be releasable, using the section’s examples of work often left until the end.
Why it matters: Recognizing the unfinished release work helps the team avoid treating a demo as proof that users can receive the feature. - Continuous delivery cycles: Describe how short, complete work cycles and automation support reliable release on short notice.
Why it matters: A short cycle only supports release on demand if it includes the work needed to make the result deliverable. - Scenarios as deliverable work units: Distinguish technical-task slicing from a functional breakdown by rules and scenarios, and explain how completing release-related tasks for each scenario helps keep the application releasable.
Why it matters: Scenario-sized work creates meaningful opportunities to test and deliver before an entire story is finished.
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.
- User value through BDD examples: Explain why a good-quality product may still fail to engage users, and how BDD can help align it with their viewpoint.
Why it matters: Building the product well is not enough if it does not serve the people who will use it.
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.
- Fixed Scope Deadline Risk: Explain why a deadline based on an estimate is hard to meet when the required scope is fixed, and why overtime or extra staff are not reliable long-term fixes.
Why it matters: It explains why pushing the team harder is a poor substitute for making choices about scope. - Rule Based Scope Flexibility: Describe how Example Mapping can flag a story for splitting and how its rules let a product owner defer lower-priority behavior to deliver as much value as possible by the deadline.
Why it matters: Breaking work down by behavior gives the product owner options when the deadline cannot move.
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.
- Scenario Based Progress Visibility: Explain how passing, failing, and not-yet-automated scenarios show stakeholders which behaviors the application supports, and why this is more useful than an arbitrary percentage of work completed.
Why it matters: Stakeholders can see what the application actually supports, not just a reported percentage. - Poor Visibility Consequences: Explain why lacking a good overview of progress makes corrective action harder and can damage trust between the business and delivery team.
Why it matters: Early visibility gives the team a chance to respond before a deadline is missed and trust suffers.
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.
- Growing cost of side-effects: Explain why bugs introduced alongside new features or fixes can become more costly as a codebase grows.
Why it matters: This is the problem the section says automated scenarios help address. - Automated scenarios as safety net: Explain how BDD's requirement-linked automated tests and scenarios help a team respond to unwanted side-effects of changes.
Why it matters: Requirement-linked scenarios give the team feedback that makes changing code less daunting.
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.
- Low-Cost, Quality-Preserving Change: Explain why responding to market changes requires a development model that keeps the cost of new features low without sacrificing application quality, and how this relates to unwanted side-effects.
Why it matters: Speed of response is useful only if new features remain affordable and the application stays reliable. - Specification-Level Scenario Experiments: Describe how product owners and business analysts can experiment at the specification level by speculatively writing and running new scenarios to investigate system behavior.
Why it matters: Business participants can explore possible behavior through scenarios rather than relying only on code changes to experiment.
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.
- Bug versus feature debates: Explain how developers writing application code and testers writing test cases independently can create “bug vs. feature” debates, and how working together on requirement details reduces those conflicts.
Why it matters: Agreeing on requirement details early can spare the team rework and frustration later.
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.
- Review feedback and recurring changes: Explain why stakeholders need to see a feature in action to give real feedback, while distinguishing useful review feedback from a pattern of changes that may signal insufficient discovery of detailed requirements.
Why it matters: Reviews are valuable, but repeated surprises at them can point to a costly gap in earlier requirements work. - BDD support for requirement clarity: Describe how focusing on examples and writing scenarios in business-readable terminology help clarify detailed requirements before review.
Why it matters: Clarifying examples and readable scenarios can reduce avoidable surprises when stakeholders see the finished feature.
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.
- Accessible and findable scenarios: Explain why a product owner who does not read scenarios may face a publishing or findability problem, and describe how to make the living documentation easier to access and search.
Why it matters: Making scenarios accessible and findable gives the product owner a practical way to use them. - Learning to use living documentation: Explain why making living documentation available may not immediately lead the business to use it, and describe how the team should respond.
Why it matters: An accessible document becomes valuable only when people learn how to use it for their questions.
Key terms: scenarios, living documentation, continuous integration pipeline, tags, retrospect
5.4 Summary
Where this is used later
- Navigation (chapter 10) · Develops navigation of living documentation.
Concepts explained in this chapter
- developer-only BDDDeveloper-only BDD is a BDD practice in which developers create and apply behavior specifications without business participation.
- behavior-driven developmentAn activity that applies behavior-driven development principles during software development.
- collaborationCollaboration is a cooperative working relationship in which relevant participants jointly discover, formulate, and refine software behavior.
- discovery workshopA collaborative session for exploring and refining software requirements through structured conversation.
- scenarioA business-readable description of an example system behavior and its expected outcome.
- automated testingThe execution of software tests by programmed tools or scripts rather than manually.
- shared understandingA common interpretation of requirements and expected behavior held by the members of a team.
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.
