CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 44 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 defined milestones or at project completion, following a sequential plan
Explanation
Predictive projects typically deliver outputs at defined milestones or at project end, following sequential phases. Unlike adaptive approaches that deliver incremental functionality throughout the project, predictive projects often produce the complete integrated product at completion (though major milestones may include intermediate deliverables like design documents or prototypes).
**Why not A:** Delivering in two-week sprints with reviews describes an agile/Scrum delivery cadence. Predictive projects do not use sprint-based iterative delivery; they follow sequential phases with deliverables at planned milestones or project completion.
**Why not C:** Continuous delivery of features as they are completed describes a continuous delivery or DevOps approach. Predictive projects plan deliverables for specific milestones rather than releasing individual features as soon as each one is ready.
**Why not D:** Incremental delivery of small usable pieces throughout the project describes an incremental or agile delivery strategy. Predictive methodology produces integrated deliverables at planned milestones following the sequential plan, not in small ongoing increments.
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