CAPM Practice: Determine how project methodologies influence business analysis processes

In agile, BAs (or product owners with BA support) define acceptance criteria as part of story specification — before development begins. These testable conditions define what 'done' means for each story, bridging requirements and testing.

**Why not B:** Acceptance criteria are a standard practice in agile projects regardless of whether external clients or contracts are involved. Internal teams use acceptance criteria to ensure shared understanding of what "done" means for each user story, enabling consistent quality and reducing ambiguity during development and testing.

**Why not C:** While QA testers may contribute to refining acceptance criteria, they are not the sole authors. BAs collaborate with product owners and stakeholders to define acceptance criteria during story elaboration, well before testing begins. This cross-functional input ensures criteria reflect both business intent and testability.

**Why not D:** Writing acceptance criteria after development is complete defeats their purpose. Acceptance criteria must be defined before development starts so they guide implementation and provide clear, upfront targets for what the story must achieve. Defining them retroactively would merely describe what was built rather than what should be built.