Skip to content
CAPMEasy

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

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

Why is the use of a predictive approach sometimes called 'plan-driven'?
Show answer & explanation

Correct answer: Because the project is executed by following and managing against a detailed pre-established plan

Explanation

'Plan-driven' emphasizes that the project is executed by following a detailed plan established upfront. The plan drives decisions, work sequencing, resource allocation, and performance measurement. Work deviating from the plan is subject to change control. This is distinct from 'value-driven' adaptive approaches where iteration and feedback drive direction.

**Why not A:** Stakeholders driving changes to the plan describes change management or stakeholder influence, not the plan-driven nature of predictive methodology. Plan-driven means the plan drives execution, not that stakeholders drive changes to the plan.

**Why not B:** A plan driven by team self-organization describes agile or adaptive methodologies where empowered teams determine how work is accomplished. This is the opposite of plan-driven, where a detailed upfront plan guides all execution decisions.

**Why not D:** Plans continuously adapting based on new information describes adaptive methodology. Plan-driven specifically means the project follows a pre-established plan, with changes managed through formal change control rather than continuous adaptation.

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).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free