Quality Tools Final
-
Upload
samrat-saha -
Category
Documents
-
view
230 -
download
0
Transcript of Quality Tools Final
-
8/6/2019 Quality Tools Final
1/20
Quality Tools
Pareto Chart
Ishikawa Diagram (FishboneAnalysis)
Team :
Samrat Saha
Akshata AchrekarEdsel Fernandes
Nilofer Khan
Deepak Kamble
Anand Iyer
-
8/6/2019 Quality Tools Final
2/20
Introduction
The Quality needs to be delivered to client to sustain
in Business.
Client wants to see Quality improvement in all thereleases.
Vendor needs to focus on high severity area to
ensure Quality by using the following tool.
Pareto Charts
Ishikawa Diagram
-
8/6/2019 Quality Tools Final
3/20
ScenarioA 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 isdesigned in the phase. This phase deliver High Leveldesign documents.
Phase3 - This is development phase. To deliver the Low level
design document and code. The Phase developerdevelop the code and does unit testing. Fix the unittesting defects and deliver the code to
Quality Control team.
-
8/6/2019 Quality Tools Final
4/20
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 tothe System Testing Team.
System Testing team again retest those defects andclose them or reopen if the defect still exist. SystemTesting will allow the code to be delivered to thenext phase if all the defects are Retested and
closed.This is the internal process of the company which isdeveloping 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 checkset up by client.
-
8/6/2019 Quality Tools Final
5/20
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.
-
8/6/2019 Quality Tools Final
6/20
Steps Towards Quality Checking
Step 1 Track all the defects from Unit testing to Systemtesting 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 toseverity.
Step 5
Prepare the Fish Bone diagram for root
causeanalysis for each cause.
Step 6 Publish the root Cause analysis to the entire team forfuture stand.
-
8/6/2019 Quality Tools Final
7/20
Step 1 & Step 2 Tracking & Making Causal
-
8/6/2019 Quality Tools Final
8/20
Step 3 - Cause-Wise defects per severity
-
8/6/2019 Quality Tools Final
9/20
Step 4 - Pareto charts for All defects
-
8/6/2019 Quality Tools Final
10/20
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
-
8/6/2019 Quality Tools Final
11/20
Step 4 Pareto Charts for Critical & High defects
-
8/6/2019 Quality Tools Final
12/20
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.
-
8/6/2019 Quality Tools Final
13/20
Step 4 Pareto Charts for Medium or Minor defects
-
8/6/2019 Quality Tools Final
14/20
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.
-
8/6/2019 Quality Tools Final
15/20
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
-
8/6/2019 Quality Tools Final
16/20
Ishikawa diagram for Inapplicable/Inappropriate Method/Process
-
8/6/2019 Quality Tools Final
17/20
Ishikawa diagram for Inadequate Self Reviews
-
8/6/2019 Quality Tools Final
18/20
Ishikawa diagram for Inadequate
Environment/Infrastructure
-
8/6/2019 Quality Tools Final
19/20
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 ofeach concerned area.
Next Release onwards these areas can be looked upon in
all the phases.
This helped in improving the Quality by identifying thedefects in earlier stage. Hence reducing the Cost of Poor
Quality.
-
8/6/2019 Quality Tools Final
20/20
thank you