CAPM Practice: Determine how project methodologies influence business analysis processes

Regulated industries (pharmaceutical, financial services, aerospace) require documented evidence of requirements definition, testing, and traceability. BAs can maintain agile practices while producing compliance artifacts — defining what documentation is required and integrating it into the agile workflow.

**Why not A:** This overstates the constraint. Regulatory bodies such as the FDA and financial regulators do not mandate a specific project methodology — they mandate documentation, traceability, and evidence of validation. Many organizations in highly regulated industries have successfully adopted agile practices while meeting compliance obligations by tailoring their artifact production.

**Why not C:** Agile projects are absolutely not exempt from regulatory documentation requirements. In fact, one of the primary BA challenges in regulated agile environments is ensuring that compliance artifacts — requirements traceability matrices, validation summaries, test records — are produced as part of each sprint or release cycle, not as an afterthought.

**Why not D:** Regulatory requirements have a significant and direct effect on methodology selection and execution. Compliance mandates shape which artifacts must be created, how requirements must be traced and verified, and how changes must be controlled and approved — all of which influence whether a team adopts a predictive, adaptive, or hybrid approach.