"Quality Products Doesn't Happen By Accident. It's A Result Of Good Tests And Hard Work"

My Profile

Friday, December 29, 2006

Who Is Responsible For Poor Quality Of Software?

The answer is obvious "Testers". Let them be in any form or in any name like QA, QC, or Tester. They are responsible for poor quality of software. Do you agree with this? I hope you don't agree because the answer is wrong. There may be chances that testers are responsible for poor quality of software but not always. "Obvious answers may not always be the right answer".

Beginning Note:
All the statements and claims made by me in this post are my learning from my experience. I have tried my best to make it informative, meaningful and truthful. I have not intended to hurt anyone by the statements in this post.

My Answer:
I believe that every one associated with the project who did injustice to their work is responsible for poor quality of software. It may be the guys of top management who believe 10 women can give birth to a baby in 1 month. It may be programmers who are aware of the existence of a bug but still they are waiting for a tester to find that bug for fixing it. It may be Testers who just merely tested the product and didn't test with passion.

Top Management:
The roles and responsibilities of top management in a project are very huge. They are responsible for recruiting developers and testers, making schedules and so on. While creating a schedule if any doubt about the completion of project with in timeline arises in their mind then they need to rethink about it and reschedule it. They also need to make sure that they recruited right people as well as right amount of people for the project.

Developers:
I have great respect for developers. There are developers who really work hard and work with passion so that they can develop a quality product. There are developers who respect testers and fix the bugs with real interest. But there also some developers who are aware of the existence of a bug but still they are waiting for a tester to find that bug for fixing it.

Testers:
Before writing anything about testers I recommend you to read Pradeep Soundararajan’s post "Being a tester V/s Working as a tester". In that article Pradeep shares his learning about two kinds of testers.
a) One who is a tester.
b) One who works as a tester.

I fully agree with his learning. And I am simplifying it again.
a) Good Testers
b) Bad Testers
Good testers are testers who have passion and skill for testing.
Bad testers are testers they lack passion for testing and they are on to testing because they want a job.

If a tester from the second category is testing the software then there is lot of chances to miss bugs. And the result may be poor quality of software. In such cases testers are responsible.

Addendum:
I have heard people blaming and cursing Testers for poor quality of software. For such people I have a request "Before cursing or blaming a tester for poor quality of software please think about other factors also”. Because it is not always true that testers are responsible for poor quality of software.

Thanks & Regards
Nishanth Balachandran.

2 comments:

shoukath said...

This is really a fantastic work nishanth.This reflects your passion towards testing.I expect much more views of this kind and share your experiences

Nishanth Balachandran said...

On Shoukath's Comment.

Thanks for the appreciation shoukath. I will try my best to deliver works that match every ones expectations.

Thanks
Nishanth Balachandran