We make it real!

Our project approach is based on Agile and Scrum. Our project organisation is based on two principles: a proven methodology for approaching and carrying out an implementation project and excellent cooperation between all stakeholders. Working together, quality, and passion are key priorities of our approach. Business know-how, empathy, and knowledge of your processes is what characterises the people of B-informed. That's how we make the difference and how we impress.

Based on a Project Initiation Document and the Business Process, a Functional Design is determined for each functional work area. This is done based on Cravit's standard templates in which the standard Odoo functionality is included. This allows a clear picture of the requirements, wishes and the fit-gap to be quickly determined at a detailed level.

DTAP (Development, Test, Acceptance and Production Environment)

An DTAP street will be set up for the implementation process. For the setup of the DTAP street, Aniar uses the guidelines as shown below. It will be constructed as shown here. In the DTAP street the development line runs from left to right and the data line from right to left. This of course with versioning based on release dates.

Github

For the source code and module development Aniar uses Github. The source codes of all developments are also fully available to the client.

Odoo project issue management

For the registration and management of bugs, issues, features, actions and planning, Aniar uses the Odoo Projects module. This environment is accessible to all those directly involved. This environment is also used for support.

In this stage of the implementation process, any modifications that are needed will be made here. This is where developers will make changes to meet project requirements and will vary based on the needs of the company. Advanced deployments, data migration (not limited to contact books) and special applications are created here as well.  

Before developing customer-specific needs, we will work with you to first see what the consequences are, what the alternatives are, and what the benefits are. Preference must always be the default, unless it clearly adds value. In order to develop customer-specific needs in Odoo, we involve end-users at an early stage. We describe the processes, demands and wishes in a functional design. During development, we're constantly testing this with the users.

After all customisations have been made to your Odoo software final user testing begins on the ERP system. System testing is put in place to ensure that all specific business needs and project requirements have been met. This is validated by the users who will be using the software. 

The training will be tailored to your specific needs. Our experience shows that training on the job gives the best results. That being the case, we're guiding employees in their day-to-day work or on a specific project. In other cases, it is more efficient to train a group of employees at once, zooming in on the general operation and application of Odoo, tips, and tricks, etc. This is combined with examples and exercises on day-to-day practice.

Always an exciting moment. With a good go-live planning, acceptance test and the guarantee of a hands-on guidance, it works!

We set up a planning and going-live schedule, and if necessary a migration plan. This gives us a good understanding of the steps and risks of the going-live process. After an acceptability test, the going-live is scheduled and run according to the planning. The first weeks following the going-live are critical. During initial use, matters should always be identified and resolved as soon as possible. Despite testing, every live walk has points that no one has foreseen. Users accept them provided they resolve quickly and visibly.