Why can’t we forget about the project once it’s started?

There is a tendency to think that, once the project is started, it is already finished and goes directly to the maintenance phase. Nothing could be further from the truth. Neglecting the post-boot phase is a mistake and is unfair, in our opinion. 

After all the process of planning and implementing an ERP, it is very important that the two parts of the project continue to work, and do not ignore the project. 

What is post-start? 

The ERP implementation project is a complex process that requires a lot of work. Once started, errors or suggestions for changes may appear that should be made even if a lot of time has been spent planning and configuring the program.

This situation that can be caused must be included in the project. That way, you can continue to modify the application until it is stabilized and, finally, the client is working perfectly.

Thus, the post-start will allow to analyze the incidents that have arisen and to be able to correct the errors experienced, or to change and qualify the aspects that are required. That way, successful implementation can be ensured.

Where to include new ideas? 

It is possible for the client to express different ideas for improvement once the ERP has been started. Thus, the question may arise as to where to include the changes that are suggested: in a second phase of the project, or consider them as post-start improvements?

If these are new issues to be applied, they must enter a second phase of the project. The reason why it is recommended to do so in this way is that these are matters that were not raised at the initial stage and are therefore part of another approach.

Also, new ideas should be differentiated from post-start improvements. these improvements are closely linked to correcting system failures or adapting some

aspects to ensure the correct functioning of the ERP. That is, those developments that are strictly necessary to function.

The closing minutes 

The situation described above can lead to a conflict, since it is a matter of opinion. For this reason, to avoid a problem, it is recommended to make closing minutes for each project area. This record is a document that indicates and details the scope of the project, that is, where it ends. The use of it depends on the complexity of the project, since sometimes it is necessary to make a closing act for simple reports.

To exemplify the closing act, you can buy with a scale screen. On this screen it is tared, weighed, and then the final weight appears that is classified with a button. Equating it with the closing act, a print screen of the screen would be made indicating the buttons and fields it contains, as well as its function. 

Finally, it is important to finish the microproject by preparing a document that must be sent by email to receive its agreement. In this way, a contract is established limiting the scope of this microproject.