CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 43 of 85 in Explain when it is appropriate to use a predictive, plan-based approach
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: An appropriate use of predictive methodology given fully documented, approved requirements
Explanation
A 500-page, stakeholder-approved requirements specification is exactly the conditions under which predictive methodology thrives. In aerospace, requirements are comprehensive by necessity (safety, regulatory, contractual). Fully documented and approved requirements support detailed planning, cost estimation, and sequential execution — the hallmarks of effective predictive project management.
**Why not A:** Rejecting the approach in favor of adaptive methodology ignores the project context. When requirements are fully documented, stakeholder-approved, and the domain demands rigorous documentation (aerospace), predictive methodology is the appropriate choice, not poor planning.
**Why not C:** While scope creep is always a possibility, a 500-page stakeholder-approved specification represents thorough requirements documentation. Assuming it is inherently incomplete dismisses the rigorous requirements process that aerospace projects demand and deliver.
**Why not D:** Demanding a predictive approach for a well-specified aerospace system demonstrates understanding of project context, not ignorance of modern project management. Modern project management recognizes that different project types benefit from different methodologies.
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