Wiki Patterns

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Assess Wiki-Ability ======

When using a wiki with a customer or client for the first time, check to see if they understand what it is and are open to using it. Using a Wiki and getting acquainted with its underlying philosophy might cause difficulties for "conservative" customers.

===== Usage =====

Customers might not be willing or able to use the Wiki. An indicator of problems is when a customer does not visit the wiki to review links sent around. If this happens, check with them as soon as you notice that they aren't editing or commenting on wiki pages that pertain to them.

===== Example =====

Clarify experience with Wiki when new customers join the project. If needed, show some customers how to use the Wiki or determine a team member to act as customer proxy. Clarify how reviews are done (e.g., by showing how to edit a Wiki page). Ask customers to set up their user homepage and provide a sandbox inside the Wiki.

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

  * [[Invitation]] - this is a great way to get a customer or client started using the wiki, and
  * [[Magnet]] - putting a critical mass of content on the wiki makes it the place to go for the most current information, but it's important to make sure people know how to use it and are willing to do so.

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

  * This contribution was generously contributed by the authors of //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\]]