Difference between revisions of "Communities of Practice"

Difference between revisions of "Communities of Practice"

From Learning and training wiki

Share/Save/Bookmark
Jump to: navigation, search
Line 24: Line 24:
 
#*Gather a core group (leader, exoerts, stakeholders) and maintain 1 closer circle (involved members) and 1 outside circle (interested members, contributors, readers). Roles and responsibilities should be rotated between members over time.
 
#*Gather a core group (leader, exoerts, stakeholders) and maintain 1 closer circle (involved members) and 1 outside circle (interested members, contributors, readers). Roles and responsibilities should be rotated between members over time.
 
#*Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.   
 
#*Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.   
  <ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no http://www.kunnskapsnettverk.no] (25September 2008)</ref>}}
+
  <ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no http://www.kunnskapsnettverk.no] (25September 2008) [http://www.communities.hp.com www.communities.hp.com] (29September 2008)</ref>}}
  
  

Revision as of 14:27, 29 September 2008

Term2.png COMMUNITIES OF PRACTICE (CoPs)
A process of social learning where a group of people who share an interest, a concern, a set of problems, or a passion about a topic, collaborate to share ideas, find solutions, and build innovations without necessarily being in a formal work meeting. CoP members are bounded one another through exposure to a common class of problems, common pursuit of solutions, and embodying a store of knowledge, by shared practices and common beliefs. Community of practice generally cut across organizational boundaries and helps create and share knowledge. It is the best way to :


  • Learn while doing;
  • Ensure effective creating and sharing of knowledge and experience;
  • Co-learn about related practices across projects;


[1]. See also: Communities of Interest
Toolkit.png Processing a CoP

Step by Step

  1. Creation:
    • Decide what topic you wish to address in a community in order to identify the domain. Pick a compelling topic that will be of interest to many people in your organization, will be relevant to their work and will build on the core values of the organization. The potential members must be passionate about the subject for collaboration and the domain can itself invite involvement.
    • To encourage people to participate, start a discussion on a domain or a smal problem and raise ideas for resolving this problem.
    • Find a committed leader or coordinator for the community. Volunteer to be the community leader, or identify someone else with the right attributes and well-respected. The community leader should know the subject, have energy for stimulating collaboration, have sufficient time to devote to leadership, and then regularly spend time increasing membership, lining up speakers, hosting calls and meetings, asking and answering questions, and posting information which is useful to the members.
    • Identify thought leaders to legimate the community and potential members to leverage knowledge. The community will need a critical mass of members. You usually need at least 50 members, with 100 being a better target. Try to take advantage of existing networks.
    • Decide on a initial tecnology platform and create one or more tools for the community to use (threaded discussion forum, collaborative team space, web site or portal, Wiki, Blog or newsletter).
  2. Starting-up:
    • Once your community is established, publicize its existence to help recruit new members (sepcial event, articles, incentive to join).
    • Watch the production of intermediate results, summaries and conclusions of the discussions.
    • Gather a core group (leader, exoerts, stakeholders) and maintain 1 closer circle (involved members) and 1 outside circle (interested members, contributors, readers). Roles and responsibilities should be rotated between members over time.
    • Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.
[2]


References

  1. Wikipedia (16 April 2008), www.km4dev.org (16 April 2008), www.kstoolkit.org (24 September 2008)
  2. www.kstoolkit.org (24 September 2008), http://www.kunnskapsnettverk.no (25September 2008) www.communities.hp.com (29September 2008)