Quality Flashcards
Used to identify the root causes or contributors to a problem, error, or defect. The problem statement is the effect and the possible contributing factors are the causes. For example, a failure in a system integration test could be due to Improper coding Unskilled coder Inappropriate environment Inappropriate test script Insufficient bandwidth The preceding are just a few examples. And each cause can be further explored for a more elaborate cause-and-effect diagram, also known as a “fishbone” diagram (because when drawn, it looks like a fish) or an “Ishikawa” diagram (named for the person who developed it).
Cause and effect diagram
Can help you see the relationship between the process steps. You can use this information to optimize the process and to see where problems and defects can occur. Useful in process improvement projects or to document any process.
Flowcharts
Used to ensure that a series of steps are followed consistently. Can be used to organize data around a quality problem. For example, you can tally the number of times that a specific cause is the source of a defect, and then use that when creating a histogram or Pareto chart to prioritize quality problems.
Checksheets
A vertical bar chart that creates a graphic display of events (such as causes of defects or types of defects) in descending order. The objective is to rank problems based on the frequency of occurrence to determine the order in which to resolve them.
Pareto diagrams
A vertical bar chart, but a is arranged to show the shape of distribution of an event: for example, the shape of distribution of calls coming into a call center. It can show the spread of results (dispersion) and the median (or mean or mode).
Histograms
A graphic display of process data over time and against established control limits, and that has a centerline that assists in detecting a trend of plotted values toward either control limit.
Control Chart
Shows on a bar graph which factors are more significant
Pareto Chart
Graphs pairs of numerical data, one variable on each axis, to look for a relationship.
Scatter Diagram
conformance to requirements and a fitness for use. It is fulfilling the project scope.
Quality
category or rank given to entities having the same functional use but different technical characteristics
Grade
the process of adding extra features to drive up costs and consume the budget
Gold Plating
prevention-driven process to do the project work right the first time.
Quality Assurance
inspection-driven process to keep mistakes from entering the customers’ hands
Quality Control
the addition of small, undocumented changes that bypass the scope change control system. Sometimes called project poison.
Scope Creep
like a run chart, but it instead tracks the relationship between two variables. The two variables are considered related the closer they track against a diagonal line. Consider the relationship of costs and schedule
Scatter Diagram