This is cool. In one corner it’s Steve McConnell, author of Code Complete and a regular god in the software field. In the second it’s Eric Wise, one of the good bloggers on CodeBetter. Steve says absolutely Yes. Eric said No. Then little-ol’-me link Eric’s post on Steve’s comments and presto – a conversation erupts.
During the management review, we discussed the fact that although there’s extensive testing, critical bugs slip through. One of the PMs, who is a big proponent of exploratory testing, said we’re concentrating too much on writing test procedures, and less on testing. I did actually produce the numbers, thanks to the newly implemented MS Project
No, it’s not over yet, and we are in preparations for the follow-up meeting. We’ve compiled a few more charts, and fixed a few mistakes, and will be ready to show those, as well discuss the topics we haven’t covered last time. We can dig through these numbers a lot, and pull out a lot
I’m finally done with extracting bug information. All projects show a runaway bug train trend. 2 of the teams have ~250 bugs accumulated over the last year, the 3rd has 90. These usually end up as an extra cost to the customer and us, moving on with subsequent releases. And there’s the cost of find-fix-retest