To keep documentation and project communication more organized and structured, we discussed and agreed to maintain project communication using JIRA rather than email communication. We used SLACK online conference for meetings, training, and monthly project audits with senior members of the client team.
After working on a module, we’d push all code to GIT. The client’s lead engineer would then review the code and either merge it with the master branch or reject it and ask the developer to fix any issues. The code is run on a pre-production system where they test the functionality. It’s pushed to live only after the system is working as expected. Over time, our engineers learned more about the client’s expectations and rejections became far and fewer.
- As always, we provided a comfortable setup for the client and all its members to work with our developers. The project manager developers are fluent comfortable in English and can communicate through SLACK conference, phone calls and emails. There were zero miscommunications on this project.
- We were mostly working with the client’s project managers and allocating projects on a first-in, first-out basis, but also keeping our daily task allocation process very flexible. This flexibility allowed us to accommodate urgent requests.
- We maintain detailed monthly records of each project, so we can look up any old projects for reference whenever needed.
Training and Onboarding
- We also took on the responsibility of training new members, saving the client time and money. Whenever we add new members to the team, we take the responsibility to train them internally and make them ready to work successfully on the client’s projects within few working days.