4 ms·

> "Remote" tends to imply a large chunk of the team is co-located, and one or more of the members are not. My experience here is that the remote people tend to

> "Remote" tends to imply a large chunk of the team is co-located, and one or more of the members are not. My experience here is that the remote people tend to not get the memo, or people fail to invite them to meetings because they don't want to bother with the conference room's videoconferencing equipment, or they do invite the remote folks but then the first 15 minutes of the meeting is devoted to figuring out how to work the Polycom system, etc. 100% this. source: am remote.

pasbesoin 8y ago
Add in the "sneakernet" of communication: Heading over to another's office or cube, and the event/conversation/information never gets captured in a form that can nor is communicated further. "Oh, we talked about that... when was that, three weeks ago?" I don't view this, per the example, as a positive pattern. Such things become anti-patterns. They're also another reason that meetings become long, confused, and drag on. The first one third, one half, maybe even two thirds can be spent syncing the team up with all these conversations and their data, that have taken place out-of-band. I guess agile, scrum, and the like are supposed to reduce this. But when people go to training to become certified "scrum masters"... Bureaucracy is winning, once again. (I remember one big, corporate "agile" name coming to speak at our campus, back when it was new. I think it was "agile"; the waves up corporate uptake start to blur, after a while. People actually showed up for it. And were rather disappointed: Same shit, new name.)
- dpkonofa 8y ago
  >Add in the "sneakernet" of communication: Heading over to another's office or cube, and the event/conversation/information never gets captured in a form that can nor is communicated further. This is a strategy and culture fail, in my opinion. Our team has a rule that sneakernetting is allowed but anything substantive that comes from it must be communicated immediately on our collaboration platforms (Slack/Box/etc). No "meetings after meetings" when people aren't connected and over-communicate whenever possible/necessary. If you discuss something and there is information that's needed that you're not communicating to people effectively, that's on you, not on the people working remotely.

pasbesoin 8y ago

Add in the "sneakernet" of communication: Heading over to another's office or cube, and the event/conversation/information never gets captured in a form that can nor is communicated further. "Oh, we talked about that... when was that, three weeks ago?" I don't view this, per the example, as a positive pattern. Such things become anti-patterns. They're also another reason that meetings become long, confused, and drag on. The first one third, one half, maybe even two thirds can be spent syncing the team up with all these conversations and their data, that have taken place out-of-band. I guess agile, scrum, and the like are supposed to reduce this. But when people go to training to become certified "scrum masters"... Bureaucracy is winning, once again. (I remember one big, corporate "agile" name coming to speak at our campus, back when it was new. I think it was "agile"; the waves up corporate uptake start to blur, after a while. People actually showed up for it. And were rather disappointed: Same shit, new name.)

dpkonofa 8y ago
>Add in the "sneakernet" of communication: Heading over to another's office or cube, and the event/conversation/information never gets captured in a form that can nor is communicated further. This is a strategy and culture fail, in my opinion. Our team has a rule that sneakernetting is allowed but anything substantive that comes from it must be communicated immediately on our collaboration platforms (Slack/Box/etc). No "meetings after meetings" when people aren't connected and over-communicate whenever possible/necessary. If you discuss something and there is information that's needed that you're not communicating to people effectively, that's on you, not on the people working remotely.