Evrone's experience: how to build processes in a remote development team

[bhasan01854]

Evrone was initially formed as a remote team, and over 12 years of work we have tested many methodologies and tools. As a result, we came to a format in which our team leader controls the successful implementation of the project, but does not slide into micromanagement. He follows digital traces, such as code, documentation, tasks in Jira, communication in corporate messengers.

Planning stage
Tasks in Jira are a way to find out who is working on what without asking too many questions. We adhere to the rule that there should only be one current task "in progress". The team leader only intervenes if he sees that the to-do list is empty or overflowing, and helps to prioritize.

In our team, we practice two-way fusion database assessment of deadlines and control over labor costs. At the planning stage, the team leader helps to orientate in time, not to set overly optimistic deadlines, but to soberly assess the task and its complexity. The developer, in turn, at the end of each day or at the beginning of the next one, notes how many hours he spent. This is a good indicator. If an employee spends several hours on solving a simple task, it's time to intervene.

Development stage
At this stage, we have two rules: the developer must send code to the repository every day, which is reminded by a push notification, and regularly submit the work for code review. The team leader reviews the code and immediately understands whether the work done corresponds to the task or the developer has lost his way and lost focus.