Wednesday, 25 June 2008

My life at work....

I was so busy today...requirement gathering for 4 works orders...QA'ing 3 custom reports...testing a new Candidate Release Version (CRV).....replying e-mails as well as answering calls from customers...

Requirement Gathering is required for any new requested work either custom report or custom plug-in module which will be recorded as Works Orders (WO). Doing this, I need to speak directly to either customer or my Sales Department..this shall be dealt by our sales department though and the next thing you know..you're flooded with so many requirements until you have to take 10 minutes break for couple of cigarettes...thankfully..my manager (who is currently in UK) had gathered all possible requirements required from our Sales Department and then discussed them over the phone...as part of my job..I am required to evaluate and translate them onto a possible and draft output..once agreed..I'll then allocate the WO to the developers..give them a due date..and let them know all customers' requirements as well as agreed output..

QA'ing reports is a stage when developers have completed their work then re-allocate the WO to me which is now being marked as "In QA"..at this stage..I'll need to perform unit/smoke test which is the basic test required to ensure all requirements on custom report work as requested...this unit/smoke test shall and must already be performed by developers...just a double-check at my end..Once this is done..I'll then need to perform scenario test..this would requires me to dig deeper into my brain and think of any possible scenarios that could possibly happen..experience makes a different..If all tests are pass then I'll forward to UK team for another QA at their end....if not..re-allocate to developers..

Testing a Candidate Release Version (CRV) is almost similar to User Accepting Testing and tests that are performed at this stage would also have unit testing as well as scenario testing..the only different is all tests that need doing will be performed at each section, each functionality and each feature...basically, unit and scenario would cover at each of those 3...it would not finish in a day but I'd usually concentrate on doing for section/functionality/features that others would have problem understanding or lack in knowledge..again experience makes a different..

Today..I spoke with an IT guy who called in from Liverpool at one of our customer's site..thankfully his accent was not that strong as an Irish or a Scot..at first the conversation was only about our software but whilst waiting for him to reboot the server as well as other workstations (7 workstations)..he asked where am I..so I said..Malaysia..he was a little shocked and thought I were in UK..he then continued asking a boring question about weather..yeah..a common question when you have nothing to talk about..then Euro 2008 came out..I responded to him and shared my disappointment on regards to the fallen of the Flying Dutch also Portugal teams..he then asked me if I watch English Premier League..I do but (tried to tell him that I'll watch if I want to not because I need/must)...he interrupted asking if I like Liverpool team.. "Sorry mate, am not" that was my line..ha..ha.....he is a fan of Liverpool..I then told him that I like Man U but am not really a fan..then he agreed that Man U is a great club....all crappy talk was stopped when the server was ready..then I continued helping him on setting several stuffs regards to our software... I had several bad experiences answering calls from Scot and Irish people...until today, I am still struggling to really understand their accent..some of them can't really do anything about their accent so I'll have to forward the call to my colleague in UK if I think I can't do any further..let's just take this simple example.."Carer" become "Ceerer"

Today..I have discussed with my manager that I'll need to assign over the training task to my other colleague as she has plenty of time doing that..we decided the new colleague will need to work with her in a month period until further notice..regardless of what shift she's in...hope it will help her because I was so worried last week when I figured she's (the new colleague) still way behind schedule..not to mention her knowledge in our product...I know that it has just been 3 weeks but if she really works hard..am sure 2 weeks would be more than enough....when I joined the company..I had no experienced seniors to share their knowledge or to teach me other than my manager himself which was 6 months senior..I had to work my ass in-out the software to reach my current knowledge status..I even dreamt of my works when I was so worry sometimes..ha.ha....8 hours working hour is not even enough to me anymore to do another training task at this time compared to 3 years ago joining this company..sometimes I had to skip my lunch/dinner due to lot of work loads..since my colleague will do the task I'll have plenty more time to work with the developers..but still I was requested to evaluate her performance by weekly basis by asking/giving her task....

2 comments:

Andrik McVean said...

ops...bos...limpas dulu kio...misti malatups gaji ko nie kan?

Wel^Beiolman said...

malatup?kesian sia ni..keja keras..tp rasa macam kais pagi makan lunch..kasi petang makan dinner...biasa sja ba..cukup makan tuk lelaki bujang..huhu...