CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

FDA-regulated pharmaceutical projects require extensive documentation, formal validation protocols, defined approval gates, and audit trails — all characteristics of predictive methodology. While clinical trials involve uncertainty, the overall project framework must be predictive to meet regulatory requirements. (Note: Some companies do use hybrid approaches, but pure predictive is most aligned with FDA requirements.)

**Why not A:** While a product owner can represent requirements in Scrum, FDA regulatory compliance demands extensive formal documentation, stage-gate approvals, and audit trails that go beyond what Agile Scrum naturally provides. The regulatory framework demands predictive rigor.

**Why not C:** While clinical trials do involve unknowns, the overall pharmaceutical project framework requires strict documentation, formal validation protocols, and defined approval gates. These regulatory demands outweigh the argument for adaptive methodology.

**Why not D:** While some companies experiment with hybrid approaches, the question asks which is MOST appropriate. The regulatory requirements for formal documentation, validation, and stage-gate approvals make a pure predictive approach the most natural and compliant fit.