The duration of the ERP project: calm, and good handwriting

Very nice! Once and for all you have decided to implement the ERP that will improve the management of your business. It will be a big change. What do you want it now? For the cart.
The time spent on a project can vary greatly from one month to two years. This difference in periods is since each client needs specific characteristics and depending on the size of their company or project, it will take longer. Thus, the adaptation and customization of the implementation to each of the users must be taken into account.

Between one month and two years

It is true that we must dedicate the necessary time to each implementation plan, and that this can be extended because they depend on a vital variable: the client. Even so, a project that takes more than two years to start… It’s not a good project. During these two years, the technological situation may have undergone many changes. In this way, all the work done previously can be outdated due to the great speed of technological evolution.  

The inseparable duo: time and methodology

The methodology chosen and used to carry out a project has a close relationship with the time spent on the project. Thus, there are some methods that allow a start in a short period of time, and others that, although they extend more, are more effective. There is everything, and for everyone.

In the case of Dynamics 365bc, we opted for the spiral implementation methodology, which we already discussed in a previous blog. The premise of the method is very simple: fragment the generic project into small parts that are delivered. In this case, the client is verifying the progress, or manifests the changes that he wishes to apply. Thus, the user constantly reviews until giving the final approval. For this reason, it is called the spiral methodology: it involves starting from a specific point and verifying and adding layers.

Commitment is indispensable

In Dynamics 365bc we affirm that this is the best method to implement an ERP because we are committed to meeting the established deadlines. In this way, if the client also presents the commitment and adopts an agile way of working in the verification and review of small deliveries, the project advances at a fast, agile and effective pace. On the other hand, if not

there is a symmetrical commitment by both parties involved, and delays in responses are experienced, the project may suffer various delays that affect the total time of implementation and its start-up. 

For this reason, a fixed implementation time cannot be established, but this fluctuates according to the work and agility of the client and the consultancy in question.

In generic terms

From our extensive experience, we have observed that microprojects are usually delivered every other day. First, two weeks after signing the project agreement, the master processes begin to be delivered. Then, the screens of operations such as orders, invoices, incidents, as well as related processes (route chapter, for example) are made. Other microprojects to be delivered are related reports such as the invoice format, and, finally, the Business Intelligence part.