CAPMEasy

CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

Question 70 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.

A project that uses a predictive approach would use which document to track what work has been approved but not yet started?

Show answer & explanation

Correct answer: Project scope statement and WBS

Explanation

In a predictive project, the project scope statement and WBS define all approved work. Unlike adaptive projects (which use a product backlog), predictive projects front-load scope definition. The WBS represents all work that has been authorized to be performed. Progress against this defined scope is tracked through schedule and earned value tools.

**Why not A:** The lessons learned register documents insights and knowledge gained during the project for future reference. It does not track what work has been approved but not yet started — that is the function of scope documentation.

**Why not C:** The sprint backlog is an agile artifact used in Scrum to track work selected for a specific sprint. Predictive projects do not use sprint backlogs; they use the WBS and project scope statement to define and track approved work.

**Why not D:** The issue log tracks problems and concerns that have arisen during the project and their resolution status. It does not define or track the scope of approved project work — that role belongs to the scope statement and WBS.

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