The document provides information on quality tools and problem solving techniques. It includes examples of various quality control tools including flow charts, check sheets, histograms, Pareto diagrams, cause-and-effect diagrams, and scatter diagrams. Examples are given for how to construct and interpret each of these tools. The tools are presented as methods to identify, analyze, and solve quality-related problems in order to drive continuous improvement.
The document provides information on quality tools and problem solving techniques. It includes examples of tools like flow charts, check sheets, histograms, Pareto diagrams, and cause-and-effect diagrams. Each tool is explained in terms of what it is, when to use it, how to construct it, and its benefits. The document aims to introduce various quality tools that can be used to identify and solve 95% of quality-related problems.
The document discusses the Basic Seven tools of quality including fishbone diagrams, histograms, Pareto analysis, flowcharts, scatter plots, run charts, and control charts. These seven tools were developed by Kaoru Ishikawa to make statistical analysis and quality control more accessible. The tools help identify problems, display data visually, find relationships between variables, and monitor processes for improvements. An example using data from Acme Pizza is provided to demonstrate how the tools can be applied.
This document discusses Extreme Programming (XP), an agile software development methodology. It provides a brief history of agile development and describes XP's goals of lower costs, fewer defects, higher productivity and return on investment. The document outlines XP's values of communication, simplicity, feedback, courage and respect. It then explains several of XP's core practices such as on-site customers, planning games, short releases, stand-up meetings and retrospectives.
Six Sigma is a robust problem-solving method. However, training is often expensive due to time and software requirements.
Over the course of my career, have often had to deliver easy-to-use, how-to, training on the Six Sigma method. These slides teach how to begin, execute and complete a project using key tools, such as CTQ tree, Process Mapping, Measurement System Analysis, Capability, Hypothesis Testing, Design of Experiments, Brainstorming, Control Charts, etc.
Including exercises, this training can be delivered in 3 days; and with some mentorship, close to green belt level performance can be achieved.
thanks for your interest.
The document describes a workshop on lean principles and value stream mapping. It outlines exercises that have participants model a pizza production process in two rounds to understand workflow and identify areas for improvement. In between rounds, participants map the current process, identify value-added and non-value added steps, and design a future state map with experiments to reduce lead times. The final round implements a change from the future state map.
Explanation of the seven basic tools used to solve a variety of quality-related issues. They are suitable for people with little formal training in statistics.
The document provides information on quality tools and problem solving techniques. It includes examples of tools like flow charts, check sheets, histograms, Pareto diagrams, and cause-and-effect diagrams. Each tool is explained in terms of what it is, when to use it, how to construct it, and its benefits. The document aims to introduce various quality tools that can be used to identify and solve 95% of quality-related problems.
The document discusses the Basic Seven tools of quality including fishbone diagrams, histograms, Pareto analysis, flowcharts, scatter plots, run charts, and control charts. These seven tools were developed by Kaoru Ishikawa to make statistical analysis and quality control more accessible. The tools help identify problems, display data visually, find relationships between variables, and monitor processes for improvements. An example using data from Acme Pizza is provided to demonstrate how the tools can be applied.
This document discusses Extreme Programming (XP), an agile software development methodology. It provides a brief history of agile development and describes XP's goals of lower costs, fewer defects, higher productivity and return on investment. The document outlines XP's values of communication, simplicity, feedback, courage and respect. It then explains several of XP's core practices such as on-site customers, planning games, short releases, stand-up meetings and retrospectives.
Six Sigma is a robust problem-solving method. However, training is often expensive due to time and software requirements.
Over the course of my career, have often had to deliver easy-to-use, how-to, training on the Six Sigma method. These slides teach how to begin, execute and complete a project using key tools, such as CTQ tree, Process Mapping, Measurement System Analysis, Capability, Hypothesis Testing, Design of Experiments, Brainstorming, Control Charts, etc.
Including exercises, this training can be delivered in 3 days; and with some mentorship, close to green belt level performance can be achieved.
thanks for your interest.
The document describes a workshop on lean principles and value stream mapping. It outlines exercises that have participants model a pizza production process in two rounds to understand workflow and identify areas for improvement. In between rounds, participants map the current process, identify value-added and non-value added steps, and design a future state map with experiments to reduce lead times. The final round implements a change from the future state map.
Explanation of the seven basic tools used to solve a variety of quality-related issues. They are suitable for people with little formal training in statistics.
The document outlines the control phase tools and activities in a Lean Six Sigma project. It includes reviewing project documentation and metrics, developing standard operating procedures and controls, implementing and monitoring the solution, confirming goals are met, identifying opportunities for replication, and transitioning the project to the process owner. Key steps are developing a control plan to monitor processes and respond to variation, updating failure modes and effects analysis, and communicating project results and benefits.
The document discusses the Business Analysis Body of Knowledge (BABOK) version 3. It provides an overview of the BABOK framework and structure to simplify understanding for the reader. It also discusses learning strategies for BABOK version 3 professional certification, comparing the Certified Business Analysis Professional (CBAP) certification with the ECBA certification. Key concepts from the BABOK such as knowledge areas, tasks, perspectives, and the relationship between business analysis and other domains like IT, enterprise architecture, and business process management are explained.
This document provides an overview of wireframing for designers. It defines wireframes as visual representations of a website's skeletal framework. Wireframes are used early in the design process to plan page layout, functionality, content and user behavior at a low cost before visual design. The document outlines tips for wireframing such as using stencil libraries, pattern libraries and grids. It also provides examples of low and high-fidelity wireframes and prompts designers to create a wireframe for a dog adoption site.
The webinar discusses testing risk management. It defines risks as things that can negatively impact a project's outcomes. There are two types of risks: product risks like bugs that affect stability, and project risks like delays that affect schedule or cost. The presenter advocates that QA managers are well-suited to manage risks due to their end-to-end visibility and balanced perspective between technical and business concerns. Effective risk management involves keeping an up-to-date risk table, reviewing risks regularly, and ensuring meetings focus on mitigation rather than blame.
Kanban is a lean methodology for managing workflow. It utilizes visual cues like kanban boards and cards to limit work-in-progress (WIP) and optimize flow. Key practices include visualizing the workflow, making policies explicit, managing flow, and continuously improving collaboratively through incremental changes. The overall goals are to balance demand with capacity, improve service delivery, and enable evolutionary change.
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
These slides are from the Metrics-Based Process Mapping webinar delivered 09-29-2021.
Companion resources:
• View the recording - https://tkmg.com/webinars/metrics-based-process-mapping-3/
• Buy the book - https://tkmgacademy.com/products/metrics-based-process-mapping/
• Take the TKMG Academy course - https://tkmgacademy.com/courses/metrics-based-process-mapping/
When prioritizing requirements in a project, have you ever been in a situation in which virtually all requirements are High Priority or Critical? As you can imagine, ALL requirements being High priority is as "good" as NO requirements having ANY priority at all. Hmm, not very helpful, isn't it? Is there anything we can do about that?
In this presentation/workshop we'll go through some ideas and practices on how to improve the requirements prioritization process.
Agenda topics:
- Why are we talking about Requirements Prioritization?
- What are we talking about?
- Who cares? Why?
- When do (should) we do it?
- How do we do it? Some useful techniques...
- Pitfalls & "Best" Practices
The workshop goes beyond the knowledge presented in this document, working as team with a faster and better Prioritization Process. The outcomes of that experiment in a future presentation.
The document discusses the 7 main quality control tools: check sheet, cause-and-effect diagram, flow chart, Pareto chart, control chart, scatter diagram, and histogram. It provides details on the purpose and use of each tool, such as using check sheets to collect real-time data, cause-and-effect diagrams to identify causes of problems, and control charts to monitor process variation over time. Overall, the 7 tools help analyze data, identify root causes of issues, measure results, and solve 95% of quality problems through techniques like data collection, visualization of processes and variables, and prioritization of key issues.
Periodic Table of Agile Principles and PracticesJérôme Kehrli
Recently I fell by chance on the Periodic Table of the Elements... Long time no see... Remembering my physics lessons in University, I always loved that table. I remembered spending hours understanding the layout and admiring the beauty of its natural simplicity.
So I had the idea of trying the same layout, not the same approach since both are not comparable, really only the same layout for Agile Principles and Practices.
The result is in this presentation: The Periodic Table of Agile Principles and Practices:
This document discusses technical stories and architecture work in agile software development. It defines technical stories as stories that focus on technical goals rather than user goals. It discusses why technical stories are important for managing technical debt, architecture, and educating the technical team. It provides examples of technical stories and best practices for writing, accepting, and tracking them. The document also discusses architecture, why it is important, and how to plan architecture work through technical stories, architectural runways, and feedback loops.
User Story Mapping for Minimum Lovable Productsuxpin
You'll learn:
How to visualize user needs instead of product features
How to make better decisions when prioritizing a UX backlog
How to align sprints with UX strategy
This document provides information about SIPOC (Supplier, Inputs, Process, Outputs, Customer), a process mapping tool. It defines each element of SIPOC and explains how to create a SIPOC diagram. A SIPOC diagram provides a high-level visual of a process by documenting suppliers, inputs, the process, outputs, and customers. The document also outlines benefits such as identifying strengths, weaknesses and opportunities, and disadvantages such as only depicting high-level processes.
More Information:
https://flevy.com/browse/business-document/six-sigma--statistical-process-control-spc-604
DOCUMENT DESCRIPTION
The Six Sigma - Statistical Process Control (SPC) Training Module includes:
1. MS PowerPoint Presentation including 136 slides covering
- Introduction to Statistical Process Thinking,
- Basic Statistics,
- Introduction to Statistical Process Control,
- Statistical Process Control Charts,
- Sample Size & Frequency,
- Out-of-Control Action Plan, and
- Process Control Plan.
2. MS Excel Confidence Interval Analysis Calculator making it really easy to calculate confidence intervals (mean value, standard deviation, capability indices, proportion, count) and perform a Comparison of two statistics (mean values, standard deviations, proportions, counts).
"After you have downloaded the training material, you can change any part of the training material and remove all logos and references to Operational Excellence Consulting. You can share the material with your colleagues and clients, and re-use it as you need. The only restriction is that you cannot publicly re-distribute, sell, rent or license the material as though it is your own. Thank you."
Got a question about this presentation? Email us at support@flevy.com.
This document provides an overview of quality tools, including 7 new quality control (QC) tools and existing 7 QC tools. It discusses how the tools can help achieve goals like increasing customer satisfaction and reducing claims. The 7 new QC tools - affinity diagram, matrix diagram, arrow diagram, tree diagram, PDPC diagram, matrix data analysis, and interrelation diagram - are designed for quality planning, while existing 7 QC tools like checksheets and control charts are for problem solving. The document gives examples of how to construct and use affinity diagrams and interrelation diagrams to organize ideas, identify root causes, and understand relationships between factors.
Statistical process control (SPC) uses tools like control charts to monitor processes and identify sources of variation. Control charts graphically display process data over time relative to control limits, showing whether the process average and variation are stable and capable of meeting specifications. SPC helps determine if a process is stable and capable over time by identifying trends, cycles, or data points outside control limits that indicate special causes of variation requiring process improvement.
The Product owner is the main stakeholder in any agile software development project. The product owner is one of the four roles (scrum master, agile team, Product Owner & stakeholder) of the scrum framework for agile project management.
Kanban is a scheduling and inventory control system used in lean manufacturing that focuses on limiting work-in-progress. It was developed by Toyota to improve production flow and involves visualizing and limiting work, continuously improving processes, and focusing on smooth workflow. Kanban boards make work visible and help teams collaborate to improve communication, identify issues, and empower self-managed processes.
7 QC Tools For Problem Solving Presentation.pdfOlivierNgono
The document discusses various quality tools used for problem solving and continuous improvement. It begins by explaining why quality is important and introduces 7 fundamental quality tools - flow chart, check sheet, histogram, Pareto diagram, cause and effect diagram, scatter diagram, and control charts. For each tool, it provides a definition, discusses when and how to use the tool, and the benefits. It emphasizes that these 7 tools can solve 95% of quality problems in a factory. The document then dives deeper into each individual tool, providing examples and steps for constructing and interpreting the different charts.
This presentation discusses quality control tools including check sheets, flow charts, histograms, cause and effect diagrams, Pareto charts, scatter diagrams, and control charts. It provides examples and guidelines for when and how to use each tool, as well as their benefits. The seven tools are effective for problem solving, process measurement and continual improvement in quality control.
The document outlines the control phase tools and activities in a Lean Six Sigma project. It includes reviewing project documentation and metrics, developing standard operating procedures and controls, implementing and monitoring the solution, confirming goals are met, identifying opportunities for replication, and transitioning the project to the process owner. Key steps are developing a control plan to monitor processes and respond to variation, updating failure modes and effects analysis, and communicating project results and benefits.
The document discusses the Business Analysis Body of Knowledge (BABOK) version 3. It provides an overview of the BABOK framework and structure to simplify understanding for the reader. It also discusses learning strategies for BABOK version 3 professional certification, comparing the Certified Business Analysis Professional (CBAP) certification with the ECBA certification. Key concepts from the BABOK such as knowledge areas, tasks, perspectives, and the relationship between business analysis and other domains like IT, enterprise architecture, and business process management are explained.
This document provides an overview of wireframing for designers. It defines wireframes as visual representations of a website's skeletal framework. Wireframes are used early in the design process to plan page layout, functionality, content and user behavior at a low cost before visual design. The document outlines tips for wireframing such as using stencil libraries, pattern libraries and grids. It also provides examples of low and high-fidelity wireframes and prompts designers to create a wireframe for a dog adoption site.
The webinar discusses testing risk management. It defines risks as things that can negatively impact a project's outcomes. There are two types of risks: product risks like bugs that affect stability, and project risks like delays that affect schedule or cost. The presenter advocates that QA managers are well-suited to manage risks due to their end-to-end visibility and balanced perspective between technical and business concerns. Effective risk management involves keeping an up-to-date risk table, reviewing risks regularly, and ensuring meetings focus on mitigation rather than blame.
Kanban is a lean methodology for managing workflow. It utilizes visual cues like kanban boards and cards to limit work-in-progress (WIP) and optimize flow. Key practices include visualizing the workflow, making policies explicit, managing flow, and continuously improving collaboratively through incremental changes. The overall goals are to balance demand with capacity, improve service delivery, and enable evolutionary change.
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
These slides are from the Metrics-Based Process Mapping webinar delivered 09-29-2021.
Companion resources:
• View the recording - https://tkmg.com/webinars/metrics-based-process-mapping-3/
• Buy the book - https://tkmgacademy.com/products/metrics-based-process-mapping/
• Take the TKMG Academy course - https://tkmgacademy.com/courses/metrics-based-process-mapping/
When prioritizing requirements in a project, have you ever been in a situation in which virtually all requirements are High Priority or Critical? As you can imagine, ALL requirements being High priority is as "good" as NO requirements having ANY priority at all. Hmm, not very helpful, isn't it? Is there anything we can do about that?
In this presentation/workshop we'll go through some ideas and practices on how to improve the requirements prioritization process.
Agenda topics:
- Why are we talking about Requirements Prioritization?
- What are we talking about?
- Who cares? Why?
- When do (should) we do it?
- How do we do it? Some useful techniques...
- Pitfalls & "Best" Practices
The workshop goes beyond the knowledge presented in this document, working as team with a faster and better Prioritization Process. The outcomes of that experiment in a future presentation.
The document discusses the 7 main quality control tools: check sheet, cause-and-effect diagram, flow chart, Pareto chart, control chart, scatter diagram, and histogram. It provides details on the purpose and use of each tool, such as using check sheets to collect real-time data, cause-and-effect diagrams to identify causes of problems, and control charts to monitor process variation over time. Overall, the 7 tools help analyze data, identify root causes of issues, measure results, and solve 95% of quality problems through techniques like data collection, visualization of processes and variables, and prioritization of key issues.
Periodic Table of Agile Principles and PracticesJérôme Kehrli
Recently I fell by chance on the Periodic Table of the Elements... Long time no see... Remembering my physics lessons in University, I always loved that table. I remembered spending hours understanding the layout and admiring the beauty of its natural simplicity.
So I had the idea of trying the same layout, not the same approach since both are not comparable, really only the same layout for Agile Principles and Practices.
The result is in this presentation: The Periodic Table of Agile Principles and Practices:
This document discusses technical stories and architecture work in agile software development. It defines technical stories as stories that focus on technical goals rather than user goals. It discusses why technical stories are important for managing technical debt, architecture, and educating the technical team. It provides examples of technical stories and best practices for writing, accepting, and tracking them. The document also discusses architecture, why it is important, and how to plan architecture work through technical stories, architectural runways, and feedback loops.
User Story Mapping for Minimum Lovable Productsuxpin
You'll learn:
How to visualize user needs instead of product features
How to make better decisions when prioritizing a UX backlog
How to align sprints with UX strategy
This document provides information about SIPOC (Supplier, Inputs, Process, Outputs, Customer), a process mapping tool. It defines each element of SIPOC and explains how to create a SIPOC diagram. A SIPOC diagram provides a high-level visual of a process by documenting suppliers, inputs, the process, outputs, and customers. The document also outlines benefits such as identifying strengths, weaknesses and opportunities, and disadvantages such as only depicting high-level processes.
More Information:
https://flevy.com/browse/business-document/six-sigma--statistical-process-control-spc-604
DOCUMENT DESCRIPTION
The Six Sigma - Statistical Process Control (SPC) Training Module includes:
1. MS PowerPoint Presentation including 136 slides covering
- Introduction to Statistical Process Thinking,
- Basic Statistics,
- Introduction to Statistical Process Control,
- Statistical Process Control Charts,
- Sample Size & Frequency,
- Out-of-Control Action Plan, and
- Process Control Plan.
2. MS Excel Confidence Interval Analysis Calculator making it really easy to calculate confidence intervals (mean value, standard deviation, capability indices, proportion, count) and perform a Comparison of two statistics (mean values, standard deviations, proportions, counts).
"After you have downloaded the training material, you can change any part of the training material and remove all logos and references to Operational Excellence Consulting. You can share the material with your colleagues and clients, and re-use it as you need. The only restriction is that you cannot publicly re-distribute, sell, rent or license the material as though it is your own. Thank you."
Got a question about this presentation? Email us at support@flevy.com.
This document provides an overview of quality tools, including 7 new quality control (QC) tools and existing 7 QC tools. It discusses how the tools can help achieve goals like increasing customer satisfaction and reducing claims. The 7 new QC tools - affinity diagram, matrix diagram, arrow diagram, tree diagram, PDPC diagram, matrix data analysis, and interrelation diagram - are designed for quality planning, while existing 7 QC tools like checksheets and control charts are for problem solving. The document gives examples of how to construct and use affinity diagrams and interrelation diagrams to organize ideas, identify root causes, and understand relationships between factors.
Statistical process control (SPC) uses tools like control charts to monitor processes and identify sources of variation. Control charts graphically display process data over time relative to control limits, showing whether the process average and variation are stable and capable of meeting specifications. SPC helps determine if a process is stable and capable over time by identifying trends, cycles, or data points outside control limits that indicate special causes of variation requiring process improvement.
The Product owner is the main stakeholder in any agile software development project. The product owner is one of the four roles (scrum master, agile team, Product Owner & stakeholder) of the scrum framework for agile project management.
Kanban is a scheduling and inventory control system used in lean manufacturing that focuses on limiting work-in-progress. It was developed by Toyota to improve production flow and involves visualizing and limiting work, continuously improving processes, and focusing on smooth workflow. Kanban boards make work visible and help teams collaborate to improve communication, identify issues, and empower self-managed processes.
7 QC Tools For Problem Solving Presentation.pdfOlivierNgono
The document discusses various quality tools used for problem solving and continuous improvement. It begins by explaining why quality is important and introduces 7 fundamental quality tools - flow chart, check sheet, histogram, Pareto diagram, cause and effect diagram, scatter diagram, and control charts. For each tool, it provides a definition, discusses when and how to use the tool, and the benefits. It emphasizes that these 7 tools can solve 95% of quality problems in a factory. The document then dives deeper into each individual tool, providing examples and steps for constructing and interpreting the different charts.
This presentation discusses quality control tools including check sheets, flow charts, histograms, cause and effect diagrams, Pareto charts, scatter diagrams, and control charts. It provides examples and guidelines for when and how to use each tool, as well as their benefits. The seven tools are effective for problem solving, process measurement and continual improvement in quality control.
The document discusses various quality control tools used to identify, analyze, and resolve problems in a systematic manner. It describes seven common QC tools: check sheets, histograms, Pareto charts, cause-and-effect diagrams, scatter plots, defect concentration diagrams, and control charts. Each tool is explained along with examples of its use in quality control processes.
Statistical Control Process - Class PresentationMillat Afridi
Statistical process control (SPC) is a method of quality
control which employs statistical methods to monitor and
control a process. This helps to ensure that the process
operates efficiently, producing more specification-conforming products with less waste (rework or scrap).
Tools Use in SPC
Pareto Analysis, Flowcharts, Checklists, Histograms,
Scatter Diagrams, Control Charts, Cause-and-Effect Diagrams
Motorola developed Six Sigma in 1986 to measure defects per million opportunities (DPMO) in its semiconductor manufacturing processes. Six Sigma uses a data-driven, scientific approach called DMAIC (Define, Measure, Analyze, Improve, Control) to reduce variation and improve quality. It aims to reduce defects to 3.4 defects per million opportunities. The DMAIC approach is used to define problems, measure baseline metrics, analyze causes of defects, improve processes by addressing key causes, and control future process performance through statistical process control.
Six Sigma is a data-driven approach to process improvement that aims to reduce defects. It uses statistical methods and the DMAIC framework (Define, Measure, Analyze, Improve, Control) to identify and address root causes of defects. The document provides an overview of Six Sigma, including its goals of reducing costs and improving customer experience. It also describes the five steps of DMAIC and some of the tools used in each step, such as process mapping in Define and data collection/analysis in Measure and Analyze to identify problems and root causes.
TQM-Unit 3-7-1 tools of quality-New.pptxTamilselvan S
This document provides an overview of various quality management tools and techniques, including the seven traditional tools of quality (flow charts, check sheets, histograms, Pareto diagrams, cause-and-effect diagrams, scatter diagrams, and control charts). It describes the purpose, construction, and relationship to the PDCA cycle for each tool. Additionally, it covers concepts of Six Sigma methodology, benchmarking, and failure mode and effects analysis (FMEA).
Quality Improvement Of Fan Manufacturing Industry By Using Basic Seven Tools ...IJERA Editor
This document summarizes a case study conducted at Fecto Fan Company in Gujranwala, Pakistan to address quality issues in their fan manufacturing process. The researcher implemented the basic seven quality tools - flow chart, check sheet, histogram, Pareto chart, cause-and-effect diagram, scatter diagram, and control charts. These tools helped identify the major defects causing 80% of issues, determine their root causes, remove the defects, and ensure the manufacturing process is now under statistical control. Implementing quality tools through the DMAIC methodology improved the process and reduced defects.
7qc_tools_173.ppt for 7 QC tools implementation of the qualityMANISHDUBEY14500
1. The document discusses various quality control tools used to identify, analyze, and resolve problems in a systematic manner. It describes tools like check sheets, histograms, Pareto charts, cause-and-effect diagrams, scatter plots, defect concentration diagrams, and control charts.
2. These 7 QC tools are simple but powerful for solving day-to-day work problems by finding solutions systematically. They are widely used by quality circle members.
3. The document explains each tool in detail - their purpose, how they are constructed and interpreted, and how each can help identify issues, root causes, and ensure process control.
This document provides an overview of Six Sigma, including:
- The basic concepts of Six Sigma and how it is used to drive improvements through reducing variation.
- Key aspects like the DMAIC process and defining critical-to-quality metrics.
- Examples of companies that have implemented Six Sigma successfully, reducing costs significantly through improving quality and processes.
- The different roles involved in Six Sigma projects and challenges that may be encountered.
Production and Quality Tools: The Basic Seven Quality ToolsDr. John V. Padua
This document describes seven basic quality tools: flow charts, Ishikawa diagrams, checklists, Pareto charts, histograms, scattergrams, and control charts. It provides examples and explanations of how each tool can be used to identify problems, collect relevant data, determine causes and effects, and monitor processes to drive quality improvements. Specifically, flow charts map process steps, Ishikawa diagrams identify potential causes of defects, checklists gather data on defect categories, and Pareto charts, histograms, scattergrams, and control charts analyze data for insights. These seven tools can be applied to solve the vast majority of quality issues in an organization.
I wrote this eBook for a software client based on the appropriate persona, available technical materials and interviews with internal subject matter experts. The client used this eBook for their content marketing lead generation campaigns targeted to international manufacturers.
This document provides an overview of a training module on problem solving techniques. It includes definitions of AQC, SQC, and SPC and their differences. It discusses the importance of data and different types of data. Basic statistical concepts like average and standard deviation are introduced. Various tools for problem solving are described such as flow diagrams, brainstorming, graphs, and stratification. Flow diagrams can be used to depict processes and different types include macro, micro, and matrix diagrams. Brainstorming is a technique to generate ideas in a team setting. Different types of graphs like line, bar, pie, belt, compound, and strata graphs are used to represent data visually. Stratification involves separating data into categories to identify problem
This document presents an overview of the seven basic quality tools introduced by Kaoru Ishikawa: flow chart, Pareto diagram, check sheet, control chart, histogram, scatter plot, and cause-and-effect diagram. Each tool is defined and an example is provided of how it can be used. The tools are designed to help average people analyze and interpret data to solve problems and improve processes.
The document provides information on quality control tools, specifically focusing on seven basic tools: check sheet, flow chart, run chart, histogram, Pareto chart, control charts, and scatter diagram. It defines each tool, provides examples of how to construct them using sample data, and explains how to interpret the results. The check sheet, flow chart, histogram and Pareto chart are explained in the most detail, with steps provided on how to create each from raw data through to the final output.
The document discusses the seven basic quality control tools: (1) flow charts visually illustrate process steps; (2) check sheets collect data at its source; (3) histograms graphically show data distribution; (4) Pareto charts identify the most important causes; (5) cause-and-effect diagrams help determine root causes; (6) control charts distinguish common from special causes of variation; and (7) scatter diagrams study relationships between two variables. Examples are provided for each tool to demonstrate how they are constructed and interpreted for quality improvement.
After World War II, Japan adopted quality as an economic strategy and selected seven statistical tools to analyze quality problems and drive continuous improvement. The seven tools - Pareto charts, cause-and-effect diagrams, histograms, control charts, scatter plots, check sheets, and flow charts - can identify up to 95% of issues. Each tool has a specific purpose, such as prioritizing problems with Pareto charts or identifying relationships between variables with scatter plots. Using these tools, Japanese companies were able to dramatically improve quality and economic performance.
Production and Quality Tools: Seven Quality Tools and Introduction to StatisticsDr. John V. Padua
The document discusses the 7 quality tools including flow charts, cause-and-effect diagrams, and Pareto charts. It explains that Kaoru Ishikawa developed the basic 7 tools to make statistical analysis more accessible. Flow charts map out process steps to identify problems and improvements. Cause-and-effect diagrams help determine root causes of issues through a graphical format. Pareto charts follow the 80/20 rule to identify the most important causes of problems based on frequency data. The tools provide visual aids to improve understanding of processes and identify areas for data collection and enhancements.
Similar to 7 QC Tools and Problem Solving Presentation.pdf (20)
Ever been troubled by the blinking sign and didn’t know what to do?
Here’s a handy guide to dashboard symbols so that you’ll never be confused again!
Save them for later and save the trouble!
Implementing ELDs or Electronic Logging Devices is slowly but surely becoming the norm in fleet management. Why? Well, integrating ELDs and associated connected vehicle solutions like fleet tracking devices lets businesses and their in-house fleet managers reap several benefits. Check out the post below to learn more.
Understanding Catalytic Converter Theft:
What is a Catalytic Converter?: Learn about the function of catalytic converters in vehicles and why they are targeted by thieves.
Why are They Stolen?: Discover the valuable metals inside catalytic converters (such as platinum, palladium, and rhodium) that make them attractive to criminals.
Steps to Prevent Catalytic Converter Theft:
Parking Strategies: Tips on where and how to park your vehicle to reduce the risk of theft, such as parking in well-lit areas or secure garages.
Protective Devices: Overview of various anti-theft devices available, including catalytic converter locks, shields, and alarms.
Etching and Marking: The benefits of etching your vehicle’s VIN on the catalytic converter or using a catalytic converter marking kit to make it traceable and less appealing to thieves.
Surveillance and Monitoring: Recommendations for using security cameras and motion-sensor lights to deter thieves.
Statistics and Insights:
Theft Rates by Borough: Analysis of data to determine which borough in NYC experiences the highest rate of catalytic converter thefts.
Recent Trends: Current trends and patterns in catalytic converter thefts to help you stay aware of emerging hotspots and tactics used by thieves.
Benefits of This Presentation:
Awareness: Increase your awareness about catalytic converter theft and its impact on vehicle owners.
Practical Tips: Gain actionable insights and tips to effectively prevent catalytic converter theft.
Local Insights: Understand the specific risks in different NYC boroughs, helping you take targeted preventive measures.
This presentation aims to equip you with the knowledge and tools needed to protect your vehicle from catalytic converter theft, ensuring you are prepared and proactive in safeguarding your property.
EV Charging at MFH Properties by Whitaker JamiesonForth
Whitaker Jamieson, Senior Specialist at Forth, gave this presentation at the Forth Addressing The Challenges of Charging at Multi-Family Housing webinar on June 11, 2024.
Expanding Access to Affordable At-Home EV Charging by Vanessa WarheitForth
Vanessa Warheit, Co-Founder of EV Charging for All, gave this presentation at the Forth Addressing The Challenges of Charging at Multi-Family Housing webinar on June 11, 2024.
What Could Be Behind Your Mercedes Sprinter's Power Loss on Uphill RoadsSprinter Gurus
Unlock the secrets behind your Mercedes Sprinter's uphill power loss with our comprehensive presentation. From fuel filter blockages to turbocharger troubles, we uncover the culprits and empower you to reclaim your vehicle's peak performance. Conquer every ascent with confidence and ensure a thrilling journey every time.
Welcome to ASP Cranes, your trusted partner for crane solutions in Raipur, Chhattisgarh! With years of experience and a commitment to excellence, we offer a comprehensive range of crane services tailored to meet your lifting and material handling needs.
At ASP Cranes, we understand the importance of reliable and efficient crane operations in various industries, from construction and manufacturing to logistics and infrastructure development. That's why we strive to deliver top-notch solutions that enhance productivity, safety, and cost-effectiveness for our clients.
Our services include:
Crane Rental: Whether you need a crawler crane for heavy lifting or a hydraulic crane for versatile operations, we have a diverse fleet of well-maintained cranes available for rent. Our rental options are flexible and can be customized to suit your project requirements.
Crane Sales: Looking to invest in a crane for your business? We offer a wide selection of new and used cranes from leading manufacturers, ensuring you find the perfect equipment to match your needs and budget.
Crane Maintenance and Repair: To ensure optimal performance and safety, regular maintenance and timely repairs are essential for cranes. Our team of skilled technicians provides comprehensive maintenance and repair services to keep your equipment running smoothly and minimize downtime.
Crane Operator Training: Proper training is crucial for safe and efficient crane operation. We offer specialized training programs conducted by certified instructors to equip operators with the skills and knowledge they need to handle cranes effectively.
Custom Solutions: We understand that every project is unique, which is why we offer custom crane solutions tailored to your specific requirements. Whether you need modifications, attachments, or specialized equipment, we can design and implement solutions that meet your needs.
At ASP Cranes, customer satisfaction is our top priority. We are dedicated to delivering reliable, cost-effective, and innovative crane solutions that exceed expectations. Contact us today to learn more about our services and how we can support your project in Raipur, Chhattisgarh, and beyond. Let ASP Cranes be your trusted partner for all your crane needs!
3. 3
Why do we need ‘Quality’ ?
In 1985, Bill Smith, an engineer at Motorola
(Father of Six Sigma) presented a paper which
concluded that …
“If a product was found defective & corrected
during the production process, other defects
were bound to be missed and found later by the
customer during early use of the product….
However, when the product is manufactured
error free, it rarely fails during early use by
the consumer …”
A Quote from Bill Smith ...
4. 4
Problem Solving Technique
Problem Types
Unknown Known
Known
Root Cause
Solution
D
C
B
A
Simple
Problems
Really Worth
Solving &
Challenging
Question of
Implementation
Require High
Level of Tech.
5. 5
Problem Solving Technique
Types of Problem Solvers
Problem
Solving
Type
The
- - -
Type
Some One
Else’s
Fault Type
Self
Negating,
Despairing
Type
7. 7
1. End Users
E.g. Consumer, User, Service
2. Intermediate customers
E.g. Retailer, Distributor, OEM
3. Internal customers
E.g. Manufacturing, In-plant user
Most
useful
Least
useful
Least
heard
Most
heard
Who are Our Customers?
8. 8
Why Do we need Quality Tools?
We need Quality Tools for:
1. Problem solving - making judgments & decisions.
2. For continual improvement.
3. For Process measurement.
“95% of the problem is solved when clearly defined”
9. 9
Problem solving - Methods & Tools
What methods & Tools do we have for Problem Solving?
10. 10
"As much as 95% of Quality related problems in
the factory can be solved with Seven
fundamental quantitative tools."
- Kaoru Ishikawa
Problem solving - Methods & Tools
11. 11
7 QC TOOLS
Q
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts and . . . .
12. 12
FLOW CHART
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
13. 13
FLOW CHARTS
What is a Flow chart ?
“ A diagram that uses graphic symbols to depict
the nature and flow of the steps in a process.”
14. 14
What is a Flow chart ?
Graphical representations of a process.
Sequential flow of processes & sub-process.
Process steps shown with symbolic shapes.
Process flow indicated by arrows & symbols.
FLOW CHARTS
15. 15
When to use Flow Charts ?
To determine how a process currently functions.
To determine how a process could ideally function.
FLOW CHARTS
18. 18
FLOW CHARTS
Start
Draft POD
Type POD
Distribute
End
MACRO MINI MICRO
Start
Get Draft of
POD
Is it
approved?
Proceed
YES
NO
End
Turn on PC
Open word
Program
Are
settings
Ok?
Approval
NO
YES
End Draft
Correct
Distribute
End
19. 19
Real world usage of Flow charts
Production
Manufacturing
To identify critical path
Accounting
Helps visualising money flow
Services
Restaurants
Real estate
FLOW CHARTS
20. 20
Benefits of Flow Charts
Create Visual map of process.
To identify time lags & NVA steps.
Identify process that need improvement.
Determine major & minor inputs in the process.
Promotes process understanding.
Depicts customer - supplier relationship.
FLOW CHARTS
21. 21
FLOW CHART
1. Examples of Flow chart:
• In-house Process Flow chart
• Supplier Process Flow chart
22. 22
CHECK SHEET
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
23. 23
CHECK SHEET
What is a Check sheet ?
A graphical presentation of information.
Data gathering & interpretation tool.
Simplest way to assess common problems.
24. 24
CHECK SHEET
When to use a Check sheet ?
To distinguish between fact & opinion.
To gather data about how often a problem occurs.
To gather data about the type of problem.
25. 25
CHECK SHEET
How to create a Check sheet ?
What is the Problem?
Why should data be collected?
Who will use the information being collected?
Who will collect the data?
30. 30
HISTOGRAM
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
31. 31
What is a Histogram ?
A vertical bar chart that depicts distribution of data.
It is a one time snap shot of a process performance.
A tool to determine the frequency of occurrence of data.
A graphical information communicating tool.
Compares process results with specification limits.
HISTOGRAM
33. 33
When to use a Histogram ?
To summarize large data sets graphically.
To compare measurements to specifications.
To communicate information to the team.
Assist in decision making.
HISTOGRAM
34. 34
HISTOGRAM
Constructing a Histogram
Step 1: Count number of data points
Step 2: Summarize on a tally sheet
Step 3: Compute the range
Step 4: Determine number of intervals
Step 5: Compute interval width
35. 35
HISTOGRAM
Constructing a Histogram
Step 6: Determine interval starting points
Step 7: Count number of parts in Each interval
Step 8: Plot the data
Step 9: Add title and legend
36. 36
BAR WIDTH & BOUNDARY
1. Find the range of the data set I.e., Highest value - lowest.
2. Bar width = Range of data set / number of bars (as / table)
?
43. 43
Benefits of Histogram
To know whether process produces within specification.
To know whether process is stable & predictable.
Process monitoring & centering.
HISTOGRAM
44. 44
HISTOGRAM
1. Learn to construct a Histogram using:
• MS Excel
• Minitab software
2. Exercise on Histogram
48. 48
PARETO DIAGRAM
1
2
3
4
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
49. 49
What is a Pareto Diagram ?
Shows focus area to get most gains.
Bar chart arranged in descending order of height.
Bars on left; relatively important than those in right.
Separates “Vital few” from “Trivial many”.
80 % of trouble comes from 20 % of the problems
Named after Italian Economist Wilfredo Pareto.
PARETO DIAGRAM
50. 50
When to use a Pareto Diagram ?
Starter to Problem solving - What to solve?
To break big problems into smaller problems.
To prioritize high impact issues - Where to focus?
Systematic analysis of causes based on magnitude.
Allows better use of limited resources.
PARETO DIAGRAM
51. 51
PARETO DIAGRAM
Constructing a Pareto Diagram
Step 1: Record the data
Step 2: Order the data
Step 3: Label the vertical axis
Step 4: Label the Horizontal axis
Step 5: Plot the Bars
1
2
3
4
52. 52
PARETO DIAGRAM
Constructing a Pareto Diagram
Step 6: Add up the counts
Step 7: Add a cumulative line
Step 8: Add title, Legend and Date
Step 9: Analyze the Diagram
Step 10: Interpret the results
1
2
3
4
53. 53
Benefits of Pareto Diagram
Identifies ‘Major Few’ problems.
Improves team performance & effectiveness.
Before & After tracking of a problem in single chart.
PARETO DIAGRAM
55. 55
1. Learn to construct a Pareto Diagram using:
• Pareto Excel - Example
• Minitab software
2. Exercise on Pareto Diagram.
PARETO DIAGRAM
56. 56
PARETO ANALYSIS OF INJURIES BY DEPARTMENT
128
102
82 76
20
12
4
54%
74%
92%
96%
99% 100%
30%
0
50
100
150
200
250
300
350
400
MAINTENANCE - 1MAINTENANCE - 2OPEARATIONS - 1OPEARATIONS - 2ADMINISTRATION TRAINING SAFETY
DEPARTMENT
ACCIDENT
IN
NO.
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
PARETO DIAGRAM
57. 57
Accident
No.
Percent
Department
Count
24.1 19.3 17.9 4.7 3.8
Cum % 30.2 54.2 73.6 91.5
128
96.2 100.0
102 82 76 20 16
Percent 30.2
Other
ADM
INISTRATIO
N
OPEARATIO
NS
- 2
OPEARATIO
NS
- 1
M
AINTENANCE
- 2
M
AINTENANCE
- 1
400
300
200
100
0
100
80
60
40
20
0
Pareto Analysis of Injury by Dept.
PARETO DIAGRAM
58. 58
CAUSE & EFFECT DIAGRAM
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
59. 59
What is a Cause & Effect Diagram ?
A graphical tool that helps identify, sort and
display possible causes of a problem or
Quality characteristic.
CAUSE & EFFECT DIAGRAM
60. 60
About Cause & Effect Diagram ?
Developed by Kaoru Ishikawa of Japan.
Also called, Ishikawa or Fish bone diagram.
Used to explore potential & real causes.
Compares relative importance of each cause.
Helps to identify root cause.
CAUSE & EFFECT DIAGRAM
61. 61
When to use a Cause & Effect Diagram ?
During Problem solving to focus on problem.
To sort out interactions among factors for a cause.
To analyze existing problems.
CAUSE & EFFECT DIAGRAM
62. 62
CAUSE & EFFECT DIAGRAM
Why to use Cause & Effect Diagram ?
Helps to determine root cause of a Problem.
Group participation & knowledge sharing.
Indicates possible cause for variation in a process.
Increases knowledge of a process, its factors etc.,
Identifies areas of further data collection.
63. 63
CAUSE & EFFECT DIAGRAM
STEP 1 - Identify & define the effect
Decide on the effect to examine.
Use operational definitions.
Phrase effect and quantify
Positive (an objective) or
Negative (a problem)
64. 64
STEP 2 - Fill in the Effect Box & draw the spline
CAUSE & EFFECT DIAGRAM
POOR
MILEAGE -
5 KMPL
65. 65
STEP 3 - Identify main categories
CAUSE & EFFECT DIAGRAM
POOR
MILEAGE -
5 KMPL
MACHINE
METHOD
PEOPLE MATERIAL
66. 66
STEP 4 - Identify Causes influencing the factors
CAUSE & EFFECT DIAGRAM
POOR
MILEAGE -
5 KMPL
MACHINE
METHOD
PEOPLE MATERIAL
Under inflated
tyres
Use wrong
gears
Carburetor
adjustment
Rash
Driving
Poor
maintenance
Poor
Driving habits
Improper
lubrication
Wrong
fuel
67. 67
STEP 5 - Add detailed levels & Analyze the diagram
CAUSE & EFFECT DIAGRAM
POOR
MILEAGE -
5 KMPL
MACHINE
METHOD
PEOPLE MATERIAL
70. 70
CAUSE & EFFECT DIAGRAM
Benefits of Cause & Effect Diagram
Focus is on ‘Causes’ rather than on ‘Symptoms’
Indicates possible causes of variation.
Improves team performance & effectiveness.
Improves process knowledge.
Encourages group participation.
71. 71
1. Learn to construct a Cause & Effect Diagram using:
• Cause & Effect Diagram Generator
• Minitab software
2. Exercise on Cause & Effect Diagram
CAUSE & EFFECT DIAGRAM
72. 72
Low Income
Society
Personal
Office
Family
Hospital exp
Relativ es
2 Wife
5 C hildren
No scope
Boss
Low pay ment
Low profile job
Pessimistic
No interest
No improv ement
Low education
Take time
C an't accept change
Has bad name
Has bad friends
Cause & Effect Analysis for Low Income - Rs. 2500 P.m
CAUSE & EFFECT DIAGRAM
73. 73
SCATTER DIAGRAM
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
74. 74
SCATTER DIAGRAM
What is a Scatter Diagram ?
A visual & statistical testing tool.
Analyzes strength & relationship between 2 variables.
Involve correlation to establish significant relationship.
Arrive at Quantitative conclusion on relationship.
75. 75
SCATTER DIAGRAM
When to use a Scatter Diagram ?
In problem solving to establish a root cause.
Examine root cause theories in C & E.
To confirm a Hypothesis.
76. 76
SCATTER DIAGRAM
Positive Correlation Negative Correlation No Correlation
Strong positive Correlation Weak negative Correlation
INTERPRETATION OF SCATTER DIAGRAM
78. 78
SCATTER DIAGRAM
SCATTER PLOT STATISTICS:
For scatter plots, the following statistics are calculated:
Mean X and Y Average of all the data points.
Maximum X and Y Maximum value in the series.
Minimum X and Y Minimum value in the series.
Sample Size Number of values in the series.
X Range and Y Range Maximum value - minimum value.
79. 79
SCATTER DIAGRAM
SCATTER PLOT STATISTICS:
X Range and Y Range Maximum value - minimum value.
Stdev of X and Y values Indicates spread of data around the mean. Line
of Best Fit - Slope Slope of the line
Line of Best Fit - Y Intercept Point at which line of best fit crosses Y axis
80. 80
Strong correlation
r-value range of between 0.85 to 1, or -0.85 to -1.
Moderate correlation
r-value ranges from 0.75 to 0.85 or, -0.75 to -0.85.
Weak correlation
r ranges from 0.60 to 0.74 or -0.60 to 0.74.
Though an entirely random relationship equals, 0.00,
r-value that is 0.59 and below is not considered to be a reliable predictor.
(Tan 45 degree = 1)
INTERPRETATION OF SCATTER DIAGRAM
SCATTER DIAGRAM
81. 81
SCATTER DIAGRAM
Benefits of Scatter Diagram
Trends & patterns of different measures are tracked.
Better process management in variable analysis.
Relationship establishment tool.
82. 82
1. Learn to construct a Scatter Diagram using:
• Scatter diagram using MS Excel
• Minitab software
2. Exercise on Scatter Diagram
SCATTER DIAGRAM
83. 83
CONTROL CHARTS
LCL
UCL
X
7 QC TOOLS
The 7 QC Tools;
Flow chart
Check sheet
Histogram
Pareto Diagram
Cause & Effect
Scatter diagram
Control charts
84. 84
CONTROL CHARTS
What is a Control chart ?
Statistical tool for monitoring & improving quality.
Distinguishes between Common & Special cause.
Measure consistency of a machine or process.
LCL
UCL
X
85. 85
CONTROL CHARTS
When to use a Control chart ?
Visual display for Process output.
To monitor, control & improve process performance.
To identify variation at its source.
86. 86
CONTROL CHARTS
Benefits of Control charts
Common visual language to predict process.
Provides cues for taking action.
Easy & simple to maintain.
87. 87
1. Learn to construct a Control Chart using:
• MS Excel
• Minitab software
2. Exercise on Control charts
CONTROL CHARTS
91. 91
STRATIFICATION
What is Stratification ?
A technique used to analyze and divide a universe of
data into homogeneous groups (Strata)
Involves observing data, splitting them into distinct layers
& doing analysis to see a different process.
Often these events, represent multiple sources that need
to be treated separately.
92. 92
STRATIFICATION
How it is carried out ?
It involves looking at process data, splitting it into distinct
layers and doing analysis to possibly see a different
process.
93. 93
Example:
For instance, analysing ‘Quality’ cost.
Prevention cost
Internal Failure cost
External Failure cost
Appraisal cost
World class companies have a Quality cost of around 2
to 5 %
STRATIFICATION
94. 94
When to use Stratification ?
Used extensively to improve
In control process &
Stable process
STRATIFICATION
LCL
UCL
X
Is this
Process ok ?
- How long?
95. 95
Benefits of Stratification
Unknown strands of data can be identified.
Systematic reduction of Common cause variation.
Overall increase in product quality.
STRATIFICATION
1 2
LCL
UCL
X
3
97. 97
What are Graphs & Charts?
A technique used to communicate information visually.
Complicated information is made easy to understand
individually and comparatively using Graphs & Charts.
Basic types include;
1. Bar graph
2. Line graph
3. Pie or Circle graph
GRAPHS & CHARTS
98. 98
1. Learn to construct Graphs & Charts using:
• MS Excel worksheet
2. Exercise on Graphs & Charts
GRAPHS & CHARTS
101. 101
What is Brainstorming?
A tool used by teams for creative exploration of options in
an environment of free criticism.
Provides creative and unrestricted exploration of options
or solutions.
BRAINSTORMING
107. 107
Check Sheet
Pareto Chart
•
•
•
•
•
A B C D E Other
20
40
60
80 100%
50%
75%
25%
Histogram
Control Chart
Flow
Chart
START
PROCESS
STEPS
DECISION
STOP
IS IS NOT
WHAT?
WHO?
WHERE?
WHEN?
HOW MUCH?
Is/Is Not Analysis
Capability Study
DEFINING THE PROBLEM
108. 108
NGT
Total
A 1 3 1 1 6
B 3 4 4 2 13
C 2 1 3 3 9
D 4 2 2 4 12
The Nominal Group Technique [NGT] provides a
way to give everyone in the group an equal voice in
problem selection.
Brainstorming
te many ideas in as short a time as possible.
nstorming can be used in two ways: structured or
tructured.
Operational
Definitions
Operational definitions give a clear communica
meaning to a concept which enables individua
work on a system based on basic guides of
understanding. There are no gray areas.
R
a
w
D
a
t
a
A
B
C
D
O
t
h
e
r
1
0
0
%
7
5
%
5
0
%
2
5
%
P
a
r
e
t
o
C
h
a
r
t
A
P
a
r
e
t
o
C
h
a
r
t
i
s
a
s
p
e
c
i
a
l
f
o
r
m
o
f
v
e
r
t
i
c
a
l
b
a
r
g
r
a
p
h
t
h
a
t
h
e
l
p
s
y
o
u
t
o
d
e
t
e
r
m
i
n
e
w
h
i
c
h
p
r
o
b
l
e
m
s
t
o
s
o
l
v
e
i
n
w
h
a
t
o
r
d
e
r
.
D
o
i
n
g
a
P
a
r
e
t
o
C
h
a
r
t
b
a
s
e
d
o
n
e
i
t
h
e
r
a
C
h
e
c
k
L
i
s
t
o
r
o
t
h
e
r
f
o
r
m
s
o
f
d
a
t
a
c
o
l
l
e
c
t
i
o
n
h
e
l
p
s
d
i
r
e
c
t
a
t
t
e
n
t
i
o
n
a
n
d
e
f
f
o
r
t
s
t
o
t
h
e
t
r
u
l
y
i
m
p
o
r
t
a
n
t
p
r
o
b
l
e
m
s
.
*
*
Y
o
u
w
i
l
l
g
e
n
e
r
a
l
l
y
g
a
i
n
m
o
r
e
b
y
w
o
r
k
i
n
g
o
n
t
h
e
t
a
l
l
e
s
t
b
a
r
t
h
a
n
t
a
c
k
l
i
n
g
t
h
e
s
m
a
l
l
e
r
b
a
r
s
.
P
a
r
e
t
o
C
h
a
r
t
CAUSE & EFFECT DIAGRAM [FISHBONE]
A Cause & Effect Diagram is used when you need to
identify, explore, and display the possible causes of a
specific problem or condition. “Fishboning”
represents a sophisticated form of brainstorming.
EFFECT
Cause Cause
Cause Cause
Cause
A Problem Statement is tool used
to document a Probletunity.
Problem
Statement
A Problem Statement is
divided into three parts: the
current situation or existing
state of the problem, the
impact the problem has on
the organization, and the
desired state one would like
to achieve by solving the
problem or improving the
process.
Define the Team
Team Members
Name Role
John Team Leader
Mary Coach
Bob Teacher
Susan Custodian
Bill Secretary
Jane Driver
Wayne Student
Purpose & Vision
Average
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Upper Control Limit [UCL]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Lower Control Limit [LCL]
CONTROL CHART
Time
Measurement
A Control Chart is simply a Run Chart with statistically
determined upper and lower control limit lines drawn on
either side of the process average. Being in control
[meaning no data points fall outside the control limits]
simply means the process is consistent.
Average
RUN CHART
Time
Measurement
A Run Chart is used to monitor a process to see
whether or not the long-range average is
changing.
Run Charts are the simplest quality tool to
construct and use.
Restraining
Forces
Driving
Forces
Force Field Analysis is
a visual listing of possible
forces driving or
preventing change.
A Force Field Analysis is
useful if a quality
improvement team wants
to find out what is
driving, slowing, or not
allowing change at all.
Hint: removing a
restraining force will
make for more progress
than creating driving
forces.
FORCE FIELD ANALYSIS
INTERRELATIONSHIP
Cause
Cause Cause
Cause
Cause
Cause
study the relationship between the causes
and discover the “root cause” of a problem.
INTERRELATIONSHIP
Cause
Cause Cause
Cause
Cause
Cause
If a relationship can be
established, lines are
drawn between two
causes. Analysis leads to
drawing arrows between
causes and effects.
HECKLISTS or sheets are simple easy-to-understand
orms used to determine whether and with what
equency specified events are taking place. Check lists
upply the necessary data for creating Run Charts and
ther continuous improvement tools.
CHECKLIST
Date Total
Category 1 Data Data
Category 2 Data Data
Category 3 Data Data
Category 4 Data Data
Decision
Process
Step
Stop
Start
FLOWCHART
A Flowchart is a pictorial
representation showing all
of the steps of a process.
Flowcharts are used to
“document” a process. By
creating and studying
flowcharts teams can often
uncover sources of trouble
as well as solutions to
problems. Many of us are
visual learners. “Let’s
flowchart it” is a most
important step in problem
solving.
The Plan-Do-Study-Act [PDSA] Cycle
The Plan-Do-Study-Act [PDSA] Cycle
Plan
Plan
Do
Do
Act
Act
Study
Study
Delighted
Customers
Systems Progress
Systems Progress is a visual technique used
to answer the questions: “Where did we start?
Where are we now? Where are we going?
Pilot Project
Pilot Projects provide evidence that proposed
innovations or improvements will work. Pilot
Projects are the “DO” of the Plan-Do-Study-Act
[PDSA] Cycle.
Five Whys?
The Five Whys? are simply a process of
asking Why? at least five times in a row
to detect the root cause or meaning of a
particular problem or situation.
Why? Why?
Why? Why?
Why?
BAR CHART
Category
Survey Results In Percent
A Bar Chart displays collected data on
parallel horizontal bars for comparative
analysis. Lengths are proportional to
collected data.
COLUMN CHART
Category
Number
A Column Chart is a vertical bar graph
that displays collected data in parallel
columns whose lengths are proportional to
specific amounts in sets of data.
SURVEY
1. xxxxxxxxxx
2. xxxxxxxxxx
3. xxxxxxxxxx
determining
quality.
Compile the results
using a Checklist
and display them
using a Bar Chart,
Column Chart, or
Pareto Chart.
Surveys are used when a project is
planned, to prove the need and demand of
the customer, or to test a group for
Project Bulletin Board
RED ITEMS REQUIRE ACTION WITHIN 30 DAYS.
1.
2.
3.
1.
2.
3.
YELLOW ITEMS ARE SCHEDULED TO MOVE INTO RED.
1.
2.
3.
GREEN ITEMS CAPTURE ALL IMPROVEMENT SUGGESTIONS.
Completed Items move to the
Successful Projects Board.
Items must be organized into segments
capable of being addressed within 30 days.
Items move into yellow as space permits.
P RIOR K NO WLED GE ASS ESSMEN T Hig h Sc ho ol Cu s tod ia l QIP Surve y
0
1
2
3
4
U nd e rs to o d th e 2 -Jo b C on c ep t p rio r to
train in g.
U nd e rs to o d th e 8 5- 15 Ru le p rio r to
train in g.
Un de rst oo d t he i de a o f " C us to m e r-Dr iven
Q u alit y " p rio r to train in g.
Un d ers to od t h at I a m a c u st om er t oo pr ior
to train in g.
S erie s1
Radar Chart illustrates relationships
tween characteristics of plotted data
ints in relation to the whole picture.
dar Charts can give a second
erpretation to the same set of data in
Bar or Column Chart.
CORRELATION CHART
Factor 2
Factor
1
A Correlation Chart measures the performance
of one factor compared to another and helps
determine what relationship. if any, exists. The
correlation is based on the pattern of data points.
Negative
Correlation
Positive
Correlation
No Correlation
100 %
90 %
80 %
70 %
ETC.
Consensogram
A Consensogram is a statistical survey that measures
an entire groups perception of effort, commitment,
understanding, etc. The question asked is decided by
the leader, group, team, or organization. The
Consensogram is used when you have a group of people
and wish to see their view on an issue.
Pie Chart
A Pie Chart is used to display data which is
represented by a circle [100 percent] and is
then broken down into slices.
The Pie Chart
shows the most
important problem
areas by giving
them a larger piece
of the pie. Pie
Charts are easy to
read and are
effective with all
age groups.
Scores
Frequency
HISTOGRAM
A Histogram is a specialized Column Graph used
to illustrate the stability of a process. The
greatest number of units are pictured at the mid
point with roughly an equal number of units on
either side of that point. See the example below.
Process A
Process B
Process A illustrates greater
variation than Process B.
Process C illustrates even less
variation than Process B.
Process C
Stratification helps analyze cases in which data
may actually mask the real facts.
This is often the case when the recorded data is
from many sources but is treated as one number.
Stratification breaks down single numbers into
meaningful categories to focus corrective action.
Time
Measurement
Time
Measurement
A and B
Combined A Alone
B Alone
Stratification
A and B Combined
Imagineering
Imagineering is a Brainstorming technique used
to identify what an individual or group envisions as
the perfect project, process, or system. Another
term used for Imagineering is idealized design.
The facilitator or leader
must clearly state the
objective of the
Imagineering session.
Example:
“What would be the perfect
learning environment?”
Flow Tree
A Flow Tree helps to break down
outcomes into major subcategories or
capacities. It is an integral part of a
Capacity Matrix [See].
Capacity Matrix
Knowledge
Understanding
Application
Analysis
Aim or Capacity Breakdown
Result
Parking
Lot
? I/O
+
What is going well?
A Parking Lot is a place where group
participants can anonymously communicate
with facilitators or group leaders.
.
What needs improvement
What question do you have?
What are the issues or observations.
Affinity Diagram
The Affinity Diagram is the result of an interactive
data collection method which allows groups of people
to identify and process large quantities of ideas in a
very short time. It is a non-judgmental way to collect
and process ideas. A question is posed. Team
members individually Brainstorm silently writing ideas
on 3”x3” sticky
notes.
Team members
randomly place
them in the middle
of the table.
Ideas are grouped
into like categories.
Finally, a header
note is placed at
the top of each
column.
PROJECT
STEPS
1.
2.
3.
4.
5.
Time
Ganntt Chart
A Ganntt Chart is used for planning schedules and
managing projects. A Ganntt Chart is useful when doing a
project where one stage depends upon another. It also
makes it obvious which steps can be done simultaneously.
Present Organization
1.
2.
3.
4.
Future Organization
1.
2.
3.
4.
Positive Forces That Create Growth
1.
2.
3.
4.
5.
6.
Negative Forces That Create Growth
1.
2.
3.
4.
5.
6.
+
-
TransitionPeriod
Quality of W
orkLife
A Bone Diagram is a systems reflection tool, which helps
organizations clarify their current and desired state. It also
identifies the forces driving and preventing progress toward the
desired change. It combines the Systems Progress and Force
Field Analysis Tools.
Quality Improvement Story Board
2.a. Identify the team members who will
address the issue.
b. Establish operational definitions to be used.
1. Describe the OFI identified in the
Baldrige Assessment.
3. Collect data regarding the
current situation.
5. Develop a plan for improvement and
how success will be measured.
6. Report results.
4. Identify causes for the current
situation.
ACTION PLAN
Action Plan refers to a series of connected steps that
are designed to accomplish a goal or objective. Action
plans include details of shorter- and longer-term
performance projections, responsible personnel, resource
commitments and time horizons for accomplishment.
Action plan development represents the critical stage
in planning when
strategic
objectives and
goals are made
specific so that
effective
organization-wide
understanding and
deployment are
possible.
STRATEGIC PLAN
The Strategic Plan refers to all aspects of organization
level planning and the deployment of action plans. This
includes primarily the development and deployment of
an organizational mission, key measures of mission
fulfillment, and strategies that take into account key
student and stakeholder requirements. Strategic
Planning has a
results-oriented
focus and seeks to
align all daily work
within the
organization with
the over-all
organizational
direction.
A Quality Tool Belt
109. 109
Quality Improvement Story Board
2.a. Identify the team members who will
address the issue.
b. Establish operational definitions to be used.
1. Describe the OFI identified in
the Baldrige Assessment.*
*Use BOTH the Building Bullet Book and the Baldrige
Feedback Report along with the annual Baldrige Survey Results
to identify OFIs.
3. Collect data regarding the
current situation. Use any or all of
the following:
5. Develop a plan for improvement and
how success will be measured.
6. Report results.
and/or
4. Identify causes for the current
situation.
and/or
Imagineering
Imagineering is a Brainstorming technique used
to identify what an individual or group envisions as
the perfect project, process, or system. Another
term used for Imagineering is idealized design.
The facilitator or leader
must clearly state the
objective of the
Imagineering session.
Example:
“What would be the perfect
learning environment?”
Define the Team
Team Members
Name Role
John Team Leader
Mary Coach
Bob Teacher
Susan Custodian
Bill Secretary
Jane Driver
Wayne Student
Operational
Definitions
Operational definitions give a clear communicable
meaning to a concept which enables individuals to
work on a system based on basic guides of
understanding. There are no gray areas.
A Problem Statement is tool used
to document a Probletunity.
Problem
Statement
A Problem Statement is
divided into three parts: the
current situation or existing
state of the problem, the
impact the problem has on
the organization, and the
desired state one would like
to achieve by solving the
problem or improving the
process.
SURVEY
1. xxxxxxxxxx
2. xxxxxxxxxx
3. xxxxxxxxxx
determining
quality.
Compile the results
using a Checklist
and display them
using a Bar Chart,
Column Chart, or
Pareto Chart.
Surveys are used when a project is
planned, to prove the need and demand of
the customer, or to test a group for
Affinity Diagram
The Affinity Diagram is the result of an interactive
data collection method which allows groups of people
to identify and process large quantities of ideas in a
very short time. It is a non-judgmental way to collect
and process ideas. A question is posed. Team
members individually Brainstorm silently writing ideas
on 3”x3” sticky
notes.
Team members
randomly place
them in the middle
of the table.
Ideas are grouped
into like categories.
Finally, a header
note is placed at
the top of each
column.
CAUSE & EFFECT DIAGRAM [FISHBONE]
A Cause & Effect Diagram is used when you need to
identify, explore, and display the possible causes of a
specific problem or condition. “Fishboning”
represents a sophisticated form of brainstorming.
EFFECT
Cause Cause
Cause Cause
Cause
Pilot Project
Pilot Projects provide evidence that proposed
innovations or improvements will work. Pilot
Projects are the “DO” of the Plan-Do-Study-Act
[PDSA] Cycle.
NGT
Total
A 1 3 1 1 6
B 3 4 4 2 13
C 2 1 3 3 9
D 4 2 2 4 12
The Nominal Group Technique [NGT] provides a
way to give everyone in the group an equal voice in
problem selection.
Average
RUN CHART
Time
Measurement
A Run Chart is used to monitor a process to see
whether or not the long-range average is
changing.
Run Charts are the simplest quality tool to
construct and use.
BAR CHART
Category
Survey Results In Percent
A Bar Chart displays collected data on
parallel horizontal bars for comparative
analysis. Lengths are proportional to
collected data.
CHECKLISTS or sheets are simple easy-to-understand
forms used to determine whether and with what
frequency specified events are taking place. Check lists
supply the necessary data for creating Run Charts and
other continuous improvement tools.
CHECKLIST
Date Total
Category 1 Data Data
Category 2 Data Data
Category 3 Data Data
Category 4 Data Data
Average
RUN CHART
Time
Measurement
A Run Chart is used to monitor a process to see
whether or not the long-range average is
changing.
Run Charts are the simplest quality tool to
construct and use.
BAR CHART
Category
Survey Results In Percent
A Bar Chart displays collected data on
parallel horizontal bars for comparative
analysis. Lengths are proportional to
collected data.
ACTION PLAN
Action Plan refers to a series of connected steps that
are designed to accomplish a goal or objective. Action
plans include details of shorter- and longer-term
performance projections, responsible personnel, resource
commitments and time horizons for accomplishment.
Action plan development represents the critical stage
in planning when
strategic
objectives and
goals are made
specific so that
effective
organization-wide
understanding and
deployment are
possible.
STRATEGIC PLAN
The Strategic Plan refers to all aspects of organization
level planning and the deployment of action plans. This
includes primarily the development and deployment of
an organizational mission, key measures of mission
fulfillment, and strategies that take into account key
student and stakeholder requirements. Strategic
Planning has a
results-oriented
focus and seeks to
align all daily work
within the
organization with
the over-all
organizational
direction.
Restraining
Forces
Driving
Forces
Force Field Analysis is
a visual listing of possible
forces driving or
preventing change.
A Force Field Analysis is
useful if a quality
improvement team wants
to find out what is
driving, slowing, or not
allowing change at all.
Hint: removing a
restraining force will
make for more progress
than creating driving
forces.
FORCE FIELD ANALYSIS
Brainstorming
Brainstorming is a procedure that allows a group to
express problem areas, ideas, solutions, or needs. It
allows each participant to state their opinion in a non-
threatening environment. Brainstorming helps a group
create many ideas in as short a time as possible.
Brainstorming can be used in two ways: structured or
unstructured.
110. 110
Define Measure Analyse
⚫ Identify Potential x’s
⚫ Analyse x’s
⚫ Select Critical x’s
Phase Review
Run 1 2 3 4 5 6 7
1 1 1 1 1 1 1 1
2 1 1 1 2 2 2 2
3 1 2 2 1 1 2 2
4 1 2 2 2 2 1 1
5 2 1 2 1 2 1 2
6 2 1 2 2 1 2 1
7 2 2 1 1 2 2 1
8 2 2 1 2 1 1 2
Effect
C1 C2
C4
C3
C6
C5
x
x
x
x
x
x
x
x
x
x
x
⚫ Select Project
⚫ Define Project
Objective
⚫ Form the Team
⚫ Map the Process
⚫ Identify Customer
Requirements
⚫ Identify Priorities
⚫ Update Project File
Phase Review
⚫ Define Measures (y’s)
⚫ Evaluate Measurement
System
⚫ Determine Process
Stability
⚫ Determine Process
Capability
⚫ Set Targets for
Measures
15 20 25 30 35
LSL USL
Phase Review
THE IMPROVEMENT CYCLE
111. 111
Improve Control
⚫ Control Critical x’s
⚫ Monitor y’s
⚫ Validate Control
Plan
⚫ Close Project
1 5 10 15 20
10.2
10.0
9.8
9.6
Upper Control Limit
Lower Control Limit
y
Phase Review
⚫ Characterise x’s
⚫ Optimise x’s
⚫ Set Tolerances for x’s
⚫ Verify Improvement
15 20 25 30 35
LSL USL
Phase Review
y=f(x1,x2,..)
y
x
. . .
. . .
. .
. . .
. . .
THE IMPROVEMENT CYCLE
Q
112. 112
1. Define the Problem
2. Interim Actions
3. Acquire and Analyse Data
4. Determine Root Cause
5. Evaluate Possible Solutions
6. Action Plan and Implement
7. Verify the Results
8. Standardise and Future Actions
Team Problem
Solving Process
PDCA LOOP IN ACTION
114. 114
SUMMARY
The tools listed above are ideally utilized in reducing the process
variability or identifying specific problems in the process. In any
case, the tools should be utilized to ensure that all attempts at
process improvement include:
• Analysis
• Improvement
• Monitoring
• Implementation