05 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 in doing the work.
Affinity diagrams
When stakeholders create a large number of ideas, you can use an affinity diagram to cluster similar ideas together for further analysis.
Alternatives generation
A scope definition process of finding alternative 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 participants to generate as many ideas as possible about the project requirements. No idea is judged or dismissed during the brainstorming 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.
Code of accounts
A numbering system for each item in the WBS. The PMBOK is a good example of a code of accounts, as each chapter and its subheadings follow a logical numbering scheme. For example, PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK.
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
These diagrams show the relationship between elements of an environment. For example, a context diagram would illustrate the networks, servers, workstations, and people that interact with the elements of the 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 qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created.
Interviews
A 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 ideas to show the relationship among requirements and the differences between requirements. The map can be reviewed to identify new solutions or to rank the identified requirements.
Nominal group technique
As with brainstorming, participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process.
Passive observation
The observer records information about the work being completed without interrupting the process; sometimes called the invisible observer.