<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Power of The Wiki</title>
	<atom:link href="http://thefuturevalueofbusiness.com/the-power-of-the-wiki.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://thefuturevalueofbusiness.com/the-power-of-the-wiki.htm</link>
	<description>Using Business Intelligence to make data meaningful and solve business problems.</description>
	<lastBuildDate>Thu, 02 Sep 2010 18:39:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Scott Felten</title>
		<link>http://thefuturevalueofbusiness.com/the-power-of-the-wiki.htm/comment-page-1#comment-668</link>
		<dc:creator>Scott Felten</dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://thefuturevalueofbusiness.com/?p=165#comment-668</guid>
		<description>Forgot to mention that the biggest challange is to get this adopted from a social standpoint...getting people to understand how to use it and for what purpose. I started with a value proposition...this tool will allow us to do the following: 

1 - Centralize our information so that we can have one source of truth. No one wants to waste time performing tasks that are not needed or based on incorrect notions.

2 - We can keep our project moving when we are sleeping. By cooperating and committing to answering questions and resolving pending issues as they occur will help our team keep on schedule and allow us to focus better.

3 - When we bring new people on the team, we have less ramp up time because all of our information/progress/secrets are in fact open to learning.

4 - Its not set in stone...use the system, lets change what is klunky! Lets celebrate what works well.

5 - Lets hold each other accountable - since everything is out in the open, we are all committed at the team level. No hidden agendas, no surprises, its all out there!

~Scott Felten</description>
		<content:encoded><![CDATA[<p>Forgot to mention that the biggest challange is to get this adopted from a social standpoint&#8230;getting people to understand how to use it and for what purpose. I started with a value proposition&#8230;this tool will allow us to do the following: </p>
<p>1 &#8211; Centralize our information so that we can have one source of truth. No one wants to waste time performing tasks that are not needed or based on incorrect notions.</p>
<p>2 &#8211; We can keep our project moving when we are sleeping. By cooperating and committing to answering questions and resolving pending issues as they occur will help our team keep on schedule and allow us to focus better.</p>
<p>3 &#8211; When we bring new people on the team, we have less ramp up time because all of our information/progress/secrets are in fact open to learning.</p>
<p>4 &#8211; Its not set in stone&#8230;use the system, lets change what is klunky! Lets celebrate what works well.</p>
<p>5 &#8211; Lets hold each other accountable &#8211; since everything is out in the open, we are all committed at the team level. No hidden agendas, no surprises, its all out there!</p>
<p>~Scott Felten</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Felten</title>
		<link>http://thefuturevalueofbusiness.com/the-power-of-the-wiki.htm/comment-page-1#comment-667</link>
		<dc:creator>Scott Felten</dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://thefuturevalueofbusiness.com/?p=165#comment-667</guid>
		<description>I use TWiki to manage a global program development team that is made up 4 outsourced development vendors, 2 insourced development teams as well as internal analysts, SMEs and our sponsor of course. These people are from 10 different countries. The best benefit that I receive is to have a common place for documents that are shared by different users located in different parts of the world. So that we can follow the sun - having progress made constantly. One downfall is that if you don&#039;t address the outstanding issues the first part of the day, you loose that overlap work (when it&#039;s AM in NA and early afternoon in Europe). Asia presents a different challange - as we are 12 hours off. For this the answer is to never skip an opportunity to close a pending issue - least it cost you two days!

The challange for me was to organize the site so that people can depend upon areas for certain types of information (funcational, technical, pending issues, etc...)

The site carries the &#039;official&#039; or cannonized truths that the team builds upon.

You can read more about TWiki at http://en.wikipedia.org/wiki/TWiki or http://twiki.org/

I also love the &#039;WebChanges&#039; feature - where it brings up any document that has changed...reverse sorted by date!

And the history (versioning) for documents is also very excellent!

Good luck and have fun!</description>
		<content:encoded><![CDATA[<p>I use TWiki to manage a global program development team that is made up 4 outsourced development vendors, 2 insourced development teams as well as internal analysts, SMEs and our sponsor of course. These people are from 10 different countries. The best benefit that I receive is to have a common place for documents that are shared by different users located in different parts of the world. So that we can follow the sun &#8211; having progress made constantly. One downfall is that if you don&#8217;t address the outstanding issues the first part of the day, you loose that overlap work (when it&#8217;s AM in NA and early afternoon in Europe). Asia presents a different challange &#8211; as we are 12 hours off. For this the answer is to never skip an opportunity to close a pending issue &#8211; least it cost you two days!</p>
<p>The challange for me was to organize the site so that people can depend upon areas for certain types of information (funcational, technical, pending issues, etc&#8230;)</p>
<p>The site carries the &#8216;official&#8217; or cannonized truths that the team builds upon.</p>
<p>You can read more about TWiki at <a href="http://en.wikipedia.org/wiki/TWiki" rel="nofollow">http://en.wikipedia.org/wiki/TWiki</a> or <a href="http://twiki.org/" rel="nofollow">http://twiki.org/</a></p>
<p>I also love the &#8216;WebChanges&#8217; feature &#8211; where it brings up any document that has changed&#8230;reverse sorted by date!</p>
<p>And the history (versioning) for documents is also very excellent!</p>
<p>Good luck and have fun!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Johnson, Jr.</title>
		<link>http://thefuturevalueofbusiness.com/the-power-of-the-wiki.htm/comment-page-1#comment-563</link>
		<dc:creator>Daniel Johnson, Jr.</dc:creator>
		<pubDate>Tue, 24 Jun 2008 21:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://thefuturevalueofbusiness.com/?p=165#comment-563</guid>
		<description>So, Andy, what are some of your favorite wiki tools? I&#039;m experimenting with PB Wiki and WetPaint some.</description>
		<content:encoded><![CDATA[<p>So, Andy, what are some of your favorite wiki tools? I&#8217;m experimenting with PB Wiki and WetPaint some.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
