Quality Management Flashcards

Enhance your quality management skills by exploring key concepts, adaptive approaches, and cost-quality trade-offs. Learn to plan, manage, and control project quality using benchmarking, design experiments, trend analysis, and statistical sampling techniques.

1
Q

Define:

Activity Network Diagram

A

These diagrams, such as the project network diagram, show the flow of the project work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Define:

Affinity Diagram

A

This diagram breaks down ideas, solutions, causes, and project components and groups them together with other similar ideas and components.

When stakeholders create a large number of ideas, you can use an affinity diagram to cluster similar ideas together for further analysis.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Define:

Appraisal Costs

A

These are monies spent to test, evaluate, measure, and audit the product, deliverables, or services of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Define:

Brain Writing

A

A data-gathering technique that’s similar to brainstorming, but provides brainstorming meeting participants with the questions and topics for brainstorming before the stakeholder identification meeting.

In this approach the topic is introduced and then each person writes down his or her ideas and thoughts. After a time period, the ideas are openly shared with the other participants.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Define:

Brain-Netting

A

A brainstorming approach that utilizes web tools to enable virtual teams to brainstorming and collaborate on ideas.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Define:

Built-In Quality

A

By planning quality in the design of the product specifications, quality is more likely to be achieved in the execution.

The product owner and team should work together to gain a full understanding of the value the customer expects from the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Define:

Cause-and-Effect Diagrams

A

Diagrams that show the relationship between variables within a process and how those relationships may contribute to inadequate quality.

Also known as Ishikawa Diagrams or Fishbone Diagrams. The diagrams can help organize both the process and the team opinions, as well as generate discussion on finding a solution to ensure quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

List:

Check Sheet

A

This is a quality tool used to tally up problems, effects, conditions, or other aspects about a project’s product during an inspection.

The results of check sheets help project managers quickly ascertain problems within the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Define:

Checklist

A

A simple approach to ensure that work is completed according to the quality policy.

For example, an electrician may have a checklist of tasks to complete when installing a new electrical fixture.

The checklist of steps for the activity ensures safety and consistency, as well as providing some evidence that all steps have been followed by the team members doing the work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define:

Coding Standards

A

An agreed-upon approach to how the code will be built, the naming system for the coding, and other standards for the code. This is always used in an XP project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Define:

Common Cause

A

An issue solved through trend analysis because the issue is systematic.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define:

Control Chart

A

A quality control chart that maps the performance of project work over time.

Control charts are typically used in projects or operations that include repetitive activities such as product manufacturing, a series of tests, or help desk issues.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Define:

Control Quality

A

An inspection-driven process that measures work results to confirm that the project is meeting the relevant quality standards.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define:

Cost of Conformance

A

This is the cost associated with the monies spent to attain the expected level of quality.

It is also known as the cost of quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Define:

Cost of Conformance to Quality

A

The cost associated with the monies spent to attain the expected level of quality.

It is also known as the cost of quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Define:

Design for X

(DfX)

A

This is a philosophy in product design, where the “X” can mean excellence, or, more often, a specific characteristic of a solution.

The X is usually a variable that the project is trying to address, such as cost, uptime, return on investment, or another facet the organization is pursuing.

Design for X considers all components of the design and how the component affects the X variable for better or for worse.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Define:

Design-of-Experiments

A

This approach relies on statistical what-if scenarios to determine what variables within a project will result in the best outcome.

This type of approach is most often used on the product of the project rather than on the project itself.

The goal of the design of experiments is to isolate the root cause of an effect and to adjust that cause to eliminate the unacceptable results.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Define:

Establish Quality in the Organizational Culture

A

Quality in the organizational culture makes quality a priority and a way of doing business for all members of the organization.

When an organization first embraces an adaptive approach, some customers may find it difficult to “follow the rules” of Agile.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Define:

External QA

A

Assurance provided to the external customers of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Define:

Failure Costs

A

The costs incurred due to defects, errors, or nonconformance to requirements.

They are part of the Cost of Quality (CoQ) and are categorized into Internal and External Failure Costs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Define:

Find the Defects through Quality Control

A

