Scope and WBS Development Flashcards
7 cards from real PMBOK 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 and WBS Development flashcards as text
A project manager is rolling out an ERP system in phases. To allow flexibility in future phases while maintaining control, which WBS element should be used for undefined future work?
Answer: Planning package
A planning package is used when the scope is known but detailed planning cannot yet be completed, allowing structured flexibility.
Prototyping is used as a requirements elicitation technique primarily because it:
Answer: Allows stakeholders to provide feedback on a tangible model before final design
Prototyping provides stakeholders with a working model to experiment with, enabling earlier and more accurate feedback on requirements.
Scope verification (now called Validate Scope) differs from quality control because:
Answer: Scope validation focuses on acceptance of deliverables; quality control focuses on correctness of deliverables
Validate Scope focuses on formally accepting completed deliverables with stakeholders, while quality control focuses on meeting quality requirements.
A project manager discovers that the project scope statement is missing the product acceptance criteria. What risk does this create?
Answer: Stakeholders may disagree on what constitutes successful completion of deliverables
Without clear acceptance criteria, stakeholders have no agreed-upon definition of done, creating high risk of disputes during scope validation.
Which of the following is an output of the Create WBS process?
Answer: Scope baseline
The scope baseline—comprising the approved project scope statement, WBS, and WBS dictionary—is the key output of Create WBS.
A project manager is told by a team member that a feature was added because 'the customer mentioned they would like it.' No formal change request was submitted. This is BEST described as:
Answer: Scope creep
Scope creep is the unauthorized expansion of project scope; adding features based on informal stakeholder comments without change control is a classic example.
When using the expert judgment technique in the Collect Requirements process, who would be the MOST valuable source?
Answer: Subject matter experts with domain experience relevant to the product
Subject matter experts with relevant domain experience can identify requirements that stakeholders may not think to articulate.