Skip to main content

Manage ERP with Success - Blockers of Success

 To manage an ERP process with success is not easy at all. Even there has been processes that have been published by companies, it is mostly depend on the people. In this blog , I am going to share the reasons I see as blockers of during the projects. This is not a scientific measure but just my opinions.


  1. Sales Team: ERP project starts from even before the sales documents are finalized. So company needs (not user/not management etc.) need to be understood wisely and to be checked if the tools can manage these needs and details need to be documented in the contract.
  2. Expectations: Unfortunately, ERP is a software but not a hardware. So expectation management is very important. If it was a hardware, then you will be able to return and to document specific details. 
  3. Project Team: By project team, mostly we understand the consultancy firm but project team does consist of also from customer project managers, users, power users etc. All project team need to be well aware, trained and need to have time for the project. So there is only one personal pronoun in the projects and it is "US". All project team needs to be qualifies on their part.
  4. Force Due to Capabilities or Perfectness: Sometimes consultants may force users due to the system capabilities which doesn't fit the needs of the company or via versa forces users for perfectness of the processes which is too over qualified and can not be managed by the users.
  5. Project Owner: Project owner is the customer company. It is not consultancy firm, it is not the users, it is not the project manager and not the consultants etc.,
  6. Manage Today: Only try to manage what you do or can do today. Do not try to manage in the system you wish to do. 
  7. This is Just a System: This is just a reporting system that helps you decision - making. So setup wisely. It doesn't help you do ERP, if physically you do not.
  8. Project Plan: Be careful when you do the project plan which is specific for each customer. Do not load everything on power users and train users as much as you can.
  9. Support and Track Go -Live: Do not let users drown!
  10. Believe, Enjoy and Celebrate!



And also I would advise to use the documentation of Fast Track Team , "Success by Design"

Labels:

Comments

Post a Comment

Popular posts from this blog

Allocation ways in D365 FO

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...
Post a Comment
Read more

Fast Track Recognized Solution Architect

      You may be a fast track recognized solution architect. Fast track is best practices to succeed on the project.(Called Success by Design) This process is documented by the fast track solution architects. When applied to be a fast track solution architect, evaluation is done by D365 engineering team.      Earning Criteria The architect must be nominated by the partner Must have a minimum of 5 years of experience with Dynamics CRM or ERP products Must have a minimum of 3 years of experience as a solution architect Must be the lead architect on at least 2 FastTrack governed customer implementation projects Must be responsible for the architecture and design of at least 2 FastTrack governed customer implementation projects Even if you can not fill these requirements above, you are still able to read the detailed documentation from the links below to succeed. https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-guide/overview https://www.d3...
Post a Comment
Read more