This quality management approach uses quality control (QC) to inspect the deliverables to keep mistakes out of the customer’s hands.

This approach still has internal costs (called internal failure costs), because you must correct the defects and redo work. Agile projects utilize testing to catch defects before they escape to the project customers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Define:

Flowchart

A

A diagram illustrating how components within a system are related. Also called process maps, these can show branching, loopbacks, or multiple paths through the system.

Flowcharts show the relation between components, as well as help the project team determine where quality issues may be present and, once done, plan accordingly.

System or process flowcharts show the relationship between components and how the overall process works. These are useful for identifying risks between system components.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Define:

Histogram

A

A bar chart that can represent categories of defects, ranking of quality problems, and any other data you want to display regarding managing quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Define:

Internal QA

A

The processes, activities, and practices carried out within the project or organization to ensure that the project meets its quality standards and requirements.

It focuses on identifying and addressing issues before the product or service is delivered to the customer.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
# Define: Ishikawa Diagrams
These cause-and-effect diagrams are also called fishbone diagrams and are used to find the root cause of factors that are causing risks within the project.
26
# Define: ISO
The abbreviation for the International Organization for Standardization. ## Footnote ISO is Greek for “equal,” while “International Organization for Standardization” in a different language would be abbreviated differently. The organization elected to use “ISO” for all languages. The abbreviation for the International Organization for Standardization, an independent, non-governmental international organization that sets standards and specifications for products, services, and systems to ensure quality, safety, and efficiency. The ISO is instrumental in facilitating international trade.
27
# Define: Let the Customer Find the Defects
This quality management approach is the most expensive and most aggravating, and it can lead to loss of sales, reputation, warranty claims, and other costs. ## Footnote Defects that make it to production are called escaped defects.
28
# Define: Logical Model Data
This data is used to visualize the organization’s data in common business language. ## Footnote For example, data for each employee could include country, state or region, phone, e-mail, and other facts. Logical model data would illustrate all of the data that contributes to the information for an employee in generic terms.
29
# Define: Matrix Diagram
A data analysis table that shows the strength between variables and relationships in the matrix. ## Footnote These tables show the relationship among different factors for example, roles and responsibilities, costs and risks, quality and scope.
30
# Define: Pareto Diagram
A histogram that illustrates and ranks categories of failure within a project. ## Footnote The project team should first work on the larger problems and then move on to the smaller problems.
31
# Define: Pareto Principle
Known as the 80/20 rule. For Agile projects, it means that 80 percent of all development should be spent on the top 20 percent of the features the customers need. ## Footnote In the context of Agile projects, this principle can be applied to feature prioritization. It means that 80 percent of customer value or impact typically comes from 20 percent of the features. Therefore, Agile teams should focus on delivering the most valuable 20 percent of features that will provide the greatest benefit to the customers.
32
# Define: Plan-Do-Check-Act | (PDCA)
A cyclical methodology used for continuous improvement in processes and products. ## Footnote It encourages iterative cycles of planning, implementing, evaluating, and refining to improve outcomes.
33
# Define: Prevent Defects through Quality Assurance Programs
Quality assurance (QA) means inspecting and creating processes to try to ensure that the work is correctly the first time, resulting in good, quality work. ## Footnote Truly understanding what the customer wants and writing good user stories will help the team recognize the DoD and what is required to pass QA tests.
34
# Define: Prevention Costs
These are monies spent to prevent poor quality.
35
# Define: Process Analysis
This technique examines the project management processes to see what processes need improvement, have constraints, or may be non–value-added activities for the project. ## Footnote If it doesn’t add value, in Agile, it shouldn’t be done.
36
# Define: Product Vision
A document that describes what the product is, who will use the product, why the product will be used, and how the product supports the strategy of a company. ## Footnote Defines exactly what the end result of the project should create in terms of functionality and value for the customers.
37
# Define: Project Dashboard
Consider a project web site, where stakeholders can periodically visit for a quick update on the project status.
38
# Define: Project Scope Statement
This defines all the requirements for the project, including what’s in and what’s out of scope.
39
# Define: Quality
The specifications and requirements of product or service measured against the standard product or service in the industry. ## Footnote According to the American Society for Quality, this is the degree to which a set of inherent characteristics fulfills quality requirements.
40
# Define: Quality Assurance | (QA)
A management process that defines the quality system or quality policy that a project must adhere to. ## Footnote QA aims to plan quality into the project rather than inspect quality into a deliverable. QA is not something that is done only at the end of the project; it occurs before and during the project as well.
41
# Define: Quality Audit
These are formal reviews of what’s been completed within a project, what worked, and what didn’t work. ## Footnote The result of the audit; is improved performance for the current project, other projects, or the entire organization. Quality audits can be scheduled at key intervals within a project or they can come without warning. The audit process can vary, depending on who is completing the audit: internal auditors or hired third-party experts.
42
# Define: Quality Control | (QC)
An inspection-driven activity, often performed by the project team or professional inspectors and testers, to verify that quality exists within the project deliverables and to keep mistakes from being released to the customers.
43
# Define: Quality Metrics
The operational definitions that specify the measurements within a project and the expected targets for quality and performance.
44
# Define: Quality Planning
The process of first determining which quality standards are relevant to your project and then determining the best methods of adhering to those quality standards.
45
# Define: Refactoring
To adjust working code to improve functionality and conservation. ## Footnote Refactoring clarifies the code and cleans up the shortcuts and quick fixes that can pile up throughout the project. Continuous refactoring is paramount when it comes to creating quality software in Agile.
46
# Define: Root Cause Diagram
A diagram that correlates different factors and the symptom.
47
# Define: Root Cause Identification
Aims to find out why a risk event may be occurring, the causal factors for the risk events, and then, eventually, how the events can be mitigated or eliminated.
48
# Define: Round Robin
A brainstorming approach in which the team forms a circle and each person shares one idea, in order, around the circle. ## Footnote This helps ensure that everyone can contribute and gives everyone a chance to speak and to listen to other ideas.
49
# Define: Rule of Seven
A component of a control chart that illustrates the results of seven measurements on one side of the mean, which is considered “out of control” in the project.
50
# Define: Run Chart
A quality control tool that shows the results of inspection in the order in which they’ve occurred. ## Footnote The goal of a run chart is first to demonstrate the results of a process over time and then to use trend analysis to predict when certain trends may reemerge.
51
# Define: Satisfaction
The feeling of workers when their needs are fulfilled. Known as motivators.
52
# Define: Scatter Diagram
A quality control tool that tracks the relationship between two variables over time. The two variables are considered related the closer they track against a diagonal line. ## Footnote The closer the two variables trend in the diagram, the more likely the two variables are related and affect each other in the process or project.
53
# Define: Seven Basic Quality Tools
These seven tools are used in quality planning and in quality control: cause-and-effect diagrams, flowcharts, check sheets, Pareto diagrams, histograms, control charts, and scatter diagrams.
54
# List: Six-Step Approach to Problem Solving
- Define the problem. - Define the problem’s root cause. - Generate solutions to the problem. - Select the best solution for the problem. - Implement the selected solution. - Test and verify the effectiveness of the selected solution.
55
# Define: Specification Breakdown
This occurs when requirements for the specification are incomplete or conflicting.
56
# Define: Statistical Sampling
A process of choosing a percentage of results at random. ## Footnote For example, a project creating a medical device may have 20 percent of all units randomly selected to check for quality.
57
# Define: Sustainable Pace
A maintainable pace of work that is intense yet steady.
58
# Define: System or Process Flowcharts
Flowcharts that illustrate the flow of a process through a system, such as a project change request through the change control system, or work authorization through a quality control process.
59
# Define: Tree Diagram
Tree diagrams show the hierarchies and decomposition of a solution, an organization, or a project team. ## Footnote The Work Breakdown Structure (WBS) and an organizational chart are examples of tree diagrams.
60
# Define: Trend Analysis
The science of using past results to predict future performance. ## Footnote Based on what’s already happened in the project, the project manager and team can identify trends in schedule and costs to predict what’s likely to happen in the remainder of the project.
61
# Define: Usability Testing
An exploratory test which uses a test subject to understand the usability of software.
62
# Define: Verification
To ensure the product meets requirements and specifications.