CAPM Practice: Determine how project methodologies influence business analysis processes

BDD's Given/When/Then format expresses requirements in business language that both business stakeholders and developers understand, and which can be executed as automated tests. BAs typically write or facilitate creation of BDD scenarios, bridging business requirements and technical implementation.

**Why not B:** Monitoring and managing team behavior is a management or HR function, not behavior-driven development. BDD is a collaborative requirements and testing practice that uses structured scenarios to define expected system behavior, not a methodology for observing team conduct.

**Why not C:** BDD does not replace BA requirements with automated scripts. Instead, it transforms BA-defined acceptance criteria into a format that serves as both documentation and executable tests. The BA's requirements work remains central; BDD simply expresses it in a testable Given/When/Then format.

**Why not D:** BDD is not a development approach where developers define their own requirements. It is a collaborative practice where BAs, developers, and testers work together to define acceptance criteria. The business perspective drives the scenarios, ensuring requirements reflect stakeholder needs rather than developer assumptions.