|
|
|
|
|
|
by imrehg
1539 days ago
|
|
|
> Recently we started experimenting with synchronous collaborative programming I wonder how those experiments are going? The expected benefits do make sense, I wonder if there are any downsides (expected or experienced) at all? It's never all free lunch, and wondering about the two sides. The calendar-based call-out to the team when one's ready for some collaboration is an interesting tool, and something I'm gonna try. I'd guess a cousin of the "focus time" calendar events when the activity is very similar (still coding), except preferring solo rather than collaborative. |
|
|
While it’s a bit early to make right conclusions, we already have some learnings and outcomes. We do see increase in overall happiness and mood in the team, knowledge is shared more effectively and we started slowly to break silos. Another interesting side-effect seems to be that regardless people collaborate on particular problem or not, disagreements somehow got easier to resolve, as we understand each other better. Another interesting change is that we need less synch meetings.
So far the biggest challenge is respecting individuals preferences, as the more people collaborate together, the more it becomes implicit expectation, whereas not everyone wants to do it, or some days you want some others not. So making sure that we don’t get pulled to any extreme is very important. Time zone differences is another challenge, sometimes because energy level really differs and its hard to find the harmony working together.