loading="eager" alt="anaptis-erp-projektmethodik">
The anaptis project methodology has proven its worth for years: grounded and unique, we reach our goals together.
ERP projects (e.g. implementations or upgrades) are, in our view, not purely technology projects. They connect people, processes, and technologies. We won’t leave you on your own—we support you with the expertise we’ve gained from years of project experience. Our proven methodology is based on numerous software projects across various industries, carried out using both traditional and agile approaches such as Scrum.
The following process begins once we’ve conducted a workshop or prologue, based on which we’ve developed a rough concept including a proposal—and you’ve agreed to move forward.
The Executive Briefing is a meeting between the management teams on both the customer and provider sides (executive level), in which respective responsibilities and expectations are discussed.
This meeting can then transition into a kickoff meeting with additional participants such as key users, during which other relevant topics for collaboration within the project are also addressed.
Planning (Planning Meeting)
At the start of each implementation phase, the sprint tasks are planned.
Tasks are conceptually detailed and the budget is planned.
Any changes in definitions at this stage lead to a reassessment of budget allocation.
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.
We’re ready for the
Experience shows that this is the point when a lot of feedback starts coming in—because despite thorough testing, many things only become apparent once the software is being used intensively by all users. That’s completely normal.
We already account for this feedback phase in our planning.
You won’t be thrown in at the deep end with us. Even after the development phase, we’re still by your side!
You’ll keep your dedicated contact person who knows your project well.
And if you wish, we’ll also train your employees on how to use the system.
Let’s be clear and transparent: An ERP project means additional work alongside day-to-day business. You’ll need to allocate capacity for key users, involve your team, and prepare them properly for the change process. Ideally, our division of work is 50:50.
From the very beginning, we make sure that we’re a good human fit and that the chemistry is right—because only then can teamwork truly succeed. After go-live, you’ll benefit from a new, modern system that reflects your updated processes and that your team enjoys working with. It’s worth the effort!
Good planning and continuous testing during the project minimize costs.
The parallelization of teams in the project leads to more productivity.
Your regular feedback will quickly reveal any weaknesses.
Involving your team leads to appreciation and acceptance.
You have an overview of the status and costs of the project at all times.
We are looking forward to your inquiry!
