Quality Tools

ParetoChart
Ishikawa Diagram (Fishbone
Analysis)
Team :
Samrat Saha
Akshata Achrekar
Edsel Fernandes
Nilofer Khan
Deepak Kamble
Anand Iyer
Introduction

 The Quality needs to be delivered to client to sustain

in Business.
 Client wants to see Quality improvement in all the
releases.
 Vendor needs to focus on high severity area to
ensure Quality by using the following tool.
 Pareto Charts

 Ishikawa Diagram
 Scenario
A project needs to be delivered to client with quality as this
project deals is to automate Billing and Collection in the
organization. The project has the following phases.

Phase1 - Gather the requirement from client and finalize

them.

Phase2 - This is design phase. The system flow diagram is

designed in the phase. This phase deliver High Level
design documents.

Phase3 - This is development phase. To deliver the Low level

design document and code. The Phase developer
develop the code and does unit testing. Fix the unit
testing defects and deliver the code to
Quality Control team.
Scenario Contd

Phase4 – This is System Testing phase. Internal System Testing

team (Quality Control Team) does Quality Check and
report the bug into the system to the development
team.
Development team fix them and deliver the New code to
the System Testing Team.
System Testing team again retest those defects and
close them or reopen if the defect still exist. System Testing
will allow the code to be delivered to the next phase if
all the defects are Retested and closed.
This is the internal process of the company which is
developing the project for their client.
Phase5 – This is System Integration Testing which is external
quality check set up by client.
Phase6 – This is User Acceptance Testing which is external quality check
set up by client.
The Challenge
 The challenge for the Organization is to deliver
high quality code to System Integration Testing
Team

 Nil defects should be found of Critical,High &

medium severity.

 This has to be maintained across all releases.

Steps Towards Quality Checking

 Step 1 – Track all the defects from Unit testing to System testing
and Post Delivery defects.
 Step 2 – Perform Causal Analysis after each release with the entire
team.
 Step 3 – Prepare Cause wise defect data per severity (Critical –
Sev1 , High – Sev2 , Medium – Sev3 , Low – Suggestion, Post
Delivery).
 Step 4 – Prepare Pareto charts for all defects according to severity.
 Step 5 – Prepare the Fish Bone diagram for root – cause analysis
for each cause.
 Step 6 – Publish the root Cause analysis to the entire team for
future stand.
Step 1 & Step 2 – Tracking & Making Causal
Step 3 - Cause-Wise defects per severity
Step 4 - Pareto charts for All defects
Focus from the Pareto graph

There are three categories of cause to focus on priority.

 Inapplicable/Inappropriate Method/Process
 Inadequate Self Review
 Inadequate Environment/Infrastructure
Step 4 – Pareto Charts for Critical & High defects
Focus from the Pareto graph

There are two categories of cause for Critical and High

defects to focus on priority.

 Inapplicable/Inappropriate Method/Process
 Inadequate Self Review
Most of the critical and High severity defects appeared
because of these two reasons.
Step 4 – Pareto Charts for Medium or Minor defects
Focus from the Pareto graph

There are one category of cause for Medium or Minor

defects to focus on priority.

 Inadequate Self Review

Most of the Medium or Minor severity defects appeared

because of these one reason.
Step 5 – Preventive Action & Ishikawa Diagram

The Ishikawa Diagram is prepared for the

following Causes.

Inapplicable/Inappropriate Method/Process
Inadequate Self Review
Inadequate Environment/Infrastructure
Ishikawa diagram for “Inapplicable/Inappropriate Method/Process”
Ishikawa diagram for “Inadequate Self Reviews”
Ishikawa diagram for “Inadequate
Environment/Infrastructure”
Conclusion

 Pareto Charts helped vendor to identify the major area

which cause the Critical & High severity defects in the
product.
 Ishikawa diagram helped to identify the root cause of
each concerned area.
 Next Release onwards these areas can be looked upon in
all the phases.
 This helped in improving the Quality by identifying the
defects in earlier stage. Hence reducing the Cost of Poor
Quality.
thank you