We follow our internal development process to make sure task is fully implemented and developed in the right way.
So we’re sure that everything done from one time, precisely and according to allocated time frame for each task.

The task or the requirements must be clear. They must be discussed if they are not.

The developer has to have the clear and complete picture of what the requirements are and the final result vision in order to avoid the mistakes in the completion of the product.

Create the conception of the implementation and estimate it.

The developer needs to create the idea of the project technical performance, one that we call “the Conception”.

They also make the estimation for the Conception.

“The conception of implementation” is to be reviewed.

Another developer(s) from the team is to review the implementation conception to make sure that it:

— fully covers the functional requirements;

— takes into consideration all of the possible corner cases (multiple possible scenarios) of requirements;

— is correct due to any technical issues and is mistake-free.

This is the most critical level for it defines the idea of future implementation and the final product. We devote time to persuade that this idea is correct. If there is no fallibility found we begin the development the app otherwise all errors are to be fixed previously and immediately.

The beginning of the development.

As soon as all is fixed and the task is clear to go we begin the process of the development.

The out of time frame notification.

If the app developer is getting out of the time frame he is to notify the Project Manager immediately. The developer is to describe the reasons of the situation and how long would it take him to add to the original estimation. The Project Manager, by-turn, is to make a decision on what has to be done with the remaining time for that task either to continue or to stop that task for now. This step helps us not to move out of allocated time frame and manage time expenses precisely.


The code clean-up.

The developer does the clean-up of the code to prepare it for the effective code reviewing by the other developer of the team.

The implementation tests.

The developer tests the implementation to make sure that everything works as expected and the newly created code doesn’t break all the others pieces of the application.

The implementation is to be reviewed and tested again.

The other team developer tests the code again and reviews it thoroughly to double check the work done.