SAB4#81_Seven Basic Tools of Quality

SAB4#81_Seven Basic Tools of Quality

1. Control charts

   • are a way of visualizing how processes are doing over time.

2. Cause and effect diagrams

   • They are used to figure out what caused a defect. You list all of the categories of the defects that you have identified and then write the possible causes of the defect you are analyzing from each category.

3. Flow charts

   • Let you show how processes work visually.

4. Pareto Charts

   • Help you to figure out which problems need your attention right away. They’re based on the idea that a large number of problems are caused by a small number of causes. In fact, that’s called the 80/20 rule—80% of the defects are usually caused by 20% of the causes.

5. Histograms

   • give you a good idea of how your data breaks down.

6. Checksheets

   • You can use them to organize the test activities you’ll be performing and track whether the product passes or fails tests.

7. Scatter diagrams

   • show how two different types of data relate to each other. If you worked with your test team to create a bunch of new tests, you might use a scatter diagram to see if the new test cases had any impact on the number of defects you found.

8. Quality control measures

   • are all of the results of your inspections: the numbers of defects you’ve found, numbers of tests that passed or failed.

9. Organizational process assets updates

   • You might need to update templates for quality metrics or checklists.
   • Lessons learned updates
     • are where you keep a record of all of the major problems that you solve in the course of your project so that you can use them later.
   • Completed checklists
     • are records of quality activities that are performed through the course of the project and their results.

10. Project Management plan updates

    • You may need to update the Quality Management plan and the Process Improvement plan, which are both subplans of the Project Management plan.

11. Verified deliverables and validated changes

    • Every single deliverable on the project needs to be inspected to make sure it meets your quality standards. If you find defects, the team needs to fix them—and then those repairs need to be checked, to make sure the defects are now gone.

12. Change requests

    • are recommended or preventive actions that also require changes to the way you are doing your project. Those kinds of changes will need to be put through change control, and the appropriate baselines and plans will need to be updated if they are approved.

13. Project document updates

    • You might discover that your company’s quality standards need to be updated.

14. Work performance information

    • might include all of the data your quality processes are producing. Once you’ve looked at the results of your quality tools, you might find places where the processes you’re using to build your product need to be changed.

15. Project Management plan

    • Describes your approach to inspection— what you’ll track and what you’re shooting for.

16. Quality checklists

    • You’ll use checklists to help you remember all of the things you need to include in your deliverables.

17. Deliverables

18. Work performance data

19. Quality metrics

    • Metrics tell what and how you are going to measure your product’s quality. They give you some objective measures to help you make better judgments about it.

20. Organizational process assets

    • Here’s where you’ll find your company’s quality policy, company‑wide metrics, and company‑wide project goals.

21. Project documents

    • This could be process documentation, agreements, or training plans that might impact quality.

22. Approved change requests

Bilder und Dateien der Mindmap