How We Work

We use agile methodologies, provide transparent reports each week, and run business processes related to the development process ourselves.

Our team (depending
on the type of the project):

We are aware of how important it is not only to deliver projects in a timely manner, but to maintain the appropriate quality level of the product as well. We use the Kanban method that allows us to maintain high development speed and high quality of services.

As for Scrum, we use only an iterative approach from this framework, for the reason that very often Scrum implemented “as is” can be more of a hindrance than a help in certain types of projects.

How Kanban board
may look like

We visualize processes using the Kanban method to make our work more transparent and effective.

In Progress
Code Review
* Kanban board may look different depending on the type of the project
Iterative approach instead of waterfall uncertainty

Probabilistic instruments and iterative development instead of traditional waterfall approach

Step 1. Project planning

To start with we decompose your project into features. Also in this step, we provide a very rough estimate of how long the entire job might take using our estimation tools.

Step 2. Planning 1 week iteration

Now we break down several features into the so-called user stories and put them into a one-week sprint backlog. On this stage, we are committed to completing all the tasks from the backlog in one week.

Step 3. Sprint (1 week)

We work on the tasks from the sprint backlog. It is very important to notice here that it is highly undesirable to add new tasks in the existing queue of the current iteration so that we could complete the work in time.

Step 4. We are reporting on the sprint results

At the end of each iteration, we provide you with a progress report. If there were any tasks we could not complete, the report will contain the explanation and how this can be corrected in the future sprints. After this, we go back to stage 2 to plan the next iteration.

Oh, wait! That is not all we do
  • We also set up CI/CD for projects

  • We can do QA job ourselves

  • We have a solid engineering culture

  • We write E2E tests using

  • We have code review process

  • We use static code analysis tools

  • and many other things!