I'm in London, ON this week presenting my Agile and Exploratory Testing class. London is a cool place. Today, it was literally cool! One of the things I enjoy doing here is browsing through the used bookstores. For some reason, there are several close to each other in the downtown area.
I forgot to mention in my last post that I had a great Father's day. I visited my dad and my sons and family were with me. All was good. What a blessing.
I was having lunch with a friend and client recently. He told me an interesting story that I want to share. Last August I designed and held a special public course that about 30 people from this one organization attended. There were developers, testers, subject matter experts, plus (most importantly) their managers all in one class for two days.
My friend said that the release they were working on at that time had to go through two cycles of beta testing, each costing about $20,000. The second cycle was due to the extra rework of excessive defects.
Their most recent release had significantly higher quality, which allowed the release to be issued with only one cycle of beta testing - roughly a savings of $20,000 over the last release.
So, I asked my friend, "Do you think the training was part of that improvement." He answered, "I really do. Mainly because the developers and their manager saw the need for better unit testing and learned ways to perform it."
As you look for ways to measure the value of training in software testing, this is an example of one way to do that. Of course, there were other factors. However, I also think the training was a platform to allow the team to do a better job.
I assure you that the savings exceeded the cost of the event!
If you would like to see similar results, contact me. I would love to discuss the possibilities with you.