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

Regulated industries (construction, pharmaceuticals, aerospace, government contracting) often mandate extensive documentation, formal stage-gate approvals, and traceability — characteristics that align naturally with predictive methodologies. The structured, document-heavy nature of predictive approaches satisfies compliance and audit requirements.

**Why not A:** Short project duration with minimal stakeholder involvement does not inherently favor predictive methodology. Predictive approaches are chosen based on requirement stability and regulatory needs, not project duration or stakeholder involvement level.

**Why not C:** Vague requirements expected to emerge over time are the opposite of what predictive methodology requires. When requirements are unclear and evolving, adaptive or iterative approaches are more appropriate because they accommodate changing scope.

**Why not D:** High novelty with no historical precedent favors adaptive approaches where the team can learn and adjust through iterations. Predictive approaches work best when the work is well-understood, not when the team is exploring entirely new territory.