Project Scope Management (Section 10) Flashcards
Which project documents can come from templates?
Scope management plans
WBS
Project change control forms
What is the difference between the product scope and the project scope?
Product scope is a description of the product deliverables; Project scope is a document that defines the required work to create the project deliverables
How are the requirements traceability matrix and the configuration management plan related?
A configuration management plan defines, documents, audits, etc all components of a project. A requirements traceability matrix could be part of a Configuration Management System (CMS)
What happens first - Quality Control or Scope Validation? Who is responsible for each of these activities?
Quality Control always happens prior to Scope Validation - Scope validation is the customer accepting the project deliverables
What is the result/output of scope validation?
Formal acceptance
What are the three most important documents that support project scope management?
- Work Breakdown Structure (WBS)
- WBS Dictionary
- Project scope statement
What are common outputs of change control?
Recommended corrective action
At what point in the scope change process should a new baseline be created?
Only when a scope change is approved
What is the project scope statement decomposed into?
Smaller deliverables in the Work Breakdown Structure
Which of these does the WBS NOT serve as an input to?
A. Planning cost management
B. Control procurements
C. Risk identification
D. Cost budgeting
A. Planning cost management - WBS is part of the planning process group; the next process groups linearly are executing, monitoring/controlling
How are the sizes of work packages in the WBS determined?
The 8/80 rule - a work package should take no more than 80 hours of labor and no less than 8 hours of labor
In general - the intent of work package size is an appropriate size where time and cost can be calculated
What are key steps to creating a WBS?
- Start with the project scope statement
- Define key deliverables and dates
- For each deliverable, define the tasks and subtasks needed to create. Groups of deliverables should be work packages - the work, owner, cost, and timeline should all be identified
**Focus on deliverables, not actions