CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 47 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: Predictive with formal stage-gate reviews
Explanation
Formal management approval at phase boundaries is a defining characteristic of predictive project governance, implemented through stage-gate (phase-gate) reviews. These structured approval points give management visibility and control over the project at key decision points, aligning with organizational governance requirements.
**Why not A:** Extreme Programming (XP) with pair programming reviews is an agile software development practice. Pair programming reviews are informal, continuous quality checks — not the formal management approval at phase boundaries described in the question.
**Why not C:** Agile Scrum sprint reviews occur at the end of each sprint and involve stakeholder feedback on the product increment. They are collaborative demonstrations, not formal management approval gates that control progression between sequential project phases.
**Why not D:** Kanban uses continuous flow with work-in-progress limits and does not have defined phases or formal approval boundaries. It is designed for steady-state work management, which is incompatible with the structured phase-gate governance described in the question.
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