Thursday, March 25, 2010

Beta, did you say beta? I say batty!

My company makes software. The software life cycle goes a bit like this : there is the pre-Alpha version, where not all the features are coded and has usually some serious flaws also called bugs. It's the layout stage. Then there is the alpha version. That usually gets tested internally by developers and internal testers. That's in the alpha testing that the big bugs are fixed and the features are all coded. Once the Alpha version has been stabilized, it changes name. Here comes the Beta. The Beta is still not the final product. But to be able to have all features tested in realistic conditions, Betas are tested in live environment by the end users. The betas testers are fully aware the product they are using is not a final version and is still flawed. They are carefully handpicked and they are briefed on what to reasonably expect in case a flaw, however major or minor,  is uncovered.

So I do have a problem when a Beta gets installed and the customer is not prepared, does not have the right kind of support to deal with everything that can ensue. And I have a problem getting this thrown on my lap with no heads up, no preparation and no support system either. It's a bit like being thrown in the arena with a bunch of growling dogs. You can coax them, cajole them all you want, you are still in a tight spot. Did I mention another customer is going to be installed with that same beta version next week? 

So there is my week and probably next week in a nutshell, trying to make the best of the cards I've been dealt. Putting out fires started by someone else. Running ragged. TGTIF !

No comments:

Post a Comment