Group items tagged

The following tips come from research into virtual teamwork. Hold an initial face-to-face startup Have periodic face-to-face meetings, especially to resolve conflict and maintain team cohesiveness Establish a clear code of conduct or set of norms and protocols for behavior Recognize and reward performance Use visuals in communications Recognize that most communications will be non-verbal -- use caution in tone and language

Strategies for VTThe following tips come from research into virtual teamwork. Hold an initial face-to-face startup Have periodic face-to-face meetings, especially to resolve conflict and maintain team cohesiveness Establish a clear code of conduct or set of norms and protocols for behavior Recognize and reward performance Use visuals in communications Recognize that most communications will be non-verbal -- use caution in tone and language

“Carriers of Culture” Principles of Collaboration The development of the “Carriers of Culture: Living Native Basket Traditions” exhibition is an activity, while coordinated by the Michigan State University Museum, is a collaboration by numerous stakeholders.  The MSU Museum will use the following set of “Principles of Collaboration” to guide the process of working in partnership with stakeholders in the basket project.

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration. Attention Management - Reduce time wasted in the Inbox. CC to Wiki - Get around the curse of Reply-to-All. Collaborating on a non wiki page using a wiki page - Use the attachment feature to collaborate on presentation files, etc. Designing Spaces - Key considerations for creating new spaces. Developing a Public Blogging Strategy Distributed Document Review Gardening and Wiki gardening tips Index Pages - create starting points for navigation around topics of interest. Lightning Editing - how to co-edit a document with a collaborator Securing buy-in - getting others to shift perspectives on wikis Sparking participation at events Using the workspace as a document repository

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration > . > Attention Management > - Reduce time wasted in the Inbox CC to Wiki > - Get around the curse of Reply-to-All. > Collaborating on a non wiki page using a wiki page > - Use the attachment feature to collaborate on presentation files, etc. > Designing Spaces > - Key considerations for creating new spaces. > Developing a Public Blogging Strategy > Distributed Document Review > Gardening > and > Wiki gardening tips > Index Pages > - create starting points for navigation around topics of interest. > Lightning Editing > - how to co-edit a document with a collaborator > Securing buy-in > - getting others to shift perspectives on wikis > Sparking participation at events > Using the workspace as a document repository > Doing a demo Create tagging structures - Develop a core list of tags for your wiki Wiki Structure - Create a page which outlines important elements of the wiki Stop creating Word documents - The first rule of integrating wikis effectively See also Bonnes Pratiques for a chart of best practices and French translations.

What Is Collaboration? Wood and Gray say that each definition of collaboration used in the articles reviewed has at least one important element missing. They say that any definition must be able to answer the following: Who is doing what, with what means, toward what ends? "This leads us to create the following revised definition," they write: Collaboration occurs when a group of autonomous stakeholders of a problem domain engage in an interactive process, using shared rules, norms, and structures, to act or decide on issues related to that domain. Stakeholders may have shared or differing interests in a problem domain, and these interests may change over time. Some degree of autonomy is required, or else stakeholders "merge" rather than "collaborate." Rules for governing interactions must be implicitly or explicity agreed upon. Acting or deciding is needed to reach a common objective. The domain is the issue or set of issues that stakeholders are interested in, such as local traffic congestion or a nation's economic health. Wood and Gray say that this definition is general enough to include a wide array of collaborative forms but specific enough to exclude others, such as blue ribbon panels that never meet, corporate mergers, and clubs that have no specific problem-solving objectives. The authors next discuss the other 3 issues confronting a comprehensive theory of collaboration.

There are two ways to go about encouraging adoption of social software: fostering grassroots behaviours which develop organically from the bottom-up; or via top-down instruction. In general, the former is more desirable, as it will become self-sustaining over time - people become convinced of the tools' usefulness, demonstrate that to colleagues, and help develop usage in an ad hoc, social way in line with their actual needs.

These key users should: be open to trying new software be influential amongst their peers, thus able to help promulgate usage have the support of their managers Users who are potential evangelists should be identified at every level of management, not just amongst the higher echelons, or amongst the workforce.

3. Convert key users into evangelists Training in the form of short informal sessions (face-to-face or online) and ongoing on-demand support are the basics for encouraging adoption. Too much training or too formal a setting will put users off, and is usually unnecessary.

Developer support is crucial to the success of Google Wave

the genius behind Google Wave is

in the way Google has assembled a set of existing technologies into an attractive platform for developers

web technologies in the service of communities of practice

SMC is created on a Drupal base

customized to reflect what Howard thought would be useful for educators