Six Basics of Preventing Pain in Your ERP Implementation
"Simplicity is the ultimate sophistication." -Leonardo DaVinci
Over the last decade of being involved with customers and implementation partners for ERP projects, I simply cannot overstate the above sentiment - if you keep everything simple, you make an ERP project smooth and constructive.
Let me explain further. I remember hearing multiple horror stories related to heavy solutions like SAP and Oracle including implementation failures, busted budgets, law suits, and other negativity. It is contrary that the ERP project is aimed at easing organization's way of working ends up being another pain itself.
I don't wish to paint a simplistic picture that the ERP journey is necessarily tough and complex. Things have changed with the advent of more user friendly ERP products like Microsoft Dynamics AX 2012. But even with the best tools, if you are involved in an ERP implementation you can avoid repeating the mistakes of those who walked before you by heeding these important points:
...
Nice article
Raman,
Nice article and thanks for sharing, the points are very clearly defined. Nowadays in the market Implementation partners not are looking at customer requirements and pains deeply, poor documentation and inexperienced consultants which lead to Implementations getting fail.
Microsoft should Initiate every implementation should pass through Microsoft-QA that will improve the Implementations (Make sure all requirements & Deliverables covered) successfully and customer satisfaction.
Nice helpful information. As
Nice helpful information.
As for point 3, I believe its hard to control or ensure that the team will remain as is.