Ch 5 Project Scope Management Flashcards
Create Work Breakdown Structure (WBS)
The process of breaking down the deliverables into smaller, more manageable components (decomposition)
The main output is the Scope Baseline
Knowledge Area: Scope
Process Group: Planning
Inputs:
- Project Scope Statement
Tools:
- Decomposition
Outputs:
- Scope Baseline
- WBS
- WBS Dictionary
- Project Scope Statement
Deliverable Life Cycle
Deliverables are:
- Created (Direct and Mangage Project Work)
- Verified (Control Quality)
- Accepted (Validate Scope)
Control Scope
The process of monitoring the status of the project/product scope as it is executed to ensure that it aligns with the scope baseline, and also managing changes to the scope baseline
Knowledge Area: Scope
Process Group: Monitoring & Controlling
Inputs:
- Work Performance Data
Tools:
- Variance Analysis
Outputs:
- Work Performance Information
Focus Groups
A data gathering method in which SMEs and stakeholders gather to participate in a moderated discussion about their project expectations
A tool used to help execute the Collect Requirements process (Scope/Planning)
Requirements Management Plan
The management plan that documents how the requirements will be collected, analyzed, documented, and managed
An output of the Plan Scope Management process (Scope/Planning)
An input to the Develop Project Management Plan process (Integration/Planning)
Validate Scope
The process in which the project deliverables are formally inspected and accepted by the customer or sponsor; if the deliverables are rejected, they return to the team as a defect for repair
This process should be done immedately after (but can be done at the same time as) the Control Quality process (Quality/M&C), where the project manager inspects and verifies the deliverable against the quality requirements
Knowledge Area: Scope
Process Group: Monitoring & Controlling
Inputs:
- Verified Deliverables
Tools:
- Inspection
Outputs:
- Accepted Deliverables
Gold Plating
Doing extra work that is not in the scope baseline
This should never be done in project management because it can increase risk, cost, schedule problems, and quality problems
Requirements Documentation
Very detailed documentation of the actual requirements needed to complete the project
An output of the Collect Requirements process (Scope/Planning)
An input to the Define Scope process (Scope/Planning)
Project Scope Management
Knowledge area regarding management of project scope, aka the work required to complete the project
Product Analysis
A method of comparing of the product to the stakeholder requirements
A tool used to help execute the Define Scope process (Scope/Planning)
Verified Deliverables
A deliverable that has been inspected by the project manager to ensure that it meets the quality requirements
An output of the Control Quality process (Quality/M&C)
An input to the Validate Scope process (Scope/M&C)
Project Scope
The work that is needed to deliver a product, service, or result with specified features and functions
Brainstorming
A data gathering method that usually allows stakeholders to generate, gather, and document many ideas
A tool used to help execute the Collect Requirements process (Scope/Planning)
Variance Analysis
A data analysis method of determining if there is a variance between the planned work (project management plan) and the actual work (work performance data).
If so, the PM may need to submit a change request
Delphi Technique
A technique where requirements are collected anonymously from SMEs so that they cannot influence each other
Benefits of this technique:
- Different geographical areas
- Reduce individual bias
- People may disclose risks they may not want to discuss in front of a group
- Minimize group thinking
A tool used to help execute the Collect Requirements process (Scope/Planning)
Inspection
A method by which the project manager and/or team inspects deliverables to ensure that it meets quality requirements
A method by which the customer or sponsor validates that the deliverables meet their requirements
This can include walkthroughs, audits, or visual inspection
A tool (never an input or output) used to help execute the;
- Control Quality process (Quality/M&C)
- Validate Scope process (Scope/M&C)
- Control Procurements process (Procurement/M&C)
Facilitation
A method of bringing stakeholders together to gather requirements
Examples include:
- A workshop or interactive discussion designed to quickly define requirements, solve differences, and build trust
- Quality Function Deployment (QFD) is a requirements workshop used mostly in manufacturing
A tool used to help execute the Collect Requirements process (Scope/Planning)
Product Scope
Features and functions that characterize a product, service, or result
Requirements for a product
Nominal Group Technique
A technique that involves ranking and prioritizing the ideas from brainstorming
A tool used to help execute the Collect Requirements process (Scope/Planning)
Plan Scope Management
The process of creating the scope and requirement management plans, which will document how the project will collect the requirements, as well as define, validate, and control the project scope
Knowledge Area: Scope
Process Group: Planning
Inputs:
- Project Charter
- (NOT the Stakeholder Register)
Tools:
- None
Outputs:
- Scope Management Plan
- Require Management Plan
Decomposition
A technique in which the high-level project deliverables from the scope statement are divided into smaller parts, known as work packages, to estimate time and cost for stakeholder acceptance
A technique used to break down the work packages on the WBS into specific activities that represent the work efforts needed to accomplish the work packages; multiple activities can be assigned to a work package
A tool used to help execute the:
- Create WBS process (Scope/Planning)
- Define Activities process (Schedule/Planning)
Scope Baseline
One of the three baselines in the project management plan, this document has three components:
- Work Breakdown Structure (WBS): A hierarchical graphic illustrating the work needed to produce the project deliverables (control accounts broken down into one or more work packages); provides a structure for integrating scope, schedule, and cost info
- WBS Dictionary: A document with details about each work package in the WBS (e.g., detailed description of work, scheduling, cost estimates, assumptions, constraints, acceptance criteria); may be a series of tables, one for each work package
- Project Scope Statement: the document that was used to create the WBS; an output of the Define Scope process and an input of the Create WBS process
The only output of the Create WBS process (Scope/Planning)
An input to the
- Define Activities process (Schedule/Planning)
- Plan Procurement Management process (Procurement/Planning)
Scope Creep
Unapproved expansion of the scope (without control)
Requirements Traceability Matrix
A table that is created to link the requirements back to their origin (e.g., who gave the requirement, why it was added to the project)
An output of the Collect Requirements process (Scope/Planning)
