We follow our internal development process to ensure that
the task is fully implemented and designed correctly.
This way we make sure everything is done in one go,
accurately and within the allotted time frame for each task
TASK OR REQUIREMENTS MUST BE CLEAR.
THEY MUST BE DISCUSSED
IF THEY ARE NOT
The developer must have a clear and complete understanding of the requirements and vision of the final result in order to avoid mistakes when finishing the product
CREATE THE CONCEPTION
AND ESTIMATE IT
Developers need to create an idea of the technical characteristics of the project, which we call "Concept".
They also rate Conception
“CONCEPT OF IMPLEMENTATION”
MUST BE REVISED
Another developer(s) from the team has to review the implementation conception to make sure that it:
– fully covers functional requirements
– takes into consideration all the possible corner cases
(multiple possible scenarios) of requirements
– is mistake-free and correct due to any technical issues
This is the most critical level as it defines the idea of the future implementation and the final product. We devote time to make sure the idea is correct. If no errors are found we start developing the app. Otherwise, all errors must be fixed in advance and immediately
START OF DEVELOPMENT
As soon as everything is fixed and the task is clear, we start the development process
OUT OF TIME FRAME NOTIFICATION
If an app developer is getting out of time frame he must immediately notify the Project Manager. The developer should describe the reasons for the situation and the time it will take to add to the original assessment. The project manager, in turn, must decide what needs to be done with the remaining time in order for this task to continue or stop at this point.
This step helps us to stay within the allotted time and precisely manage the spent time
Developer performs the code cleanup to prepare it for effective code review by another developer of the team
Developer tests the implementation to make sure everything works as expected and the newly generated code doesn't break all other parts of the application
IMPLEMENTATION MUST BE REVIEWED AND TESTED AGAIN
Another developer on the team is testing the code again and thoroughly reviewing it to check the work done again