Friday, June 1, 2007

When a system goes live

Before a system can go live, the user have to confirm that all the request had been fulfilled and no bugs found. That is why we have the user acceptance test, UAT, to have the user to accept what had been developed.

This system that we've developed had gone through the uat for a month, no bugs reported,
no major changes need to be done, no complaints and of cos no comments, no suggestions, no reply from the user. Basically, hear nothing from the user for that whole month. After the uat,
the training comes in place.. training took around 2 weeks, then the system goes live.

The very first day the system goes live, we started to receive tonnes of emails, phone calls from the users complaining this,asking that, y this one not included, y that one is compulsory, why no emails from the system, why this why that.

I also feel like asking them W-H-Y!!! so many weeks of uat & training, none of this had been raised! what does that mean? nobody performed the uat? nobody paying attention to the training? When they're forced to use the system only they asked to change this and change that, won't it be a bit too late? all this will be charged, and the project will be over budget.


so.. who will be the one that suffer?



ME LAR cos i have to make all the changes mar.. :|

No comments: