How to organize remote work of programmers?

Question

Work organization

Colleagues, good evening. There is a team of programmers - front, back and full stack, all working remotely without a clear schedule. The question arises - how best to organize the workflow?

At the moment, for example, the front sits down to do its job, some questions arise for the back, edits, etc. If the back is not working at this time, the team stands still. Or vice versa, the backend writes its own code, but cannot test it normally, because there is no front for all this.

I would like to ask you to share your experience, how is it implemented for you? Maybe assign working days / hours so that everyone is online at the same time? How to set tasks so that there are fewer questions?

Now a task is simply created in the jira, divided into two parts - backend and front. Everyone does what they want, as long as they get the required number of working hours per week.

Maybe there are some articles on this topic?

Answer 1

There is a logic... they should work at the same time. agree on a schedule that suits both.

Answer 2

Messenger, developers must know each other's total time, at least a few hours must coincide.

Answer 3

You can make a daily phone call at a certain time, but in general, if the back and the front cannot work completely independently (and they really don’t need each other at all, they haven’t given up on each other for 100 years), then, firstly, they both they are not professionally suitable - they do not know the techniques of unit testing, and, secondly, you have not described the format of json requests, which the front and back should exchange. These are the 2 questions you need to solve.

Answer 4

By default, their schedules can be shifted, but certain hours must overlap for everyone. Say, from 10 to 14 Moscow time everyone should be in place.
Separately, about the lack of a front for back tasks - this is poor planning, and not problems of remote work. Tasks should be divided and distributed over time so that there are a minimum of such situations.

Answer 5

The problem is that there are some blocking tasks, and the work must be asynchronous.

the front sits down to do its job, some questions arise for the back, edits, etc. If the back is not working at this time, the team stands still.

This is nonsense - let him deal with those parts that do not depend on the back.

Or vice versa, the backend writes its own code, but cannot test it normally, because there is no front for all this.

Likewise bullshit. Maybe you don’t have rest there, but some kind of crap with a terrible connection? Then that's the problem, not the graphics.