Why Wiki?
Why wiki?
Sort of a strange question by itself, but put another way : Why should you consider implementing a wiki when it comes to project management?
Wikis can be great communication and sharing tools, as well as helpful for collaboration on solving problems. But are those good enough reasons to start one? While a wiki has the potential to be a great asset to a project group, there are reasons where you may want to seriously re-evaluate the possibility (for example, there is a certain situation you are trying to address and you think the wiki will solve it). To justify the creation of a wiki, just as with the implementation of any new process or feature, there needs to be a supporting rationale to adopt it.
Content or Discontent
Part of that justification process will involve setting up a method in which to determine if the wiki, or parts thereof, accomplish specific goals. Areas could be designated as deliverable- specific, with success conditional and broken out based on the various elements that comprise a project. Other quantifiers may include soft measurable statistics such as individual member participation (number of posts, amount of content added, replies to other posts and so on) and group involvement (number of registered contributors, how many of those members are adding content, etc.).
And speaking of content, just who will be responsible for
Please log in or sign up below to read the rest of the article.
|
"You can't build a reputation on what you are going to do." - Henry Ford |




