After seeing the previous phases of the ERP implementation project such as Microsoft Dynamics 365 (and talking about the foolishness of demos as an ERP selection method), we talked about the deliveries and the ERP implementation methodology, since we know that it is one of the most important pillars of the entire project process. We believe that the best and those that will be successful are those implemented with spiral methodology.
Spiral methodology
The basis of this methodology is a simple functional analysis, without excessive detail, that is, the data structures or screens are not specified. It is exposed what you want to do and how. From there, deliveries are made, and improvements are proposed on the deliveries.
How does the spiral implementation method work?
In the form of a loop, it is delivered, and improvements are suggested again. Clearly limiting the number of improvements or revisions per project. The client must commit at some point to be responsible in their requests and close the request for improvements.
Then several deliveries of the same part are executed. Hence it is called spiral.
This is the only methodology with which we will be able to do exactly what the client had in mind and consequently, earn their satisfaction with the finished and delivered product.
Why not use calendar or extensive trainings?
The schedules of deliveries and formations are absurd. A fixed timetable cannot be proposed, because each human being has a different capacity to absorb knowledge. So, each person learns faster or slower. In addition, depending on the functionality that is formed, it can be slower or faster, due to the difficulty of this. It is always recommended after a training to leave homework for the student to learn.
How should deliveries/trainings be?
Deliveries/trainings should be short, maximum one and a half hours of training and should be constant. The ideal and we recommend are 2 per week. They must be personal training or at most with groups of up to 2 people. Very concise, forming and delivering exclusively what the user needs to work, the ideas that are described in the analysis.