Are All Bugs Should Be Fixed?
The answer to this question is defiantly NO!!!
All bugs should be managed but not all bugs should be fixed.
Many times when I talk with my customers about the way they develop software I hear the wrong concept of fixing all the bugs before the release.
So why not to fix all the bugs? An application without bugs is not better than an application with bugs?
Well lets start with a very important fact: There are no applications without bugs, there are applications that have unfound bugs.
But we still left with the bugs that we have found why not to fix them all?
Fixing a bug has a cost, it takes developer time, tester time, it will probably create more bugs because of the changes we make in the code so the risk of delaying the delivery of the application on time is high.
So what is the right way of dealing with bugs?
As I mentioned before all bugs should be managed, the result should be a list of bugs that will be fixed based on criterions that are placed before.
What do we do with the bugs that are left open?
The are a few actions left to be taken regarding these bugs:
- Bugs that need to be entered to the known bugs list released with the product.
- Bugs that need to be passed to the support so they will have answers to customers including work arounds.
- Bugs that need to be fixed in later versions.
- Bugs that need to get in to Questions and Answers published to the customers.
These actions are the main actions, this list is not final.
I will give a brief introduction on how to manage bugs in one of my future posts.
Have Fun!!!