CAPM - Predictive, Plan-Based Methodologies (17% of the exam) - Section 2.1

Apply scope management techniques including requirements collection, scope definition, and decomposition into a work breakdown structure (WBS).

Collect requirements, define project and product scope, and decompose deliverables into a work breakdown structure (WBS) whose lowest level is the work package. Recognise that the scope baseline comprises the scope statement, the WBS, and the WBS dictionary, and that uncontrolled additions to scope without process constitute scope creep.

Work breakdown structureScope baselineWork packageScope creepRequirements collection

Practice question for this objective

Free samplePredictive, Plan-Based Methodologiesmedium

On the Harbourgate fit-out project, the project manager has just finished baselining scope with the sponsor. A team member asks which set of documents makes up the approved scope baseline. Which combination correctly identifies the scope baseline?

AThe project charter, the stakeholder register, and the requirements traceability matrix
BThe approved project scope statement, the schedule baseline, and the cost baseline
CThe approved project scope statement, the work breakdown structure, and the WBS dictionary Correct
DThe requirements management plan, the scope management plan, and the change log

Identify that the scope baseline comprises the approved scope statement, the WBS, and the WBS dictionary. The scope baseline is the approved scope statement plus the WBS and its dictionary, because together these fix the agreed deliverables and work against which change control and performance are measured.

Why A is wrong: These are genuine scope-related inputs and outputs, but the charter and stakeholder register sit outside the scope baseline and the traceability matrix links requirements rather than forming the baseline itself.

Why B is wrong: This mixes three separate baselines together; the schedule and cost baselines are distinct from the scope baseline and are not part of its definition.

Why C is correct: The scope baseline is the approved version of the scope statement, the WBS, and the WBS dictionary, and changes to it are controlled through formal change control.

Why D is wrong: These are planning and control artefacts that guide how scope is managed, but they describe the process rather than defining the approved scope content itself.

See more CAPM practice questions, answers explained.

Exam traps in Predictive, Plan-Based Methodologies

Answers that look right on this material and are not. Each one is a distractor from a different question in the CAPM bank for this domain.

Progressive elaboration, because the deliverable is naturally becoming more detailed as the team learns more.
Why it is wrong: Progressive elaboration refines planned work within approved scope; adding unapproved deliverables is not the same as detailing existing ones.
The project charter, the stakeholder register, and the requirements traceability matrix.
Why it is wrong: These are genuine project documents, but the charter authorises the project and the register and matrix track stakeholders and requirements rather than defining the approved scope baseline.
The requirements documentation, the requirements traceability matrix, and the stakeholder register
Why it is wrong: These are useful scope-related records produced during requirements collection, but they are inputs and supporting tools rather than the approved baseline that scope is measured against.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.