Exam PMI-ACP topic 1 question 318 discussion

In agile, particularly in approaches like Test-Driven Development (TDD) or Behavior-Driven Development (BDD), writing tests before coding ensures that the team has a clear understanding of the definition of done and the acceptance criteria for each story. Writing tests early also helps to catch issues earlier in development and aligns the team on the expected outcomes of the stories. Other options are less appropriate: A: Running automated tests on legacy functionality might be important for regression testing, but it's not the next immediate step after defining new requirements for the iteration. B: Asking the customer to write tests might not be feasible or appropriate. The customer provides the acceptance criteria, but it’s up to the team to translate those into tests. C: Starting coding without writing tests or having well-defined tests first can lead to misunderstanding of requirements or missed edge cases.

1.Test-Driven Development (TDD): Agile encourages a TDD approach, where tests are written before coding to ensure Clarity about requirements and acceptance criteria. 2. Customer Collaboration 3. Iteration Planning 4. Quality Assurance

D is correct (TDD)