Article Highlights:
- Human factor (hello we are human)
- Communication Failure (Poor or No Requirements Analysis Documents)
- Unrealistic Development Time frame (We want it and we want it NOW!)
- Poor Design Logic (Didn't think of your requests from a user perspective)
- Last Minute Changes (More often the culprit)
- Lack of Skilled Testing (When a user decides to save money and do their own testing instead of letting the experts do it.)
http://www.softwaretestingtricks.com/2008/12/why-are-bugsdefects-in-software.html
Also read:
Creating quality software products means knowing when to fix bugs and when to leave well alone, writes Eric Sink. There are four questions to ask about every bug. The first two are customer ones, and the next two are developer ones.
http://www.guardian.co.uk/technology/2006/may/25/insideit.guardianweeklytechnologysection
1) How bad is its impact? (Severity)
2) How often does it happen? (Frequency)
3) How much effort is required to fix it? (Cost)
4) What is the risk of fixing it? (Risk)