While working at the strategy level, the team needs to ensure stakeholders actively support an environment for constructive communication…

Behavior Driven Development (BDD) is a collaborative approach that unites technical and non-technical stakeholders. It uses a shared, natural language format (like Gherkin's Given/When/Then syntax) to create a common understanding of desired system behaviors before development begins. This process inherently fosters an environment of constructive communication and collaboration. By defining acceptance criteria in this clear, unambiguous way, teams can continuously validate that the solution meets the strategic intent, thereby supporting continuous improvement.

A. Product Roadmap: A Product Roadmap is a high-level, strategic artifact that communicates the product vision and direction; it does not, by itself, create a collaborative working environment.

B. Reviews: Reviews (e.g., retrospectives, sprint reviews) are specific, time-boxed events for feedback and inspection. While they support collaboration, they are activities within a process, not the overarching approach to create the environment itself.

D. Release Plans: A Release Plan is a tactical document that outlines the timeline and scope for upcoming releases. Its primary focus is on scheduling and delivery, not on fostering a collaborative culture.

1. International Institute of Business Analysis (IIBA). (2017). Agile Extension to the BABOK® Guide (Version 2).

Section 7.4

Behavior Driven Development (BDD): This section describes BDD as a technique that "helps to ensure all stakeholders have a shared understanding of the desired behavior of the system before implementation begins... It is a collaborative approach that defines the acceptance criteria for a user story." (p. 82). This directly supports BDD as the correct answer for fostering collaboration and shared understanding.

Section 7.16

Product Roadmap: This section defines a roadmap as a tool to "describe how a product is likely to grow" and to "communicate the product direction." Its purpose is communication of a plan

not the creation of a collaborative environment. (p. 106).

Section 7.18

Reviews: This section explains that reviews are used to "evaluate a work product." While collaborative

they are distinct events

unlike the continuous collaborative nature of BDD. (p. 110).

Chapter 4

The Delivery Horizon: This chapter discusses release planning as a tactical activity focused on what will be delivered in the near term

distinguishing it from the strategic and cultural aspects addressed by BDD. (pp. 29-35).