CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 3 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: At the beginning of the project, before work begins
Explanation
A hallmark of predictive approaches is front-loaded planning. Scope, schedule, and cost baselines are established at the beginning. This allows for detailed planning, resource allocation, and cost estimation before work commences, with changes controlled through a formal change management process.
**Why not A:** Iterative determination through sprints is characteristic of adaptive (agile) approaches, not predictive. In adaptive projects, scope is refined each sprint based on feedback, but predictive projects define scope, schedule, and cost upfront before execution begins.
**Why not C:** Continuously adjusting scope, schedule, and cost based on stakeholder feedback throughout execution describes an adaptive approach. Predictive projects resist changes during execution and manage them through formal change control rather than continuous incorporation.
**Why not D:** Determining scope, schedule, and cost at the end of each phase based on deliverables completed describes an incremental or phase-gated approach with progressive elaboration. In a purely predictive project, all three are established at the beginning during the planning phase, not progressively at phase boundaries.
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