CAPM Practice: Determine how to document project controls of predictive, plan-based projects
Question 49 of 85 in Determine how to document project controls of predictive, plan-based projects
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Root cause of the delay, specific actions to recover the schedule, responsible parties, and target dates for recovery
Explanation
A corrective action plan addresses: what caused the problem (root cause analysis), what specific actions will be taken to correct it (recovery actions), who is responsible for each action, and by when. This structured approach transforms a problem statement into an actionable recovery plan that stakeholders can evaluate and support.
**Why not A:** Requesting a deadline change is one possible option but should not be the entire corrective action plan. A proper plan analyzes the root cause, proposes specific recovery actions, and may include deadline extension as one option among several for the sponsor to evaluate.
**Why not B:** Listing team members responsible for the delay is blame-oriented rather than solution-oriented. A corrective action plan should focus on what happened, why it happened, and what specific actions will fix it — not on assigning personal fault.
**Why not C:** Stating that the project will be late with no possible action is defeatist and rarely accurate. A project manager should always analyze recovery options — crashing, fast tracking, scope adjustment, resource reallocation — before concluding that no corrective action is possible.
Key Concept
This question covers Determine how to document project controls of predictive, plan-based projects under Determine how to document project controls of predictive, plan-based projects (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