|
Share Knowledge

LinkedIn Co
Page
Please visit the site
map to navigate this comprehensive site [Recommended]
OR select the topic from the alphabetical
list
| |
Why limit customization?
-
Once there was a farmer. He was working hard in
his small field. He did lot of worshipping. God appeared and told him to ask a
wish. He always wanted more land so that he can become rich. He told God to
give him bigger piece of land. God said, “At sunrise, start running and make a
circle as big as you can, all the land within the circle will be yours, but at
sunset you should be back to this point where you started, otherwise you lose
everything”. The farmer was very happy and looked forward to the next day
eagerly.
-
Next day, at he sunrise he started running, and by
noon covered lot of ground. He included many fields, which he always wanted.
This field, and that field, and that one far away too, and so on. By afternoon,
he was quite far from the point where he had to return. So he started his
journey back. But, then he saw another large piece of land, and thought why not
cover this too. Just after that he found neighbouring lush green field and now
he became greedy, and thought it is important that I cover this ‘lush green’
field as well, other wise what is the use? So he ran and ran…. Alas, by the
time he came back to the point the sun was already set. God told him that he
will not get anything because he became greedy and did not finish in time.
-
In case of ERP implementation, it is observed that
the ERP coordinator sometimes also becomes greedy and asks for too much
of customization. “I want this also automatic and that also automatic”.
“Include this procedure and that procedure too, other wise what is the use”?
The ERP team also will carry out all those changes to please him. However,
sometime everyone forgets that ERP implementation is a time bound activity
and customization (chopping and changing) should be limited to ‘essential’
changes. The wish list can also be prepared and implemented in a phase manner.
Otherwise the steam runs out, the time and the budget overrun which hampers the
ERP project. The blame game starts, but what is the use, sun is already set……..
-
Moral of the story is that, please be happy and
content with what you have and control the greed and respect the time factor.
ERP implementation is a journey and not a destination. Get the essential
changes done. Use for sometime. In the next phase plan some more changes and
so on…That way the system will also have time to settle. Unlimited
customization may take unlimited time.
.
| |
Related Links

Social Media sites

Blog

FB Page /YourDNS

Facebook Group Discuss Social Media

Join LinkedIn group Digital Platforms Pro

Twitter
@JyotiSocial

Newspaper Social Media
ERP Sites

ERP Blog

FB Page /dnsERP

Facebook
Group Discuss ERP

Join LinkedIn group ERP, E-business Forum

Twitter @followERP

News e-Business Online
|