• Name *

  • Company

  • Email *

  • IM (Skype)

  • Message *

  • captcha

Thank you for contacting us !


Project lifecycle


The first step in a project lifecycle is a client request for building application with tech specification and requirements. Client describes in the document the idea of application, required functionality and business purpose of the application.

Next step from our side is to analyse received information and give some draft estimation and our price per hour.

If the client agrees with everything and client’s tech spec is good to start development – we made more detailed estimation and make agreement after which we start working on development phase of the project.

If spec is just general description of the project we working on draft version of complete documentation for the project and together with client prepare final spec. Based on that spec we make more detailed estimation and make agreement after which we start working on development phase of the project.

First of all we make architecture and system design. On that stage we plan how many components we will have and what milestones we determine for the project.

Having completed that step we start to make a task list for implementation of the application according to designed architecture.

We use agile approach in application development process. So we are creating sprints (1-2 weeks plan) with a list of tasks which need to be done during this sprint. Each task is passing several steps before it appears in the main application:

1. Development
Developer according to the spec implements the task.
2. Checking
Team leader checks if task was done correctly from the logical point of view and does the code review of the task to check if it’s done without overheads. If something was not good – task is returned to the developer for bug fixing.
3. Integrational test
After team leader checked the task it goes to the CI (Continuous Integration server) where set of tests are running to check if the new functionality didn’t affect application causing some errors. If some test wasn’t passed the task is returned to the developer. Team leader  also gets notification about that.
4. Integration into application
If everything passed good the task code is integrated into main branch of the application.

After sprint is done the updated application is deployed to the staging environment for testing. It’s a copy of production server and allows to see how the system will work with current production data. If for some reasons some functionality isn’t working well – a new task is created to fix that and created “hot-fix” to resolve the issue.

If everything is good the application can be deployed to the production and a new sprint can be started.