CAPMEasy

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

Question 12 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.

In a predictive approach, stakeholder requirements are typically gathered:

Show answer & explanation

Correct answer: At the beginning of the project, before detailed planning

Explanation

Predictive approaches front-load requirements gathering. Stakeholder needs, expectations, and requirements are documented comprehensively before detailed planning begins. This comprehensive requirements phase forms the foundation of the scope baseline and all subsequent planning.

**Why not A:** Continuously gathering requirements throughout the project is characteristic of adaptive (agile) approaches, where requirements emerge through iterative discovery. Predictive approaches deliberately front-load requirements gathering to enable comprehensive upfront planning.

**Why not B:** Refining scope after each phase describes an iterative or rolling-wave approach. In a fully predictive approach, requirements are gathered comprehensively at the beginning, not progressively refined phase by phase.

**Why not C:** Gathering requirements during closeout would be far too late — the project is already complete. Requirements must be known before work begins so that scope, schedule, and cost baselines can be established.

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