CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 80 of 85 in Explain when it is appropriate to use a predictive, plan-based approach
Show answer & explanation
Correct answer: Document the dependency in the project plan, include vendor milestones in the schedule, and manage through procurement management processes
Explanation
Predictive projects manage vendor dependencies proactively through procurement management. The dependency is formally documented, the vendor's key milestones are integrated into the project schedule, contracts specify deliverable dates and quality criteria, and risk management addresses vendor delay scenarios. This systematic approach is preferable to reactive management after problems occur.
**Why not B:** Assuming the vendor will deliver on time without documentation is a significant project management failure. Vendor dependencies are external risks that must be formally documented, monitored, and managed. Undocumented assumptions leave the project vulnerable to unplanned delays.
**Why not C:** Switching to an adaptive approach for one component is unnecessary when the dependency can be properly managed within the predictive framework. Predictive procurement management processes are specifically designed to handle vendor dependencies through contracts, milestones, and risk management.
**Why not D:** Waiting until the vendor delivers before including the component in the plan is reactive management that prevents proper scheduling and risk planning. The dependency must be incorporated into the schedule upfront so the project team can plan around it and prepare contingencies.
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