Let me show you why…
Firstly, the customer will explain to you what they want. Most of the time, the customer have something in their mind but when it comes out of their mouth, it would be something else.
Then the Project Leader, who are leading the programming team, would come up with his or her version based on what he or she understood from the customer.
At the same time, the business consultant, with his or her I-know-it-all attitude would brief the team on his or her version of the customer;s requirements.
The analyst, on the other hand, normally does not really give a damn about the other two people and come up with his or her own ideas… Best kan?
The the programmer takes over. Most of the time things just don’t work…
Documentation? What documentation?
When the Operation side takes over and installed the work, it turns out to be something else since most people hate to read instruction properly.
Then after some troubleshooting and debugging was done, the product would be tested and most of the time, it would fail… That’sthe reality of it…
Eventually, the project is completed and the support kicks in… Just look at what has happened…
So, back to the beginning, The Marketing people come up with the product and all promises that it can be made to the customer’s expectation. You know, the sun and the moon stuffs…
Then when the customer got the bill, they would go, “What the hell!”
And what they actually needed was a different thing in the first place…
And the Project Manager get to enjoy all of the above throughout a project…
Fun? You tell me.



2 comments:
customer...customer...
cita-citanya tinggi, tapi omongnya nggak jelas!
kalo x jadi, kecoh pulak.
biasala... heheh
Post a Comment