A Pareto Chart is a special form of a bar graph and is used to display the relative importance of problems or conditions.

A PARETO CHART IS USED FOR:
1.    Focusing on critical issues by ranking them in terms of importance and frequency (example: Which course causes the most difficulty for students? which problem with Product X is most significant to our customers?)
2.    Prioritising problems or causes to efficiently initiate problem solving (example: Which discipline problems should be tackled first? or, What is the most frequent complaint by parents regarding the school? solution of what production problem will improve quality most?)
3.    Analysing problems or causes by different groupings of data (e.g., by program, by teacher, by school building; by machine, by team)
4.    Analysing the before and after impact of changes made in a process (example: What is the most common complaint of parents before and after the new principal was hired? has the initiation of a quality improvement program reduced the number of defectives?)

You would..
Share
Related Documents
  1. Testing Metrics (1764)
  2. Software Feature Priority Matrix (Excel file) (3010)
  3. Testing Metrics: Process, Project, and Product (721)
  4. How to do the estimation in testing? (2881)
  5. Lessons From Software Work Effort Metrics (1364)
  6. Lines Of Code - KLOC - Issues in Estimation (2742)
  7. What is Traceability Matrix? (3157)
  8. Requirement Traceability Matrix (2780)
  9. Test Coverage : How not to miss anything during testing? (1244)
  10. Test Estimation Process (1835)
  11. Testing Effectiveness Assessment (1189)
  12. Systems Engineering Measurement (1140)
  13. Requirements Traceability Matrix (2915)
  14. Requirements Traceability Matrix (2121)
  15. [Free] Risk Matrix : Risk Analyze Tool (Excel) (6183)
  16. Metrics and more metrics (1391)
  17. Software Project Estimation Model (2046)
  18. Test Estimation Techniques (4144)
  19. Software Test Estimation - 9 General Tips on How to Estimate Testing Time Accurately (1889)
  20. Size of software in IFPUG Function Points (1717)