My Photo

Site Tracker

  • Extreme Tracker
Blog powered by Typepad
Member since 08/2003
Related Posts with Thumbnails

« Flood hits Putrajaya | Main | Wireless Tower »

Friday, August 15, 2003

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

QS in Malaysia are the punching bags whenever Construction Project Managers (CPM) fail to do their "management". From my past experience in private sectors and from what I am doing now, QS are forced to prepare tender documents eventhough we only receive other party's minimal input. We are preparing a document that will decides who gets the job and yet we do not get enough information to satisfy ourselves and from those basic informations we have to make sure that our BQs are perfect. The question is, how do we know what a designer wants if he himself (or she herself) does not know what he/she wants??? And on top of this, our CPMs say "what ever it is the tender must be out immediately". OK... we manage to "create" the info needed and we meet dateline for tender (of course not all are achieved). Then after re reporting our tender evaluation, construction begin. Suddenly my contractor claiming that my BQ does not have this, does not have that, my provisional sums allowed are to small. What the project manager says?.... "Aiyaa.. this QSes ahh.. always like that... never prepare perfect BQs!!!" To make matters worst... drawing issued to the contractor will never be the same with the tender drawings... and yet QS are the guilty party for preparing incomplete documents.
They tend to forget that we "create" the incomplete thing from incomplete supply of what to be done.

This is just an example of how project managements done in Malaysia... we like to cut short our planning just to make sure that the physical works on site start... and almost everytime we only achieve our target on when to start it but seldom achieve the target on when it should finish.

The dump everything on the QS as late as possible syndrome is a symptom of the "pre-contract" process not being managed. If there was any sort of plan (even a on a scrap of paper) at the outset of the process it would be clear, even to an imbecile, that there must be something wrong that the architect takes 12 months, the engineers take 12 weeks and the QS is expected to take 12 hours!!!

The QS get dumped with the responsibility is just another sympton of the same problem. Who is responsible for the project in the "pre-contract" phase? Nobody.

Just my two sen.

Adib

To get an acute accent over the e in cafe, hold down the option key press e, release the option key, press e again. Voilà an é.

Oh I forgot you passed you iBook to your son.

Qsdar,
The QS will never get the BQ right if the project manager(whoever is in-charge) does not do scope defination and scope planning. Scope management is one of the nine knowledge areas in Project Management Book of Knowledge.(Pls refer to www.pmi.org).
Anybody can start a project,but NOT anybody can complete the project on time. The chinese proverb says :

Anybody can open a shop, but NOT anybody can keep the shop open!

Many project managers in construction industry are engineers,architects,QS's BUT are they competent project managers?They are project managers by defaults or by accidents.That is why many projects met with many 'accidents'.

I think project management (PM) in construction is very easy (jangan marah...) compared to PM in software engineering (SE). We can see the building, bridge, road etc. but in SE, we can see "nothing". project manager in construction may be engineer, architect, qs etc. but YET abedib say most of them are unqualified PM. How about PM in SE?. Who do you think the "qualified" PM?

In software development life cycle, I have known a few methodologies but when it comes to managing IT project I have seen none. I think PM be it in IT or Non-IT will be the same. The basic principles are the same, what say you Mr. Adib?

Nona,
I agree with you that the basic principles of project management are the same across the industries.

There are three types of knowledge you need to manage the project:

1.Project Management Knowledge(pls refer to PMBOK:http://www.pmi.org),

2.The general management knowledge,

3.The application area knowledge( ex;construction,IT etc).

Only number 3 differs,the rest are the same.

The comments to this entry are closed.

TypePad Profile

Get updates on my activity. Follow me on my Profile.

Become a Fan

October 2013

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31