• After a preliminary discussion about the project details, you will define the person to act as your dedicated project manager, the person who will carry out quality assurance with you. 
  • We offer our QA engineers’ services on request if necessary.     
  • We assign a responsible contact person for the new project – a Team Lead or an expert developer from our side, who will communicate with the Project Manager or Product Owner from your side. Communication with developers takes place via Redmine (or another tracking system of your choice) and via our corporate chat in Slack. We can also hold joint weekly meetings via Google Meet/Zoom/Skype with the team, usually 2-3 times during the life of the project.
  • We examine the project’s scope and estimate the approximate work volume. The most important thing at this stage is to get a comprehensive overall picture, so we know for sure what the project involves and can get everything right from the start. . 
  • The project manager and Team Lead discuss and define the various project development phases, splitting them into sprints and smaller tasks.  
  • After our developers have estimated what’s involved in each task, they will indicate the time needed within the project management system. Sometimes, when it’s hard to estimate a task for a developer or team lead, we split it into even smaller subtasks and assess each of them.    
  • Before starting on development, we ask for as much information as possible. We may also ask for other project member’s contact details so we can clarify unclear elements of the system. If the existing application is not covered by automated tests, we’ll develop them. We always insist on automated testing when it comes to complex business logic.

The process is as follows:
– We carry out several operations in the current system like add/edit/delete on the most essential modules, then we save the output results.
– We consider output values as correct (more operations are better).
– After we develop a feature or fix a bug we apply our changes to the system, first running automated tests to see if the results are the same as before and we haven’t broken anything.


  • For medium-complexity projects, learning the documentation normally takes around 3-4 days, sometimes a week. In the case of complex projects, it can take as long as 10 days. We also check if the project development requires coding standards, development requirements, coding conventions and more. Once we’ve learned and understood the project concept fully, we set up our development environment. 
  • Some customers require continuous integration and continuous delivery. In this case, the testing and deployment processes are entirely automated. We mainly deal with finance software involving many calculations, formulas, and reports, where automated tests are usually required. Writing a test takes around 30-35% of the task development time and it’s vitally important, saving us a lot of time in the future. 
Was this helpful?