|
Walter A Shewart developed and used Control Charts and he is sometimes referred to as father of Statistical Quality Control
Phillip B Crosby who originated the zero defects concept was an ASQ Honorary member and past president.
Crosby’s steps to quality improvement are given below.
Make it clear that Management is committed to quality.
Form quality improvement teams with representative from each department like implementation, support, development.
Determine how to measure where current and potential quality problems lie for which ishikawa diagram can be used.
Evaluate the cost of Quality and explain its use to the management.
Raise the quality awareness.
Take formal action identified through previous steps.
Establish a committee for the zero defects program.
Train all employees to actively carry out their part of the quality improvement program.
Encourage individuals to establish improvement goals for themselves and the groups.
encourage employees to communicate to the management the obstacles they face in attaining the improvement goals.
Recognize and appreciate those who participate.
Do it all over again so that the quality improvement propaganda never ends.
The Below Table is a Risk Abatement Plan where we can map the particular organization processes on a scale 1 to 5 and find a counter measure to abate the risk.
|
|
|
|
Six Sigma Risk Abatement Plan |
|
|
|
|
|
Serial Nos |
Potential Risk Element For Process /Product/Service |
Potential Harm Caused by the Risk Element |
Risk element Score 5 being the highest |
Counter Measure(Risk Abatement Plan) |
Risk Owner |
Completion Date for Counter Measure |
|
|
Before |
After |
||||||
|
1 |
Testing Process |
|
|
|
|
|
|
|
2 |
Development Process |
|
|
|
|
|
|
|
3 |
Implementation Process |
|
|
|
|
|
|
|
4 |
Support Process |
|
|
|
|
|
|
Failure Mode and Effect Analysis
Please find the example template of Failure Mode and Effect Analysis Template below by filling this template with respect to the Processes in your Organization you can find the root Cause of the problem.
|
Serial Nos |
Critical Parameter (1) |
Potential Failure Mode (2) |
Potential Failure Affect(3) |
Severity on a scale of 1 to 10 (4) |
Potential Causes (5) |
Occurrence on a scale of 1 to 10 (6) |
|
1 |
Bugs In Software |
Customer Complaints |
|
|
No Proper Standard followed in Coding |
|
FMEA Table Continued……
|
Current Controls (7) |
Detection on a scale of 1 to 10 (8) |
Before RPN(Risk Priority Nos) (9) |
Recommended Action (10) |
Responsibility and target Date and schedule Preparation (11) |
Action taken (12) |
Severity (13) |
Occurrence (14) |
|
|
|
|
|
|
|
|
|
FMEA Contd….
|
Detection(15) |
After RPN (16) |
|
|
|
The Above table is Continuous with 16 Columns and RPN is the Risk Priority Number , in the column 12 after the Action to rectify the problem is taken as mentioned in the Critical Parameter and RPN is a Number which should reduce after the action is taken.
Note :RPN is Calculated By Multiplying Columns 4,6 & 8.
The Author Suresh Menon is a Subject Matter Expert on ERP and has worked in various capacities as Test Manager, ERP Consultant, Principal Consultant and Implementation Manager he can be contacted at testconsultants@outlook.com for comments and queries.
