Contractor's personal account
Posted: Wed Jan 22, 2025 6:15 am
Personal account of the job candidate;
Personal account of the design organization;
Internal marketplace for purchasing inventory items, etc.
CRM implementation projects stand apart. Of latvia telegram number database the three projects implemented in 2023, two were initial implementations, the third was the modernization and acceptance of the system for support from teams that had previously failed.
At the start of the work on upgrading the first (let's call it basic CRM) we had:
an exploited system on containers (support for this technology in Bitrix has not yet been implemented);
tight deadlines, parallel contractor and long backlog;
work in the customer's environment via VPN in compliance with information security standards;
complex industrial infrastructure: B24 in a box in the DMZ, no direct access to SAP (only through an intermediate database in the cloud), authorization via Active Directory, storage on S3;
a team of 12 with expansion on the go.
In order to meet deadlines and avoid jostling with another contractor, we had to adjust the development process:
developed a new release cycle, introduced a new status model;
with the customer's participation, we adjusted the pipelines for deploying environments;
implemented test plans and test cases.
While the work on the basic CRM was not yet completed, we started implementing the next one, focused on export contracts. The third implementation began in mid-2023 and was completed in February 2024. All three implementations are almost the same at the business level, but very different from the code point of view. In the application, we described in detail what difficulties we had to face and how we solved them.
Personal account of the design organization;
Internal marketplace for purchasing inventory items, etc.
CRM implementation projects stand apart. Of latvia telegram number database the three projects implemented in 2023, two were initial implementations, the third was the modernization and acceptance of the system for support from teams that had previously failed.
At the start of the work on upgrading the first (let's call it basic CRM) we had:
an exploited system on containers (support for this technology in Bitrix has not yet been implemented);
tight deadlines, parallel contractor and long backlog;
work in the customer's environment via VPN in compliance with information security standards;
complex industrial infrastructure: B24 in a box in the DMZ, no direct access to SAP (only through an intermediate database in the cloud), authorization via Active Directory, storage on S3;
a team of 12 with expansion on the go.
In order to meet deadlines and avoid jostling with another contractor, we had to adjust the development process:
developed a new release cycle, introduced a new status model;
with the customer's participation, we adjusted the pipelines for deploying environments;
implemented test plans and test cases.
While the work on the basic CRM was not yet completed, we started implementing the next one, focused on export contracts. The third implementation began in mid-2023 and was completed in February 2024. All three implementations are almost the same at the business level, but very different from the code point of view. In the application, we described in detail what difficulties we had to face and how we solved them.