CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 8 of 85 in Explain when it is appropriate to use a predictive, plan-based approach
Show answer & explanation
Correct answer: Predictive, because the requirements are clear and compliance demands documentation
Explanation
Clear, documented requirements and regulatory compliance needs are defining characteristics of projects suited to predictive approaches. The well-defined process and outcome mean that iterative discovery is unnecessary, and the compliance requirement for audit trails is better served by predictive documentation practices.
**Why not A:** Adaptive methodology may support rapid iteration, but when the process is well-documented with clearly defined outcomes, iterative discovery is unnecessary. The stable, known requirements and compliance demands favor predictive over adaptive approaches.
**Why not B:** A hybrid approach mixing agile sprints with waterfall documentation adds unnecessary complexity when the project characteristics all point to predictive. The well-defined process and clear outcome do not require the iterative discovery component of hybrid methodology.
**Why not C:** A manufacturing quality improvement project with regulatory compliance absolutely requires a formal methodology. The audit trail requirements alone demand structured documentation and governance that informal approaches cannot provide.
Key Concept
This question covers Explain when it is appropriate to use a predictive, plan-based approach under Explain when it is appropriate to use a predictive, plan-based approach (Predictive, Plan-Based Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free