While attending testing seminars, I noticed that there was a gap in what was being taught. There's a lot of theory presented, a lot of 'why test' classes and a lot of classes on specific techniques--but nothing on a couple of practices that will go a long way towards improving the testing process in a company, specifically, setting up a defect tracking system and enforcing policies and procedures to resolve those defects. Setting up these two things, more than anything else, will put a company on the road to organizing its testing and QA effort. To fill that gap, I've come up with the 'Bug Life Cycle' presentation. While I can't claim it as my own, it is what I've learned over the years as a tester; many of you will find it familiar.
The Bug Life Cycle
[article]
What happens to a bug from start to finish
Summary:
File: