portfolio

ENTERPRISE RESOURCE PLANNING

Mission background

Innoval is the result of the merger of the Évolution cooperative, the GDS Bretagne and the BCEL Ouest and Copavenir livestock consulting companies, which together represent more than 30,000 breeders and 1,700 employees.

At Advential I strengthened the team in charge of the client project "Innoval360" by replacing the Tech Lead who had just left. The team was composed of 4 frontend developers of which I was the Lead, and 2 backend developers led by another Lead. We worked in close collaboration between leads and the project manager, as well as with the various people at Innoval.

► The challenge was to create an application that is both static and nomadic, connected and offline, efficient and intuitive for the operators and administrators of the tools while aggregating the old data and use cases of the tools that the application replaces.

Roles, actions taken and objectives achieved

• Development of business features based on a graphics and functional specifications.
• Realization of an audit/analysis on the whole application to highlight some technical needs which brought a significant gain in performance as well as a modification of the erroneous vision of the offline (i.e. it is necessary to think Offline First).
• Decision & supervision of a refactoring necessary for the viability of the project
  • Solo development of the real-time data synchronization brick for the frontend.
  • Work with the backend team to define and create the contract between the frontend and backend data.
  • Abstraction of the synchronized SQL tables via a custom implementation of the Redux Pattern in RxJS in order to get the alterations in a continuous way.
  • Realization of a set of scripts & schematics in order to conventionalize the refactoring done by the devs.
  • Realization of a documentation of refactoring GraphQL towards IndexedDB specific to the project for the team.
  • Refactoring of the backend functionalities already developed to date due to the awareness of the need for offline first.
  • Definition of new data standards, new frontend responsibilities and new technical tools.
  • Set up restrictive types to restrict/encourage the team to follow the guidelines.
  • Creation of ESLint rules to indicate best practices to the team.
  • Implementation of a set of integration tests to validate the refactoring.
• Integration and support of a student in the frontend team.
• Supervision and daily support of a team of 4 junior developers.
• Follow-up of the team's progress & learning around the paradigm of reactivity.
• Close relationship with the client's technical and product department.
• Weekly meeting with the project manager to standardize the new functional specifications so that they can be broken down into tasks and distributed to the front-end team.
• Weekly/daily participation in product meeting / targeting the need.
• Occasional participation in steering committee meetings.
• Set up and manage the client's CI/CD (Gitlab) evolutions so that our products are seamlessly integrated and delivered into their Kubernetes environment.