A couple of weeks ago I presented at Qbit's TestExpo in Manchester. Rare indeed is it for me to go there these days. There was a good turnout, a whole bunch of presenters and me to wrap up the show before the prizes, the bar and the night shift. What would you expect for an audience of testers? Having spent the day gabbing I was sure they'd have to go back to work right after I was done.
These are the slides from the presentation I gave (If you're reading this in an RSS reader such as Google Reader, you're probably not going to be able to see the slides so click on the blog title to get to the page itself and you'll be able to see them. Alternatively, if you really don't want to visit the blog, you can access them at this page on slideshare.net.
The essence of the show was a proposition that too often in programmes, testing is treated as contingency time. Because testing can't start until design and build are broadly completed, the only scope that ever gets cut is that of test. Programmes are generally loath to over-run and, even if they do, it's rarely because more time is needed for testing. So, to get as much in as possible, all the stops come out and long nights and many weekends are worked over and over to try and hit the live date. Inevitably stuff gets missed.
Every so often over the next few weeks I'll pull one of the slides out and post it here as a picture and talk through the things that I said at Qbit - very roughly at least, I have no script (how did Cameron put it? "It'll be a bit of a mess but it will be me"?) so whatever I post will doubtless not match what I said and here, of course, I get more room to be lazy and expand my points.