Tuesday, August 23, 2005

Buggit and Test Case Manager

Of all the software that I have come across, the software Buggit and TCM represents some of the older based database type and a typical design on an Access system. Of course it cannot be compared against system running on SQL server and have all those web based functionality. In itself, it is a very good FREE system.

Buggit and TCM is virtually free. What we do need to have is Microsoft Access licenses. It can be installed over a network, meaning the database sits on one PC and the rest of the PCs can act like clients. It is suppose to only support about 5 concurrent users updating, but since my project team is not big anyway, so the system works just nicely and all for FREE. I have had the opportunity to get Mercury team to come in for a presentation and from the sound of it, it will cost us a lot. With what we had I think Buggit and TCM is just as great and serves the same purpose. I look forward to continue using it at this moment of time..

Monday, August 15, 2005

Installation, Training and Standby at D**by Park

It seems funny for me to join my fellow developer to do an installation at D**by Park, near KLCC. What is funnier is that there is 5 of us there. I think we must have frighten the staff and the folks working in D**by Park. It was a wonderful experience for all of us and I thoroughly enjoyed my work there although it was a bit tiring for us.

The first day was on the 10th where I arrived there about 3+ pm. The guys already installed the system. Before I left the office, they have called me numerous times to bring this and that. So, I am travelling with 3 telephone set, a bunch of manuals, some discs and this and that.... My travel there was further hazed with the road seems to be in the middle of some cloud... Everwhere seems clouded with the haze.

Arrived to help up here and there. Do some testing. Watch them do some testing. Show them how things should work, basically learning myself as well as contributing my knowledge.. Went for dinner with the guys... the Naan was crazy... It caused me RM14... phenomenal.. more phenomenal then the haze.

Continued work and before I knew it, it was 1am... went home but was there again the next day... today it was luckier as we had a room to stay in. We used the room phone for testing purpose, but the TV set was so much more entertaining. As it the bathroom. I took the opportunity to bath before I went home that night. It feels great...

I am hoping that the installation is successful. I am hoping everything is smooth. We don't know yet and one of us might go back on Wednesday to check things out. Anyway a good experience and definitely worth going...

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.

Saturday, August 06, 2005

Current Status

Firefighting on the existing products. The company felt that it is time to change the current product and replace it with the newer version. Strong push has been applied by management to have the new products rolled out by certain unreasonable time line.
The possibility of me having to approve unqualified product is my concern right now. The status quo is that we must roll out a product within 10 days of its modules integration. It is totally not something that can be achieved. I managed to get the team to calm down and work towards the dateline, doing our very best.
Sometimes I do wonder whether this is something good for the organization and its people or not. But that is the way Malaysian companies stay competitive. Providing the minimum and expecting the maximum. The programmers having learned all this from the predecessor have also been defensive and doing only minimal or what they are required to. The rest, they just don't want to take the initiative to know and find out.
So being QA in all this environment is certainly challenging. But I believe, with teamwork and proper channel of communication, couple with the implementation of proper processes, things might just change for the better. We'll see until the end of this project what happens....

Wednesday, June 29, 2005

Requirement Specification

Trying to come up with the requirement specification for my organization. It will not be easy and it is a continuous process to come up with something that suits the organization without upsetting or changing too much the current organization.
Wish there is a step by step book that can help me thru, well at least I have not found one so far. Still looking for it though. I know that there is no one book fits all scenario kinda solution but I really gotta kick start this without much time given to me. :(
Well ... what can I say, I'll do my best and see how the result it.... Be positive...

Friday, June 24, 2005

ASQ Training

Next weekend, the ASQ CQM training will be starting. Excited with the possible prospect of meeting up with people of the same field and of the same concern. Of course at the same time, I am quite worried with the development of HMS project. It seems a big concern that our partners and prospective customers feel differently about our product.

I am planning to enforce more stringent rule especially for the group so that the support could be improved. It is inevitable that changes need to be made and made fast. As my boss is still away on business trip. I'll propose to her once she get back.

Thursday, June 23, 2005

The start of the blog...

This is in addition to what I blog on msn space and Y360. MSN space would be dedicated to info on my Christian walk... :) while Y360 would be for something casual and friendly. I guess I am going to use this for work purpose.
Bout work... great... boss not around (well even if she is around, I work as hard anyway)... but it does reduce a certain amount of pressure when she is not actually around. Ermmm doing my work but at a slower pace.
And the rate of the bug finding, I'm really worried about the final product of the version 2. I am keeping my fingers cross that my findings will help them improve sooner then later. In the meantime I will just do whatever I can.
1 more week to the presentation of requirement analysis. I am a bit worried. Never tried that before, it is my first time presenting in this area... a bit worried but excited all the same.
OK, i'll continue to work now...

Twitting Up and Down

    follow me on Twitter

    The Person Behind this Blog