Project Scope and WBS Flashcards
7 cards from real Project Management practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Project Scope and WBS flashcards as text
A WBS dictionary primarily serves to:
Answer: Provide detailed descriptions of each WBS component including acceptance criteria
The WBS dictionary supports each WBS component with details such as description, acceptance criteria, responsible party, and resource requirements.
Scope creep most commonly results from:
Answer: Inadequate change control and stakeholder management
Scope creep typically occurs when changes are allowed informally without going through change control and stakeholder agreements are unclear.
On a large program, a project manager is uncertain about the details of work that is 6 months away. The best approach is:
Answer: Use rolling wave planning to plan near-term work in detail and far-term work at a high level
Rolling wave planning allows progressive elaboration, detailing near-term work while keeping far-term work at a higher level until more information is available.
Which of the following is NOT typically included in a project scope statement?
Answer: Resource assignments by name
Resource assignments by name belong in the resource management plan, not the scope statement.
A customer requests a feature during execution that was explicitly listed as an exclusion in the scope statement. The PM should:
Answer: Evaluate the request and process it through integrated change control
Even excluded items can be added via formal change control; the PM should evaluate and process the request properly rather than refusing outright.
The process of monitoring the status of the project and product scope and managing changes to the scope baseline is called:
Answer: Control Scope
Control Scope is the process of monitoring scope status and managing changes to ensure the scope baseline is maintained.
In agile projects, the product backlog most closely corresponds to which traditional PM artifact?
Answer: Scope statement and requirements documentation
The product backlog serves as the evolving list of features and requirements, functioning similarly to the scope statement and requirements documentation in predictive approaches.