Knowledge Management

We began with a problem, how to manage knowledge between team members. Note:both general and project status.

Things we tried:

    * paper documentation
    * common-access file system and Text editor files
    * Traditional webpages
    * Content Management Systems
    * Project management systems
    * wikiWiki

The negatives:

    * paper - updating, versioning and distribution
    * file systems - access and portability (ASCI)
    * webpages - updating
    * cms - updating
    * pm - interface, access

What we came to realize: The wiki offered the general access of a webpage with ease of update of a text file. This works because of trust

Ectrivia:

What is a WikiWiki?

http://lightblue.cats.ohiou.edu/snipsnap-1.0b1/space/start

self organizing

as users approach infinity, risk approach 0

more good guys than bad

?HyperCard was an important inspiriation for ?WardCunningham to come up with ?WikiWikiWeb.

The Wiki concept was invented by Ward Cunningham, and his first Wiki is still active. This Wiki shall be taken as the "reference implementation" for the purposes of this discussion.

The Wiki concept was invented by Ward Cunningham, and his first Wiki is still active. This Wiki shall be taken as the "reference implementation" for the purposes of this discussion.

social software, because it's a term that's still fairly amorphous. My definition is fairly simple: It's software that supports group interaction.

http://c2.com/cgi/wiki?TextFormattingRules''


Comments