Monday, August 08, 2005

The crucial bug elimination stage

The environment have not been as tense as it is now. All the developer in the team are in a mad rush to eliminate bugs. Some are overworked, others have a darkish ring around their eyes. The project leader seems to have her dark hair turn white overnight (i mean from a closer angle). So things are pretty tense here so to say.
As a QA person, it is this kind of mad rush that we have been trained to avoid all the time. Whatever steps that we have implemented, it seems that it is inevitable everytime a need product is to be launched, it always ends up in this kinda tense, sleepless and worrisome environment. Has it been the lack of support from management to foresee this problems causes all this? or is it the capability of the technical team? or is it the uncompromising schedule that the management is pushing the team to commit?
All the questions seems so senseless now as we move on to the last stage of the development cum bug fixing cum regression test cum load test cum..... everything you need to do with the amount of time you have. I am not complaining here, but I am in a battle to improve my company's product. I am thinking of what is the best way to help prevent this situation.
I guess, I have to go back to the beginning of another SDLC and start to push more things to be done, then to leave it to the last minute.

No comments:

Twitting Up and Down

    follow me on Twitter

    The Person Behind this Blog