Embedded Files
When managing a project, you want to control the quality of said project so that it is on par with customers expectations. In the 1950's a Japanese quality control expert introduced the Seven Basic Tools of Quality. These tools are commonly used in industries such as manufacturing and healthcare, but can also be used in the Information Technology world to help deliver quality software or hardware implementations. These Seven tools are:
Cause and effect diagram
Control Charts
Checksheet
Scatter Diagram
Histogram
Pareto Chart
Flowcharts
We'll also talk about the Six Sigma, a data-driven methodology for quality controlled with a structure through several phases which are:
Define
Measure
Analyze
Improve
Control
https://www.educba.com/seven-quality-tools/
Here we will go in-depth on each tool used in the Seven Basic Tools of Quality.
A Cause-and-Effect Diagram, also known as a Fishbone Diagram or Ishikawa Diagram, is used to identify the root cause of a problem. It is a graphical representation of the various factors that can contribute to a problem, organized into categories such as People, Process, Equipment, Materials, and Environment. By using a Cause-and-Effect Diagram, quality control personnel can identify the factors that are most likely to contribute to a problem and develop strategies to address them.
A Control Chart is used to monitor a process over time. It helps to determine whether the process is stable or not, and to identify any changes or trends in the process. A Control Chart is used to identify the causes of variation in a process, to determine whether the process is under control or not, and to identify areas for improvement. By using a Control Chart, quality control personnel can identify patterns and trends in data and develop strategies to improve the process.
Check Sheets are used to collect and organize data in a structured manner. They help to identify the frequency and distribution of defects, errors or other issues that need to be addressed. A Check Sheet can be used to gather data from any process, such as the number of defects in a product, the types of customer complaints, or the frequency of machine breakdowns. By using a Check Sheet, quality control personnel can identify patterns and trends that can help them to understand the root cause of a problem.
A Scatter Diagram is used to show the relationship between two variables. It helps to identify the correlation between the two variables and to determine whether there is a cause-and-effect relationship. A Scatter Diagram is used to identify the factors that are most likely to contribute to a problem and to develop strategies to address them.
A Histogram is a graphical representation of a distribution of data. It helps to identify the distribution of defects, errors or other issues in a process. A Histogram is used to identify the variation in a process, to determine whether the process is under control or not, and to identify areas for improvement. By using a Histogram, quality control personnel can identify patterns and trends in data and develop strategies to improve the process.
A Pareto Chart is a bar graph that ranks issues in descending order of frequency or impact. The chart is based on the Pareto principle, also known as the 80/20 rule, which states that 80% of the effects come from 20% of the causes. Pareto Charts are used to prioritize the most important issues or problems and to focus on areas that require the most attention. They help to identify the root cause of problems and to determine the best course of action to address them.
A Flowchart is a graphical representation of a process or workflow. It helps to identify the steps involved in a process, the decision points, and the possible outcomes. A Flowchart is used to understand the current process, to identify areas for improvement, and to develop an improved process. It also helps to identify bottlenecks, redundancies, and inefficiencies in a process.
https://www.visual-paradigm.com/features/quality-control-software/
How could these tools be used in an IT world? Take this example of a software company developing a new mobile app. The software company could use a flowchart to map out the process flow of the mobile app, including all the different steps involved in developing and testing the app. They could also use a check sheet to track the number of defects or errors that are found during testing, including the type of error, the severity, and the frequency of occurrence. The company could also use a Pareto chart to identify the most common types of defects or errors that are found during testing, and to prioritize which issues need to be addressed first. They could then use a histogram to analyze the data collected in the check sheet, and to identify any patterns or trends in the data. They could use a scatter diagram to analyze the relationship between different variables, such as the severity of defects and the frequency of occurrence. They could then use a control chart to monitor the performance of the mobile app during testing, and to identify any instances where the performance falls outside of acceptable limits. Finally, they use a fishbone diagram to identify the root causes of defects or errors that are found during testing, including factors such as coding errors, compatibility issues, or user interface design problems.
What about the specifics for the Six Sigma technique? Let's look at each phase in this technique.
To start with the first phase, define. In this phase, the problem or opportunity for improvement is defined and the goals of the project are established. The scope of the project is defined, and a team is assembled to work on the project. The second phase is measure, in this phase, data is collected on the process to establish a baseline and to determine the extent of the problem. This involves identifying key process inputs and outputs, and collecting data on these variables. The third phase is analyze, where the data is analyzed to identify the root causes of the problem. This involves using statistical methods to identify patterns and trends in the data, and to determine which factors are most important in causing defects or errors. The fourth phase is improve, this is where solutions are developed and tested to eliminate the root causes of the problem. This involves developing and implementing process changes, and testing these changes to ensure they are effective. The fifth and final phase is control, in this phase, the improved process is monitored and maintained to ensure that the improvements are sustained. This involves establishing control measures to ensure that the process remains stable and continues to meet the goals of the project.
https://www.sixsigma-institute.org/What_Is_Six_Sigma.php
How could the Six Sigma technique be used in the IT world? Take a similar example where a software company is experiencing a high number of bugs in their software development process. Here's how they would utilize each phase.
The software company starts by defining the problem as a high rate of defects in their software development process. They establish a project team and set a goal of reducing the number of defects by 50% within six months. The team then measures the problem by collecting data on the software development process to establish a baseline and determine the extent of the problem. They identify key process inputs and outputs, such as code complexity, code review time, and testing time. The team then analyzes the data to identify the root causes of defects. They use statistical methods to identify patterns and trends in the data, and to determine which factors are most important in causing defects. They find that the most common causes of defects are code complexity and code review time. The team then tries to improve from this data by implementing process changes to address the root causes of defects. They use best practices for coding and code review to simplify the code and reduce review time. They also improve their testing process to ensure that defects are caught earlier in the process. Finally, they establish control measures to ensure that the improvements are sustained. They implement a process for monitoring and measuring the software development process to ensure that it remains stable and continues to meet the goals of the project.
Page updated
Report abuse