A Testers Journey

An ounce of practice is better than tons of theory

Why-Why Analysis

This is not post which will say why to do an analysis if at all you are confused with the title :).

I wanted to post this after a discussion with one of my friend regarding bug analysis method followed in his organization.

Let me start it straight..

Kaizen is a Japanese term which means continuous improvements, In this method various techniques are followed like Pareto diagram , fish bone diagram , why why analysis etc.., These techniques help us in narrowing down to the root cause of the issue and find a permanent solution for eliminating the cause.

The step by step approach for the above technique is as follows:

Step-1 : List down all the critical issues faced during the project period.

Step-2 : Analyze which issue topped the chart i.e which issue contributed the major percentage.

These two steps are done using the Pareto diagram.

Step-3 : For that particular issue find out the various possible reasons that could have been a cause for the issue and analyze on every reasons.

Step-4 : Narrow down on the cause of the issue.

The above two steps are done using the fish bone diagram.

Step-5 : Now with the analyzed data , gather your team and draw a why why diagram and there you are with your solution.

Step-6 : Find a permanent fail proof solution for the reason found out.

Step-7 : Document your finding and data analyzed.

This method is popular in manufacturing industries. Interesting to know that this method has also been accepted in the software industry.  This analysis is done every month such that there is some continuous improvement in the process and the number of defects also gets reduced, This is a starting phase for zero defect and attaining 6sigma certification.


September 20, 2009 Posted by | Analysis, bug, Process | | Leave a comment