Difference between revisions of "Communities of Practice"
From Learning and training wiki
Chantal joly (Talk | contribs) |
Chantal joly (Talk | contribs) |
||
Line 13: | Line 13: | ||
__NOTOC__ | __NOTOC__ | ||
=='''Step by Step'''== | =='''Step by Step'''== | ||
− | #''' | + | #'''Creating:''' |
#*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. | #*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. | #*To encourage people to participate, start a discussion on a domain or a smal problem and raise ideas for resolving this problem. | ||
Line 23: | Line 23: | ||
#* Watch the production of intermediate results, summaries and conclusions of the discussions. | #* 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. | #*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. |
+ | #'''Developing:''' | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
<ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no www.kunnskapsnettverk.no] (25September 2008), [http://www.communities.hp.com www.communities.hp.com] (29 September 2008)</ref>}} | <ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no www.kunnskapsnettverk.no] (25September 2008), [http://www.communities.hp.com www.communities.hp.com] (29 September 2008)</ref>}} | ||
Revision as of 13:36, 29 September 2008
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 :
|
Processing a CoP |
Step by Step
|
References
- ↑ Wikipedia (16 April 2008), www.km4dev.org (16 April 2008), www.kstoolkit.org (24 September 2008)
- ↑ www.kstoolkit.org (24 September 2008), www.kunnskapsnettverk.no (25September 2008), www.communities.hp.com (29 September 2008)