====== Communication ======

Since Wikis can support communication in many ways, the actual communication procedures need to be defined clearly to avoid misunderstanding. Furthermore, email is the main personal knowledge management tool so it's important to use it effectively to let people know when wiki pages need review. [[Social+Tagging|Social tags]] allow easy labeling of pages to be changed and thus, self-determined work on critical and most interesting content.

===== Usage =====

Briefly go over current work on the wiki and open questions at each meeting. Solve document interdependencies. During this discussion, try to avoid discussing the actual content so you can focus on logistical issues.

===== Example =====

Have communication procedures that clarify at least when pages should be sent around via email (e.g., for review). In particular, clarify whether customers provide feedback directly to the Wiki. Discuss and change communication procedures if problems occur.

===== Related Patterns =====

  * [[Social Tagging]]
  * [[ContentAlert]]

===== Further Reading =====

  * This contribution was initially taken from Using Wikis to Manage Use Cases: Experience and Outlook, page 113 of  [[http://www.se.uni-hannover.de/events/LSOplusRE/LSOplusRE-Proceedings-web-v1.0.pdf|Proceedings of Workshop on Learning Software Organizations and Requirements Engineering\]]