“There’s a myth that if we were really good at programming, there would be no bugs to catch.”

I don’t remember where I read this quote but maybe that’s not important. This is quite interesting since it suggests that it is possible to avoid SQA altogether. Now I can just visualize some manager out there memorizing this quote to shout at their developers. Lets face it, managers want to deliver a product with as less cost as possible, and SQA increases your budget. Can’t blame them for that cause that’s where out salaries and raise comes from. But be sure to consider that this quote still remains a myth.

So where does SQA come in? The size and duration of the project does play a role in deciding how much budget you should allocate for SQA. Management wouldn’t really want to have a SQA team for a project that requires a developer to complete within two or three days; or it maybe just the reason to do so when the project is actually a week long project hurried into three days (sounds familiar doesn’t it).

“Developers are by their nature constructive people. Testing requires that the developer discard preconceived notions of the ‘correctness’ of software just developed and overcome a conflict of interest that occurs when errors are uncovered.”

Now don’t ask me where I read that cause I just don’t remember. I had it written down so that I can tell this to SQA members I hired…and they would give me their blank faces. It’s a pretty cool quote. Even then, testing is only one of the many duties of a SQA team.

So lets talk SQA…Share your knowledge with the intelligent people of Bangladesh.

- Sajjad