ERP projects according to the anaptis method.

WORK MORE EFFECTIVELY WITH ANAPTIS:

An ERP project affects to a large extent business-critical processes in your company. Of course, this requires a deep trust in the solution partner. By presenting our project methodology, we would like to acquire this trust on your part. Our methodical approach has been tested over several years and guarantees quality and risk minimization. The knowledge gained from numerous software projects, realized according to classical approaches or agile like Scrum, flows into our very own project methodology.

1. Prologue to the rough planning

The project team defines all necessary functionalities and tasks for the software development in a coherent time frame (four days) without a detailed, conceptual definition of the later implementation.

This results in individual tasks, which are brought into an evaluation system by calculation. The result of the prologue is a list of all tasks and a budget framework to be commissioned for this. Tasks receive a classification (must-have, nice-to-have) with influence on the budget usage.

Practical example: One requirement is the creation of collective invoices per customer and month.

2. Planning of the implementation phase (planning meeting)

Which tasks should be implemented? The detailed conceptual design and budget allocation will follow.

Practical example: Using batch processing, unposted sales invoices are generated at the end of the month. These can then be checked, processed and posted by the responsible employee. Batch processing can be limited using the following parameters: Customer number, order number and delivery date. Fully settled orders should be deleted after the posting transaction. The user can specify the posting date using another option. The action for batch processing is inserted in the Accounting role center to allow direct access.

3. Implementation of the requirements

After the implementation plan has been released, the implementation phase begins. We implement the coordinated requirements from the phases before that.

4. Testing and acceptance of the implementations

Tasks that are not completed will be carried over to the next implementation phase. Definition changes lead to a new evaluation of the budget usage.

Cooperation with the startup echometer

Through our cooperation with the Münster Start-Up Echometer, you increase the acceptance of your employees already during the ERP project. How exactly does this work? The company conducts employee surveys using an agile feedback tool.

Why does this make sense?

The introduction of a new software is accompanied by major changes. Often this means a change in the entire way of working. Fears and concerns quickly arise among your employees, which can cause the entire project to fail if they are not taken into account. Therefore, communication between employees, management and the software provider is of particular importance. This is easily done with the help of Echometer.

How does it work?

As a software service provider, we receive regular feedback from you and your employees, so that we know what is going well and where difficulties could arise throughout the entire project. We then take immediate action to counteract these critical points, thereby increasing employee acceptance of the project.

The bottom line is that regular feedback increases the acceptance of your employees and ensures a constant improvement process of your processes. Just let us know that the topic interests you.