In this series of articles, we've already taken a closer look at each stage of an ERP project implementation separately, with a focus on practical aspects and documentation.
The first stage ended with the approval of the project concept and the development of a detailed plan for the second stage, which is where software is developed, reference books are prepared, and technical solutions are formed.
Early user training and reference book development
One of the key tasks of this stage is to train end users to work with reference books and to create a structure of reference books in the system. This allows:
- familiarize the team with the new system in advance;
- avoid short training periods after the launch;
- adapt the data to the new structure of the directories;
- check, approve, and prepare a high-quality database for testing.
Important: In many cases, the structure of the new system does not match the old one, so transferring reference books may require manual work. Advance training helps to avoid problems with nomenclature migration in the future.
Technical solution and architecture of the ERP project
Once the preparatory activities are completed, the team moves on to formulating a technical solution. This is a process in which:
- The analyst describes, What exactly should be implemented in the system according to the concept;
- the architect develops how to implement it these functions, taking into account the capabilities of the platform.
Based on these documents, developers create program code and prepare the system for testing.
Waterfall implementation involves detailed documentation. We always strive for a balance between a sufficient level of formalization and flexibility for the customer. But the more complete the documentation, the easier it is to maintain and develop the system in the future.
Testing on real data
After the programming is completed, the prepared reference books are transferred to the system, and only then does full-function testing start. This approach allows users and analysts to work together:
- see how the system works in a real environment;
- test the functionality on actual data;
- formulate a final user manual.
Presentation of functionality and management of improvements
The result is a demonstration of the modeled processes and implemented functions. The customer checks whether it meets their expectations, and then:
- a list of improvements is recorded;
- decide which of them can be postponed until after the launch.
Not all user requests make sense to implement immediately. Often, 80% improvements become obsolete after a few weeks of working with the new system.
Thus, the agreed list is fixed, and critical changes (if any) are made before the launch. Next, the team develops a schedule for the transition to operation.
What's next?
The development stage is complete - the software is ready for pilot operation. In the next article, we will take a closer look at the final stage of ERP system implementation.
Do you need turnkey automation?
To-Do implements ERP solutions on the platform Odoo for medium and large businesses. Leave a request for a consultation - our analysts will help you create an automation roadmap for your company.
