CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 25 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: Initiation → Planning → Executing → Monitoring & Controlling → Closing
Explanation
The five process groups in the PMBOK® Guide for predictive projects are: Initiating, Planning, Executing, Monitoring & Controlling, and Closing. These represent the broad sequence of project management work, with Monitoring & Controlling running throughout Executing to manage performance.
**Why not B:** The Discover-Define-Design-Deliver-Deploy sequence is not the standard predictive project process group framework. This appears to be a design thinking or product development framework, not the PMBOK process groups used in traditional predictive project management.
**Why not C:** Initiation-Sprint Planning-Sprint Execution-Sprint Review-Retrospective describes the Scrum framework used in agile projects. This is fundamentally different from the predictive process groups, which follow a sequential rather than iterative pattern.
**Why not D:** Requirements-Design-Testing-Deployment-Retrospective describes a software development life cycle with an agile retrospective added. While it shares some sequential characteristics with predictive, it is not the standard PMBOK process group framework for predictive project management.
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