CAPM Practice: Determine how project methodologies influence business analysis processes

Continuous requirements (also called 'emergent requirements') acknowledges that the full picture is rarely known at the start. Requirements evolve through delivery experience, user feedback, market changes, and technical learning — the BA facilitates this ongoing discovery.

**Why not A:** This describes cross-cutting or persistent requirements, not "continuous requirements" in the adaptive methodology sense. Continuous requirements refers to the ongoing process of discovering and refining requirements, not requirements that apply universally across product versions.

**Why not C:** Continuous requirements does not mean discarding previous work each sprint. While requirements evolve, adaptive methodologies still build on prior understanding and maintain traceability. Redefining requirements from scratch each sprint would be wasteful and chaotic, undermining the iterative learning that adaptive approaches depend on.

**Why not D:** Automated testing is a verification technique, not a requirements approach. While continuous testing may validate requirements, "continuous requirements" specifically describes how requirements are progressively elaborated and refined throughout the project lifecycle, not how they are monitored by tools.