For example, if you are designing a very complex system requiring multiple participants then it's very very hard to communicate your ideas over video conferences - even when tech worked flawlessly. It's not because people are not able to articulate the ideas but there is a lot goes on in body language, facial expressions and quick back-and-forth exchanges over whiteboard. The high bandwidth of occupying same physical 3D space permits speedy iterations while low bandwidth constraints what you must express in given slot you are expected to express.
So, remote work doesn't work for all scenarios. It works well when everyone knows things fair bit, number of iterations during communications needed are small and number of ideas don't need huge bandwidth. It doesn't work as well otherwise. For example, early days of startup where the product is in embryonic state, everybody working remotely would not work out well. However, if product is mature and roadmap is well under control then remote team might work great.
I supervised an entire PhD remotely many years back. We made it work, and learned as we went. Over time we got better as expressing confusion, double checking understanding, and all those sort of things where we use non-verbal clues in face-to-face meetings. It worked, but it wasn't an easy path at first. But there was an unexpected plus side - I'd learned to vocalize my doubts and confusion better, and to double-check we're on the same page. And so ever since I've found I'm more effective in face-to-face meetings.
That's funny but it reminds me of my relationship in the beginning. We didn't speak each other's native language fluently. Unexpectedly, harder communication had the effect of being clearer when expressing ourselves, and double-checking assumptions before reacting. It ended up very healthy.
Personally, while I agree that the bandwidth is higher locally, I don't agree you are prevented from expressing what you wish by communicating remotely; it just takes a bit longer, which is more than compensated by the time saved on other things.
Having an easily accessibly video conference software, committing to getting employees good headsets, and enforcing videos on/1 person per screen makes collaboration very easy.
----
The only thing that's missing is whiteboarding sessions (which seem to be more about fun than actual productivity). Instead, we typically ask a single engineer to write up a proposal doc then have everybody comment on that.
It requires a bit more lead time - write up, feedback, then finalization. However, the actual developer time is significantly less. One developer doing most of the work, with others chiming in periodically.
But I'm not a huge fan of whiteboards in general. Of course one problem with offline whiteboards is that the information tends to get wiped away (unless someone's snapping and uploading photos), the other is that they tend to be messy and unsearchable and hard to edit & update afterwards.
IMO it's generally better to flesh out ideas in text. It's just that sometimes a figure or two, maybe a flow chart, would get the point across quicker. I haven't found software I like enough to consider it better than hand, but hand sucks too. I often brainstorm on paper, and run out of paper or end up having to squeeze stuff because I didn't start with things in the right place. A software solution would help.
The main problem is the price, we can hardly afford one for each person, especially since it's not exactly something we use daily. Plus, even if we did, I'm not sure there's anyway to sync them in real-time.
IME unless your a particularly good teacher then your whiteboard isn't as high bandwidth as you think anyway. In face to face meetings everyone will just smile and nod because you have to go away and dig into the details to find issues. Put it in a graphviz drawing with the accompanying text and you'll get better results.
There’s stuff we outsource (easy to describe tasks), but the stuff that needs tight iteration loops is so much easier when you can just get up, walk a few meters, and talk about it.
That, by itself, isn't an argument that remote work for a given company will work.
I'm not saying it's not a good idea to have competing delivery teams. But it's quite expensive.
* Individual parts of the Linux kernel are often developed by people who do work together in an office (e.g. I used to sit with a bunch at Red Hat).
* Top-level Linux folks do meet in person fairly regularly, especially at LF events.
* Collaboration via email etc. is the primary workflow for the kernel, so there's no in-office cabal that has to learn new habits (and likely will resist doing so).
I'm also tired of hearing how silly startups can't do remote, but I don't think I'd hold up the kernel as an example that they could/should emulate.
[1] https://thenewstack.io/contributes-linux-kernel/
[2] https://www.cio.com/article/2909736/who-s-behind-linux-now-a...
It’s just poor quality planning and execution.
Your team is just improvising, figuring out as you go, what is exactly that you need to build.
It’s not even Agile. Agile is about tight loop upfront planning, and avoiding last-minute distruttive changes and meetings...
That's an abomination definition of agile, probably influenced by scrum. In the agile manifesto it says nothing about "tight loop upfront planing", however it does explicitly say[1]:
> Individuals and interactions over processes and tools
> [...]
> Responding to change over following a plan
While that doesn't mean all planning is bad (it isn't and the manifesto acknowledges that), the planning is not the agile part, it's the leftover of the original traditional management, because it is necessary to a certain degree (e.g. for alignment but also for a lot of other business related tasks).
If you're running a pure kanban approach, you don't even plan in tight loops and I had much better experience with that (and a single team lead with a good strategic vision) than I had with Scrum. Scrum is just easier to handle for big (old) organizations and gives developers some protection from bad management.
Sure it might be an abomination, but if we set the rhetoric aside for a minute we should consider the option that the context where Agile is applied isn't just RoR rockin' startups in the Bay. Lets call it dilution perhaps?
Besides, there's context. The Manifesto was drafted in a world still reeling in RUP and floor-wide teams marching towards quarterly releases.
That wasn't sustainable, but neither is "responding to change over following a plan" if that means moving targets every other day. That's a recipe for burn-out, and sprint commitments are sacred.
So yeah, context: respond to change means reassess every some sprint, not pivot 3 times a week.
/s (tongue in cheek people, life's too short for zealotry)
Potato potato. If you can get away with "poor quality planning" in person but not in remote, it doesn't matter what you call it.
If that's the case, you shouldn't be in the business unless you're in a junior/apprentice position (which is fine, one has to start somewhere.)
That doesn't mean I'm against remote work, by the way, we do a lot of it. But we need to be realistic about its limitations.
I'm convinced that remote work is something that works only for some people and some kinds of tasks. Anything that requires a lot of coordination sucks doing remote.
Our startup has gone through distinct phases -- It took us years to find product-market-fit and with that our ability to work remotely has gone through distinct phases that were obvious to the whole team.
At certain points it worked great, but once we moved from the idea testing phase to execution, we wanted to be face to face much more so that we could coordinate our work. Also since new hiring ramped, we have to prioritize face-to-face training.
We have a liberal remote working policy to the point where one of our team works from home almost all the time, whilst at the other end of the spectrum there are people who prefer to be in the office almost all the time, and then everything in between.
I fall somewhere in the middle. A day a week from home, particularly one with few or no meetings, can enable me to get a huge amount done. But I live alone so, whilst I am an introvert, I am not a misanthrope and need to ensure I get enough social contact.
Multiple consecutive days working from home can leave me feeling quite depressed and demotivated. I certainly wouldn't want to do it all the time.
I've had to do remote probably half dozen days in past couple of years. Here are some things I've observed:
1) As someone who do not regularly work from home, simply I'm not equipped well enough. I don't have extra monitors sitting around at home to hook up my laptop to give myself multiple monitors, for example, so I'm forced to work in a suboptimal setting.
2) Meetings can get tricky (Note: I also do language interpretation) I have mitigated this by hooking up my recording gear, which actually worked pretty decent.
3) Where there are clear objective for the day, it is relatively easy to handle. For anything other like supporting people who managed to show up at work remotely, was certainly harder part.
4) Everything becomes distractions. Something as simple as getting a cup of coffee. In other word I have to make one myself (or go out and get one myself) where at office I would have access to one close by or walk short distance to buy one.
I would probably sustain... maybe a week of remote at the most. Maybe regular remote workers have designed their life to work with it but certainly not for me. (Again, this also depending on the nature of tasks I need to get done.)
Most importantly, distractions from family members and lack of a boss looking over your shoulder means most people's productivity will be perhaps 20% of normal.
I felt this way for a very long time. Then I switched jobs and realized (1) there are some very good video conferencing tools that work even on 1 bar of LTE (2) a small investment in a camera/headset/microphone goes a long ways.
Call quality is easy to solve with decent hardware, a quiet office and proper muting (I see this work all the time with 10 to 100 person meetings.)
But I agree, better tools that integrate communication with project management is going to be a good space to try to build something in.
Remote work and distributed teams is basically like fate at this point. If our economy is prepared to build a whole car in different parts of the world and then ship it to the US, you better believe your little job tasks that can easily be sent in email is going to have to reckon with that.