A man named Gerald Weinberg wrote a series of books on Quality Software Management. I highly recommend getting and reading his books if you can get your hands on them. They changed how I see software development. Fundamentally, like all human activities, the activity of programming is a feedback loop. If you take a look at what you are measuring and how those measurements are fed back into the design process, you can figure out what needs to change. If things like those described either your QA team isn't doing what they need to, doesn't exist, or needs to be given guidance on what things to test. One of the quotes in the series is from Lord Kelvin: "What gets measured gets done." Take a look at what is measured and how it is measured and you will start to see what is being done. Unfortunately, I cannot hope to sum up all of the things the author goes over in a post of this size and hope you will investigate them for yourself.

The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully by Gerald M. Weinberg
It has a lot of little anecdotes that help you recall concepts of how to manage your own time. Things like Rudy's law of Rutabaga stick with me even though I haven't picked up the book in a while. I read this book based on someone's recommendation on /. a long time ago, and I am glad I did.

I saw a program a while back interviewing an author about a book called "Crashing Through", where the main character looses his sight when he is very young, and then has it restored to him later in life. The problem was that because his brain had not learned to interpret the signals coming from it, he was unable to get "Normal" vision. From what I remember of the interview, a lot of people who have been in a similar situation get very depressed because they know their vision will never be restored and they are overwhelmed by the amount of new and useless info their brain is receiving.