Scope Management Flashcards
7 cards from real PMP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Scope Management flashcards as text
Which document defines all requirements that must be met for the project to be accepted, including measurable acceptance criteria?
Answer: Project Scope Statement
The project scope statement includes deliverables, acceptance criteria, project exclusions, and constraints that define what must be met for acceptance.
A project has a well-documented scope baseline, but the project manager is concerned about scope creep. The BEST preventive measure is:
Answer: Rigorously enforce the integrated change control process for all scope changes
Rigorous integrated change control is the most effective preventive measure against scope creep by ensuring all changes are formally evaluated and approved.
Which of the following is NOT an output of the Validate Scope process?
Answer: Scope baseline updates
Scope baseline updates are an output of Control Scope, not Validate Scope; Validate Scope produces accepted deliverables, work performance information, and change requests.
A project manager uses facilitated workshops to collect requirements. What is the PRIMARY advantage of this technique?
Answer: It allows cross-functional stakeholders to rapidly define and reconcile requirements together
Facilitated workshops bring together cross-functional stakeholders to quickly discover and reconcile differences in requirements, building consensus efficiently.
When a project manager performs variance analysis during scope control, they are PRIMARILY comparing:
Answer: Scope baseline versus actual scope performance
In Control Scope, variance analysis compares the approved scope baseline against actual project performance to determine if a variance exists.
An agile project team refers to the product backlog as a living document. In terms of traditional scope management, the product backlog MOST closely aligns with:
Answer: The requirements documentation
The product backlog captures and prioritizes all features and requirements, most closely aligning with requirements documentation in traditional approaches.
A project manager is told by a team member that a feature was quietly removed from the deliverable to save time. What should the project manager do?
Answer: Document it as a change request and process it through change control
Removing work from scope is a scope change that must be formally processed through integrated change control regardless of the reason.