The story of how to “burn out” in distributed teams.
We at ProtocoleOne are writing different projects and almost all of them are Open Source. And it so happened that cool specialists live in different cities and even countries and not only in capitals.
One such project is PaySuper . A project for monetizing game projects and simplifying payment acceptance.
Every day I work with a lot of tough guys, write letters and talk in the morning, and once arrived at the office, I met all of them ... one of them.
Everyone else was somewhere in the “virtual” world, connected to me by a fiber optic line. And with all this, we manage to develop complex, long and cool (well, at least I think so :)) projects.
How? Let's try to figure it out.
In general, this article is my personal experience, but I tried to dilute it with an opinion from the “other side”, namely from the team leaders and technical director.
Well, let's get to know each other a bit. I’ve been a developer for over 11 years. He worked in large integrators, several startups and even in one indie gamedev team and for the last 3 years I have been working completely remotely.
At work, we use a standard set of tools for communication, the same as if we were working in the same office:
- Slack
- Jira / TargetProcess (here is your task tracker)
- Google Docs - for documentation
- Figma - for design
- Github as a code review platform and, in fact, code content
Nothing new, is it? But there are nuances.
Communication complexity
When working in the office, you see the flame of work or creativity burning in other people and they can share this heat with you so that you can flood your blast furnace.
In general, its micro-climate with special atmospheric pressure, a “shoulder-to-shoulder” feeling and all that.
, , . , , .
, . , . , , , — .
, . , , , , , -. .
, , , \\ , , . , , , .
“ , \ ”. “” .
, “” , . , “”.
, , “”, “ — ” . . , , , .
, .
?
, , , , . , “ ”, , .
15-20, . - , , - . , .
, - — " ". , , , , .
, , . , .
, .
, . , , . , . , “”
, .
, ? ?
, “” 1-2 . ""\"" , , — , "" , .
“” , — . ProtocolOne , , , .
( , , ), , “” .
scrum kanban . , , , , .
, - 1-2 .
"" , "". "" — , , . , , , , .
? ?
, “ , ” , . — , . “” . , -.
— , , , "". , , . . — . , , , , . . , -, , .
© (aka misterion )
, , .
, , , . " " " , ".
? , " ". , , , " " .
, .
, ?
— . , , , — “”.
. “” “ ” . , — .
, — , , .
.
. . , . , . .
— . , , , - :
- — , ,
- — . , , “”, . .
- — , , , , - , . , — , . , . , :)
- — . “” . , , , , , “”, .
, :) , .
— , .