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.
Task (requirements) should be clear. Ask if not.
Developer should avoid mistakes in understanding of requirements, so he should have a clear picture of the result.
Create a “conception of implementation”. And estimate it.
Developer should create idea of project technical performance, which we call “conception”.
They also make an estimation for that conception.
“Conception of implementation” should be revived.
Other developer from the team should review the implementation conception to make sure that it:
- fully covers the functionality requirements;
- takes into consideration all possible corner cases (multiple possible scenarios) of requirements;
- is correct due to technical issues and has no mistakes.
This level is the most critical as it defines the idea of future implementation.
We devote time to persuade that this idea is correct.
If it doesn’t we correct it before start development.
Start working on task.
Only when the task is clear and we know how to do it, we should start the development.
If task is out of time frame, notify team lead.
If developer out of time frame, he should notify Project Manager as soon as possible.
Developer describes the reason of situation and how long does it takes him to add to the original estimation.
So Project Manager can decide what to do with 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.
Developer should make clean-up of the code to make it ready for code reviewing by the other developer of the team.
Test an implementation.
Developer should test the implementation and to make sure that it works as expected and the new code doesn’t break all others pieces of application.
The implementation must be reviewed and tested.
Other developer from the team should test and review the code, to make sure that everything is done right.