Project Scope Management Terms Flashcards
8/80 Rule
A planning heuristic for creating the WBS. This rule states that the work package in a WBS must take no more than 80 hours of labor to create and no fewer than 8 hours of labor to create
Active Observation
The observer interacts with the worker to ask questions and understand each step of the work being completed. In some instances, the observer could serve as an assistant doing the work
Affinity Diagrams
When stakeholders create a large number of ideas, you can use these diagrams to cluster similar ideas together for further analysis
Alternatives Generation
A scope definition process of finding other solutions for the project customer while considering the customer’s satisfaction, the cost of the solution, and how the customer may use the product in operations
Autocratic
A decision method where only one individual makes the decision for the group
Brainstorming
This approach encourages particpants to generate as many ideas as possible about the project requirements. No idea is judges or dismissed during this session
Change Control System (CCS)
Documented in the scope management plan, this system defines how changes to the project scope are managed and controlled
Change Management plan
This subsidiary plan defines how changes will be allowed and managed within the project
A numbering system for each item in the WBS
Code of Accounts
Configuration management plan
This subsidiary plan defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project
Context Diagram
This diagram shows the relationship between elements of an environment.
Focus Groups
A moderator led requirements collection method to elicit requirements from stakeholders
Functional Analysis
This is the study of the functions within a system, project, or, what’s more likely in the project scope statement, the product the project will be creating. Functional analysis studies the goals of the product, how the product will be used, and the expectations the customer has of the product once it leaves the project and moves into operations. Functional analysis may also consider the cost of the product in operations, which is known as life-cycle costing.
Funding Limit
Most projects have a determined budget in relation to the project scope. There may be a qualified on this budget, such as plus or minus 10 percent ased on the type of cost estimate created
Interviews
Requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation
Majority
A group decision method where more than 50 percent of the group must be in agreement
Mind Mapping
This approach maps the ideas to show the relationship among the requirements and the differences between requirements. Can be reviewed to identify new solutions or to rank the identified requirements
Nominal group technique
Participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process
Passive Observation
Observer records information about the work being completed without interrupting the process
Plurality
A group decision method where the largest part of the group makes the decision when it’s less than 50 percent of the total
Product Acceptance Criteria
This project scope statement component works with the project requirements, but focuses specifically on the product and what the conditions and processes are for formal acceptance of the product
Product Breakdown
A scope definition technique that breaks down a product into hierarchical structure, much like a WBS breaks down a project scope
Product Scope Description
This is a narrative description of what the project is creating as a deliverable for the project customer
Product Scope
Defines the product or service that will come about as a result of completing the project. It defines the features and functions that characterize the product
Project Assumptions
This is a factor in the planning process that is held to be true but not proven to be true
Project Boundaries
This clearly states what is included with the project and what’s excluded from the project. Helps to eliminate assumptions between the PM team and the project customer.
Project Constraints
This is anything that limits the PM’s options. Consider a predetermined budget, deadline, resources, or materials the PM must use within the project - these are all examples of what?
Project Objectives
Measurable goals that determine a projects acceptability to the project customer and the overall success of the project. Often include the cost, schedule, technical requirements, and quality demands.
Project requirements
These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be acceptable
Project scope
This defines all of the work, and only the required work, to complete the project objectives
Project scope management plan
This PM subsidiary plan controls how the scope will be defined, how the project scope statement will be created, how the WBS will be created, how scope validation will proceed, and how the project scope will be controlled throughout the project
Requirements documentation
Documentation of what the stakeholders expected in the project defines all of the requirements that must be present for the work to be accepted by the stakeholders
Requirements management plan
Subsidiary plan defines how changes to the project requirements will be permitted, how requirements will be tracked, and how changes to the requirements will be approved
Requirements traceability matrix
This is a table that maps the requirements throughout the project all the way to their completion
Schedule milestones
The project customer may have specific dates when phases of the project should be completed. Often treated as project constraints
Scope creep
Undocumented, unapproved changes to the project scope
Scope validation
The formal inspection of the project deliverables, which leads to project acceptance
Stakeholder analysis
Scope definition process where the PM team interviews the stakeholders and categorizes, prioritizes, and documents what the project customer wants and needs. This analysis is to determine, quantify, and prioritize the interests of the stakeholders
Systems analysis
A scope definition approach that studies and analyzes a system, its components, and the relationship of the components within the system
Systems engineering
Project scope statement creation process studies how a system should work, designs and creates a system model, and then enacts the working system based on the projects goals and the customers expectations
Unanimity
A group decision method where everyone must be in agreement
Value analysis
As with value engineering, this approach examines the functions of the project’s product in relation to the cost of the features and functions
Value Engineering
This approach to project scope statement creation attempts to find the correct level of quality in relation to a reasonable budget for the project deliverable while still achieving an acceptable level of performance of the product
WBS Dictionary
A WBS companion document that defines all of the characteristics of each element within the WBS
WBS Template
A prepopulated WBS for repetitive projects.
Work breakdown structure WBS
A deliverables-oriented breakdown of the project scope
Work Package
The smallest item in the WBS
Work performance information
Status of the deliverables : the work that’s been started, finished, or has yet to begin
