Pareto Analysis Step by Step
Pareto Analysis Step by Step
Pareto Analysis Step by Step
~ By Duncan Haughey
The Pareto Principle has many applications in quality control. It is the basis for
the Pareto diagram, one of the key tools used in total quality control and Six
Sigma.
In PMBOK, Pareto ordering is used to guide corrective action and to help the
project team take steps to fix the problems that are causing the greatest number
of defects first.
Pareto Analysis
Here are eight steps to identifying the principal causes you should focus on,
using Pareto Analysis:
1. Create a vertical bar chart with causes on the x-axis and count (number of
occurrences) on the y-axis.
2. Arrange the bar chart in descending order of cause importance that is, the
cause with the highest count first.
3. Calculate the cumulative count for each cause in descending order.
4. Calculate the cumulative count percentage for each cause in descending
order. Percentage calculation: {Individual Cause Count} / {Total Causes
Count}*100
5. Create a second y-axis with percentages descending in increments of 10
from 100% to 0%.
6. Plot the cumulative count percentage of each cause on the x-axis.
7. Join the points to form a curve.
8. Draw a line at 80% on the y-axis running parallel to the x-axis. Then drop
the line at the point of intersection with the curve on the x-axis. This point
on the x-axis separates the important causes on the left (vital few) from
the less important causes on the right (trivial many).
Fi
gure 1: Pareto Analysis Diagram
Here is a simple example of a Pareto diagram, using sample data showing the
relative frequency of causes for errors on websites. It enables you to see what
20% of cases are causing 80% of the problems and where efforts should be
focussed to achieve the greatest improvement. In this case, we can see that
broken links, spelling errors and missing title tags should be the focus.
The value of the Pareto Principle for a project manager is that it reminds you to
focus on the 20% of things that matter. Of the things you do for your project,
only 20% are crucial. That 20% produces 80% of your results. Identify, and
focus on those things first, but don't entirely ignore the remaining 80% of the
causes.