Implementation Methods
Work cycles
Phased deliveries in 3-week cycles.
After each cycle, the hourly load used is billed.
Beginning of the project
Entry into planning 3 weeks after allocation.
Implementation time to be defined in a Kickoff meeting
Our process in four easy steps
Validation
Collection and approval of
customer requirements and needs
Implementation
Implementation of functionalities according to the raised requirements.
Testing
Tests of the implementation of functionalities in the
client's instance
Go-live
Training of end users and correction
of possible "bugs".
The team involved in the project
Project Manager
Responsible for coordinating projects, validating client requirements, managing deliverables, overseeing development, testing functionalities, and supporting implementation.
Functional Technician
Responsible for configuring and customizing the system in alignment with the specific needs of each service or client.
Developer
Responsible for developing specific functionalities based on defined requirements and conducting unit tests.
Contact person
On the part of the client, the point of contact (SPOC) is identified for all project decisions, with recurrent communication being necessary and fundamental to the success of the project.
Implementation
The objective of the implementation is to avoid customized developments, framing the processes in the workflow of the Odoo system, thus guaranteeing greater stability and the possibility of migration, although in the reality of the institute some future customization may be necessary to fill in the requests related to the operations.
Implementation assumptions
a) The SPOC (Single Point of Contact) is responsible for receiving training and relevant information during the project implementation and conveying that knowledge to the rest of the team.
b) A Project Manager is assigned to each client, providing personalized support and ensuring high-quality service and effective project management. The time dedicated to project management will be recorded and billed as part of the implementation process.
c) Thanks to the flexibility of the Agile methodology, even if there is an initially defined macro scope, it can be redefined as the client's needs evolve during the implementation process. This means that initial budget estimates can be significantly adjusted as the project progresses.
d) When there is a need for custom development, the estimated consumption methodology is maintained; however, the pricing undergoes a change. All activities related to custom development are included in the cost of the development product.
e) Arxi is responsible for conducting configuration and development testing, with the time spent on these being consumed in project management. However, the client is responsible for conducting additional tests and has the final authority (represented by the SPOC) to decide when the developed work is ready to be put into production, after the presentation in the testing environment. This ensures that the client has control over the quality and release of the project.
f) At the time of project closure (Go Live), when the overall scope of the project is in production, the project will be ready to be closed and handed over to support (as established in an active support contract). After the Go Live date, a period of 15 calendar days will be granted for adaptation and validation by the client in a real environment, at no additional cost.
Consulting
Personalized guidance to optimize system usage, ensuring its alignment with business requirements and the proper training of employees, thereby promoting efficiency and productivity.
Implementation
Configuration and customization of the system in accordance with the client’s requirements, including Odoo installation, initial setup, module adaptation and, where necessary, integrations and data migration.