- Year not given
Pareto charts
Short answer
A Pareto chart is a histogram ordered by frequency of occurrence, showing defects by cause and based on the 80/20 rule: about 80% of problems come from 20% of causes. Construct it by sorting causes descending, drawing bars for frequency and a cumulative percentage line, then focusing on the tallest bars.
What do you mean by pareto charts?
A Pareto chart is a histogram, ordered by frequency of occurrence, that shows how many defects or problems were generated by each identified cause. It is based on the Pareto principle (80/20 rule), named after Vilfredo Pareto and applied to quality by Juran: about 80% of problems come from 20% of causes ("the vital few versus the trivial many"). It is one of the seven basic quality tools.
Construction
- Identify the categories of causes or defects.
- Collect data for a period.
- Count the frequency of each and sort in descending order.
- Calculate percentage and cumulative percentage.
- Draw bars for each category (left axis: frequency), with a line for cumulative % (right axis).
- Focus on the tallest bars.
Example data (software defects)
| Cause | Defects | % | Cumulative % |
|---|---|---|---|
| Requirement errors | 40 | 40 | 40 |
| Coding errors | 30 | 30 | 70 |
| Design errors | 15 | 15 | 85 |
| Interface issues | 10 | 10 | 95 |
| Others | 5 | 5 | 100 |
Count Cum %
40 |## 100%
30 |## ## ___----
20 |## ## ## ---
10 |## ## ## ##
+-----------------------
Req Cod Des Int Oth
Uses
- Prioritise problems and decide where corrective action brings most benefit.
- Focus limited resources on the vital few causes.
- Compare before and after improvement.
- Communicate priorities to management.
Advantages and limits
Simple and visual, but based on past data and shows frequency, not necessarily severity or cost; may need weighting by cost.
Example: In the table, fixing requirement and coding errors would remove 70% of defects.
✓ Answer checked by Claude Opus 5.5 (high effort)
Related questions
- Control charts · ICT Project Management, chapter 10