Our Proven Project Methodology

Neither classic nor according to Scrum but according to the anaptis project methodology. Down-to-earth and unique.

Project Methodology
Benefits

ERP System Project Methodology:

Our Proven ERP Project Methodology

Will our team work with the software? Will there be personnel resistance? Will we have to revise our processes? Questions upon questions.

Don’t worry: Our approach is holistic and leaves no questions unanswered. In our opinion, ERP projects are not purely technology projects, but combine people, processes and technologies. We won’t leave you on your own and will support you with our know-how from our many years of project business. Our proven methodology is based on numerous software projects that have been implemented using classic or agile approaches such as Scrum. But we also have to be honest and transparent at this point: an ERP project means additional work alongside your day-to-day business. You need to create capacity with key users, get your team on board, prepare them properly for the change process and show commitment. Ideally, our division of labor is 50:50. We make sure from the outset that we fit together on a personal level and that the chemistry is right. Only then can teamwork work. After the go-live, you benefit from a new, modern system that maps your updated processes and that your team enjoys working with.

The subsequent process starts once we have conducted a workshop or prologue, on the basis of which we have drawn up a rough concept including an offer and you have agreed to it:

Executive Briefing and Kickoff Meeting

The Executive Briefing is a meeting between the executive leadership on the client side and the provider side (executive level), in which the respective tasks and responsibilities are discussed. Expectations can also be discussed so that clarity exists for both sides from the beginning. Following this, the meeting can transition into a kickoff meeting with additional participants such as key users, where relevant topics for collaboration in the project are also discussed.
Planning and Implementation (in Phases)

Let’s go! We start with the iterative implementation phases (individual number of sprints). Our teams work regularly in 4-week sprints.

Planning (Planning Meeting)
At the beginning of each implementation phase, the sprint planning takes place. Tasks to be implemented are planned.

The tasks are detailed in terms of concept and the budget is planned. At this point, definition changes lead to a new evaluation of budget utilization. In the end, the customer must test the implementations of a phase and assess the quality.

Implementation
Subsequently, the tasks are implemented in an iterative process.

Testing and Quality Assessment (Review Meeting)
In the context of the Review Meeting, the implementations are tested and the quality is assessed. Incomplete tasks are carried over to the next implementation phase. This process is repeated in each of the implementation phases.
Consolidation, Integration, and Optimization

After these implementation phases in sprints, we move on to the integration phase. Here, we carry out integration, performance, and stress tests to ensure that our implementations interact seamlessly and that you can work optimally with the ERP system.
Go-Live

Once this is done, we are ready for the official launch of the software. Finally, the software will be put into operation!

Experience shows that at this stage a lot of feedback is received, as many issues only become apparent when the software is used extensively by all users. This is completely normal. We already account for a certain time period for this feedback in our planning.
Support

You will not be left in the lurch with us. Even after the development phase, we are here for you! You will retain your dedicated contact person who knows your project well. We are here to support you if you need assistance, have a question, or if new requirements arise over time. If desired, we can also provide training for your employees on how to use the system.