7 ms·
I thought agile was supposed to be a preference for useful flexibility, rather than a fixed set of practices? The canonical remote collaboration tools are IRC
by tbrownaw 13y ago
I thought agile was supposed to be a preference for useful flexibility, rather than a fixed set of practices?
The canonical remote collaboration tools are IRC and mailing lists.
There are various sites that allow some sort of remote pair programming, I'm not sure if it's just screen sharing plus audio chat or if there's more structure to it.
At work we have conference calls, often with presenter-to-group screen sharing. (We use cisco webex, does anyone know an open alternative?)
For larger meetings we've been experimenting with videoconferencing between meeting rooms in different cities. Since being on video is annoying, maybe this would be an alternative to stand-up meetings? (I'm pretty sure whatever we use for this is proprietary as well, what's a good open alternative?)
The point of many Agile practices is to increase communication. How can you best capture the ease of walking 2 cubes over to have a chat with your coworker? If everyone's remote you don't have as good a natural indication of how busy or available everyone is. If you build something to provide that indication, the boss can monitor it and it will stop working right.
If people are talking in the next cube over, I can ignore it or jump in if I hear something interesting or that I can help with. But in some cases the discussions are things that wouldn't be discussed where certain other people might be able to overhear. How do you capture when communications should be available to some part of the group without interrupting them (so no acknowledgement needed from the recipient), but hidden from some other part of the group? And without requiring the people initiating the communications to explicitly bother to set this up? This is naturally baked in to physical-world interactions, is it useful enough to try to duplicate?
I've heard suggestions of a "virtual office" for voice chat, where you have a grid layout with cubes or conference rooms or whatnot and people have locations on that grid and can hear eachother (or not) based on how close they are. Is there anything that actually does this? Is it useful (or if it doesn't exist, would it be useful to have or is it just gimmicky)?
From what I understand, electronic text-based communications tend to be archived for a long time for legal reasons. How far does this apply to voice communications, and does VoIP vs telephones make a difference? How far does this affect what is or isn't said? I know at work, some conversations only happen in person or over the phone rather than IM or email. How important is this effect, and how does it impact getting work done?
- dragonwriter 13y ago> I thought agile was supposed to be a preference for useful flexibility, rather than a fixed set of practices? It is. To too many people "Agile" means "Scrum" (or, whatever particular set of fixed practices they've adopted, but Scrum seems far and away the most common.)
- lucaspiller 13y ago> The point of many Agile practices is to increase communication. How can you best capture the ease of walking 2 cubes over to have a chat with your coworker? If everyone's remote you don't have as good a natural indication of how busy or available everyone is. If you build something to provide that indication, the boss can monitor it and it will stop working right. I saw a tool the other week (I think from here) that shows you live webcam views of all your co-workers in a grid like fashion. Clicking on one of them starts a video conversation straight away. If they are busy or AFK it just shows a static profile picture. Regarding the boss monitoring it, I think in that case you need to find a better boss. EDIT: I think this is actually better than going over and straight up talking to someone. What if they are deep in the zone and don't want to be disturbed?
- sambeau 13y agoIt is, but the Agile Manifesto isn't, on the face of it, remote-worker friendly. 6. Close, daily cooperation between business people and developers 7. Face-to-face conversation is the best form of communication (co-location) So, I can see why people think there's a need to work out how to do remote working in an Agile manner or to find a viable alternative.
- dragonwriter 13y agoRemote working is always a trade-off sacrificing communication bandwidth for some other gain. Mitigating that cost -- because the gains to be purchased with it are often attractive -- has long been an issue in Agile circles, and its not really a "rethinking" of Agile to address that. Sure, the Manifesto states that Face-to-face conversation is the best form of communication -- that doesn't mean you can't use other forms of communication in an agile process, it means that you need to be aware of the costs and to do it only as a conscious decision weighing the communication costs against the benefits, and ideally doing what can be done to mitigate the communication costs.