- Conference Calls
- Instant Messaging
- IRC/Group Chat
- NetMeeting (Shared Desktop)
- Social Networking Sites (LinkedIn, Facebook)
- Forums/Bulletin Boards
- Video Conferencing
- Second Life
Factors in Choosing Tools:
- Location of members, documents, and products.
- Ease of use
- Time--lenght of collaboration--amount of planning
- Audit trail
- Time zones
- Urgency of collaboration
- File sharing
- Number of people on your team
pros: Lots of info, versions, flexible, fast to post, great for producing docs, generally easy to use, good for documentation, infinitely scalable, captures high quality, good for background
cons: not as easy to understand, better for tech savvy, dfficult to parse, can be difficult to find, adoption is challenging, adoption can be hard, needs more monitoring, can be hard to view what changes (depending), difficult to compartmentalize, versions can be an issue, bad for simultaneous groupware
pros: simultaneous writing, easy access to files, structure is closer to what people are used to, easy to have different teams on different documents, Can have view-only users, versions is easier, more easily supports word/openoffice, easy to get started, easy to upload without a lot of
cons: individualnot group focused (in GoogleDocs), security is a pain, everyone needs google account, not as fast to scale, easy to delete, have to backup data, internet dependence, hard to archive
SharePoint/Intranets--intranet portal that allows easy creation of subportals--group collaboration internet tool--includes calendars--microsoft project
pros: flexibility, doc storage, SharePoint integrates well with Microsoft, easily post docs, file sharing, good for non-tech ????
cons: user adaptation, it can do anything but at a weighty cost, SP: overlap with MS Products poorly, difficult/costly to customize, costly to add licensens/file space
more: There's an overlap of sharepoint skills and programming skills to be able to fully utilize sharepoint.
Pros: easy to use, see different changes/audit log, clear doc trail, tasks/milestones, discussions
Cons: expensive, limited functionality, not as flexible
More: When would you use wiki vs. basecamp?
Social Networking Sites
Pros: good for contact storage, outreach to volunteers, free, keeping in touch, personal ties
Cons: personal ties, substantial setup
Pros: one question/multiple answers, ask the public, social postings, can opt to view or get emails, task allocator, digest or not, push
cons: bat at organizing things, setup intensive, adoption, volume of email, lack of ownership, easy to ignore
Pros: familiar, promotes discussion, feel fancier/newer, more central control
Cons: needs central direction, needs to be set up, stagnates/bottlenecks without central contributor, new setups for new things
more: good if you'd got it.
Pros: fast response, synchronous/asynchronous, captures fluid knowledge, great for rewrite, quick question/answer, watercooler conservation
More: Multicollaborative Joomla Bug Squashing IRC/Yugma/Skype
Cons: Geeky, high setup--admin/avatar angst/user needs to setup,
There's no tendency to multitask since you're accountable. Maybe we should change the culture of multitasking for other larger-scale collaborative venues (group chats, conference call, etc).
Q: What do you do with team members with different amounts of tech experience? What tools would you recommend?
A: Conference calls. There needs to be a culture of how to be comfortable with the tools that you use on both sides.