anaptis GmbH
Your successful ERP project according to the anaptis project methodology.
WORK MORE EFFECTIVELY WITH ANAPTIS:
An ERP project touches business-critical processes in your company. This requires a deep trust in the supporting partner. Our proven methodology is based on numerous software projects, realized according to classical approaches or agile ones like Scrum.
We always think holistically. Because ERP projects are not just technology projects. Anyone who thinks that is wrong. We know our stuff when it comes to the processual and human components in change projects and are happy to provide support in the area of change management. In our experience, it achieves quality as well as risk minimization in equal measure. Unique and recommendable.
Technology
Processes
People
anaptis project methodology:
This is how we implement your project.
The following process starts when we have conducted a workshop or prologue, on the basis of which we have worked out a rough concept including an offer and you agree with it:
STEP 1:
Executive Briefing and Kickoff Meeting
The executive briefing is a meeting between the management on the customer side and the provider side (executive level) in which the respective tasks and responsibilities are discussed. In addition, expectations can be discussed so that both sides are clear from the start. This meeting can then be followed by a kickoff meeting with other participants such as key users, in which relevant topics for collaboration in the project are also discussed.
STEP 2:
Planning and implementation within fixed implementation phases
Let's go! After the release of the implementation plan, the iterative implementation phases begin (individual number of sprints). Our teams work regularly in 4-week sprints.
Planning (Planning Meeting)
At the beginning of each implementation phase the planning of the sprint takes place. It is planned which tasks will be implemented.
The tasks are conceptualized in detail and the budget is planned. At this point, definition changes lead to a new evaluation of the budget usage. At the end, the customer must approve each of these implementation phases.
Implementation
Subsequently, the tasks are implemented in an iterative procedure.
Tests and acceptance (review meeting)
Finally, the implemented tasks are tested and accepted during the review meeting. Without acceptance, the next implementation phase will not start. Tasks that are not completed are transferred to the next implementation phase.
This procedure is repeated in each of the implementation phases.
Planning (Planning Meeting)
At the beginning of each implementation phase the planning of the sprint takes place. It is planned which tasks will be implemented.
The tasks are conceptualized in detail and the budget is planned. At this point, definition changes lead to a new evaluation of the budget usage. At the end, the customer must approve each of these implementation phases.
Implementation
Subsequently, the tasks are implemented in an iterative procedure.
Tests and acceptance (review meeting)
Finally, the implemented tasks are tested and accepted during the review meeting. Without acceptance, the next implementation phase will not start. Tasks that are not completed are transferred to the next implementation phase.
This procedure is repeated in each of the implementation phases.
STEP 3:
Consolidation and optimization of the implementation phases in the integration phase
After these implementation phases in sprints, we move on to the integration phase. Here we carry out integration, performance and stress tests and ensure that our implementations mesh ideally and that you can work optimally with the ERP system.
STEP 4:
Training and testing by your team
We then begin to finalize your data and train your key users. After that, the key users have time to put the system through its paces.
STEP 5:
Go-Live
Once this is done, we are ready for the real start of the software. Finally, the software is put into operation!
Experience shows that a lot of feedback comes at this point, because despite the conscientious testing, many things only become apparent when the software is being used intensively by all users. This is quite normal. We therefore already take a certain time frame for this feedback into account in our planning.
Experience shows that a lot of feedback comes at this point, because despite the conscientious testing, many things only become apparent when the software is being used intensively by all users. This is quite normal. We therefore already take a certain time frame for this feedback into account in our planning.
STEP 6:
Support
With us, you are not thrown in at the deep end. Even after the development phase we are there for you! You keep your fixed contact person, who knows your project well. We are at your side if you need support, have a question or if further new requirements arise over time. If you wish, we can also train your employees in the use of the system.
How do I get my employees excited about the project?
Successfully master change management and increase your employees' acceptance of the new software solution already during the project.
anaptis project methodology:
These are your wonderful advantages.
Lower costs
Good planning and continuous testing in the project minimise costs.
Productive work
The parallelisation of teams in the ongoing project leads to more productivity.
No weak points
Through your regular feedback, weaknesses are quickly uncovered.
Enthusiastic users
The continuous involvement of your team leads to appreciation and acceptance.
Transparency
You have an overview of the status and costs of the project at all times.
Learn more: