TWiki Collaboration Tool An Intranet Publishing Tool and

TWiki Collaboration Tool An Intranet Publishing Tool and Knowledge Base Tool Peter Thoeny Peter@Thoeny. com 1 -408 -255 -1477 http: //TWiki. org/

Agenda z Executive Summary z Challenges: Virtual Team, Intranet z Goals for TWiki Tool z Solution z Benefits of using TWiki z Limitations of TWiki z How to Learn TWiki z Collaboration Hints z Conclusions

Executive Summary z. TWiki is a web based collaboration tool, tailored for organizations with distributed offices. z. It is an integrated set of tools : y. A team based intranet publishing tool. y. A departmental collaboration tool. y. A publishing tool to maintain FAQ and KB on company web site.

Executive Summary (cont. ) z. Open Source software (GPL), hosted at http: //TWiki. org/ z. In use by many companies as a dynamic Intranet tool (CNN, Ericsson, Lucent, GE, GTE, Newbridge, Sun, TI, Motorola, Web. MD, . . . )

Executive Summary (cont. ) z. Tool highlights: y. Use your browser to create and change content (web pages. ) y. Content is a searchable and can be categorized. z. Competes with HTML publishing tools, e-mail, mailing lists and usenet.

Challenges: Virtual Team Challenges a R&D team faces that is distributed over several locations: KHow to brainstorm and work on new designs. KHow to synch different teams. KHow to avoid reinventing the wheel.

Challenges: Virtual Team (cont. ) Typical answers: J Scheduled conference calls & occasional visits. J Exchange documents by e-mail. But: L E-mail gets lost after some time, but content might be needed again in the future. L Searching e-mail is limited to email client. L E-mail is not hyper-linked and is not structured, content can’t easily be grouped into related topics. L E-mail is not version controlled, e. g. it is difficult to look at a document history.

Challenges: Intranet Content Static intranet sites are typically not very popular. This is because: LSome content is outdated. LThe quantity is limited. LContent is static, it has a "one webmaster syndrome. "

Challenges: Intranet Content (cont. ) Example of “one webmaster syndrome. “ : z. If I discover a page on the intranet that has incorrect or insufficient information, it is too complicated to find out who the webmaster is and to tell what should be changed. Result: Page typically will not get updated.

Goals for TWiki Tool We had these goals and requirements when we developed and deployed TWiki: z. Ease of use: y“I am not going to use a tool that is too cumbersome to use” z. Streamline the information flow between corporate offices, especially between factory and the field.

Goals (cont. ) z. Document centric environment, not tool centric. Type of content: y. Intranet content: Linked pages of product documentation, release notes and such. y. Knowledge Base (KB): Problem / Solution pairs. y. FAQ: Question / Answer pairs.

Goals (cont. ) z. Promote collaboration: y“Shared knowledge is more then the sum of its parts. ” y. Not one webmaster responsible for content, but each support engineer and field engineer is a webmaster. z. Self regulating system: y. Minimize tool administration. y. Automated FAQ and KB maintenance.

Goals (cont. ) z. Quality of Content: y. Peer review process that promotes accurate content. y. Used by all engineers on a daily basis ensures up to date information.

Goals (cont. ) z. Quantity of Content: y. Enough relevant data is needed to find a solution to a problem. y. Process that promotes feeding and maintaining content. z. Version Control of Content: y. Find out who changed what and when; see differences between versions; see previous versions of documents.

Solution: Web Based Collaboration z. TWiki is an “Instant Intranet”, or a web based publishing tool that allows anyone to easily add or change content by just using a web browser: y. Browse and search content. y. Create and change web pages. y. Classify web pages, for example as public FAQ, KB or confidential.

Solution: Ease of Use z. Web pages are linked automatically, no more “ 404 page not found” errors. z. Create new pages by simply entering a topic name and filling out details. z. File attachments: Add files to a page, like an email attachment.

Solution: Interactive Tool z. Add content “Share Knowledge” z. Notification of changes: y. Get notified of page changes by email. y. A way to keep everybody in synch. y. It is also a way to check content by senior engineers. z. Peer review for up to date content: y. Fix a posting that is inaccurate or insufficient.

Solution: Quality and Quantity z. Quality: y. User is empowered and encouraged to make changes to content. y. Email notification promotes review. y. Up to date information (we eliminated the “one webmaster syndrome”) z. Quantity: y. Ease of use promotes contributions. y. Statistics with “top contributor list” can be used for an incentive program.

Solution: Categorization z Pages can be edited in free form. z In addition, each page has meta data, which classifies and categorizes a page. z Classify: y. Declare a page as confidential, public FAQ, or public KB entry. y. Public pages will be published. z Categorize: y. Additional meta data like a product category.

Sample Screen Shot

Solution: Version Control z. Pages are under version control: y. See previous page revisions. y. See differences between revisions. y. See who changed what and when.

Case Study: Motorola z. Motorola UK uses TWiki for the Systems-on-Chip Design Technology. y. Crawford Currie of Motorola: "We are now hosting 7 different [TWiki] webs, extending the 'team' from an on-site project team to a virtual team including members in Germany, UK, France, Australia, Russia and the US, with about 60 regular contributors (and growing). "

Case Study: Motorola (cont. ) z. The TWiki tool helped Motorola’s virtual teams to work efficiently on requirements capture, issues lists and internal documentation.

Benefits of using TWiki z Improved communication for a virtual team èDocumentation that is in synch with project. èAccurate content because of peer review. èEliminate the “one webmaster syndrome” èEmpowered engineers are motivated to contribute. z Web based 1. No additional publishing tools needed. 2. No client side tools to update.

Limitations of TWiki is a purely web based tool. This has the following implications: z The editor is simply an HTML form; browser editors are not very sophisticated. z Non WYSIWYG editing; nevertheless rich text can be written using a very simple markup language (Wiki. Syntax). Example: make text appear in *bold* or in =fixed font=. (This is basically how you write an email)

How to Learn TWiki z. It takes about 30 minutes to learn TWiki. z. First read Welcome. Guest in the TWiki web. z. Then study the TWiki. Tutorial. Short demo of basic features.

Collaboration Hints: E-mail and Mailing Lists vs. TWiki z Tools should be used where appropriate: z E-mail and mailing lists: y. Short lived information like meeting announcements y. Sensitive data that should not reach everybody z TWiki web: y. Anything that is more permanent like discussions or documents y. Reason: Version control, search and accountability

Collaboration Hints: Software Projects z Each software project has its own TWiki collaboration web (name space) to y. Discuss and capture design ideas and requirements y. Document all aspects of the project z One person should be the designated "collaboration coach" who promotes best practices (but not webmaster) z Team members should bookmark the Web. Home page and subscribe in Web. Notify.

Collaboration Hints: Organize Projects z Define a category table for the TWiki web to help organize the content. One common way is to define subcategories by tool, i. e. define a Tool. Category that can be set to Editor. Tool, Simulation. Tool and so on. z Each tool has it’s own index page. z Each web page can be categorized; content can be listed or searched based on the category.

Collaboration Hints: Organize Projects (cont. ) z. For each Tool. Category index page define sections with bullet lists: y. Document list: Content that is well defined, or on the way to be well defined, i. e. a design document. y. Discussion list: Content that is in a preliminary state where team members collaborate on. y. Team list: Team members.

Conclusions z. The TWiki tool covers most of the documentation and knowledge management needs for the corporate Intranet world.