HKSM

Scope is the defined set of deliverables, outcomes, and work required to meet the project objectives, including what is included and explicitly excluded from the project.

Why this domain matters

Scope defines what the project will deliver and what work will be performed. When scope is clear and controlled, the team can focus on delivering agreed outcomes without constant surprises. Poorly defined or unmanaged scope leads to scope creep, rework, stakeholder dissatisfaction, and overruns in time and cost.

Key concepts

• Product scope: characteristics and features of the product, service, or result being delivered.
• Project scope: the work that must be performed to deliver the product, service, or result.
• Scope baseline: approved scope statement, work breakdown structure (WBS), and WBS dictionary.
• Requirements: documented needs and expectations that the project must satisfy.
• Acceptance criteria: measurable conditions used to accept deliverables as complete.

Common pitfalls and exam traps

• Allowing scope creep by accepting stakeholder requests without formal change control.
• Gold plating: adding extra features that were not requested or approved.
• Writing vague scope statements that invite conflicting interpretations later.
• Failing to link requirements to deliverables through a requirements traceability matrix.
• Exam trap: choosing to “update the schedule” or “add resources” before controlling scope through the change process.

PMP Example Question

PMP Example Question

A key stakeholder requests an additional reporting feature late in the project. The feature is not in the approved scope baseline but could provide value to users. What should the project manager do first?

1. Add the feature because it increases stakeholder satisfaction.
2. Evaluate the impact on schedule and cost and submit a change request.
3. Reject the request because it was not part of the original plan.
4. Ask the team to estimate the work and start development immediately.

Correct Answer: B — Evaluate the impact on schedule and cost and submit a change request.

Explanation: Any change to the approved scope baseline must follow the formal change control process. The project manager should first assess the impact of the requested feature and then submit a change request for review and approval. Automatically accepting or rejecting the request, or starting work without approval, bypasses proper scope governance.