<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: A report examining Twitter in the Enterprise</title>
	<atom:link href="http://www.fastforwardblog.com/2008/11/10/a-report-examining-twitter-in-the-enterprise/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2008/11/10/a-report-examining-twitter-in-the-enterprise/</link>
	<description></description>
	<lastBuildDate>Sat, 07 Nov 2009 18:38:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jordan Frank</title>
		<link>http://www.fastforwardblog.com/2008/11/10/a-report-examining-twitter-in-the-enterprise/comment-page-1/#comment-198087</link>
		<dc:creator>Jordan Frank</dc:creator>
		<pubDate>Tue, 09 Dec 2008 18:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=1206#comment-198087</guid>
		<description>I barely had  tweet of a thought about how Twitter would play in the enterprise until we added &lt;a href=&quot;http://traction.tractionsoftware.com/traction/permalink/Blog878&quot; title=&quot;Live Blog&quot; rel=&quot;nofollow&quot;&gt; to Traction TeamPage. Since then, a few obvious and immediate use cases have emerged in our own use (and I&#039;ve been experimenting on Twitter itself - though haven&#039;t quite figured out yet what to &quot;do&quot; there). 

First off, we setup a Live Forum (twitter style, using Live Blog) to complement our regular Forum (blog/wiki/discussion style). Interactions in Live Forum are shorter as you would expect, and more immediate. Answers offered to questions in Live Forum can easily leverage (via links) the rest of the content that is spread across documentation and support projects in Traction. 

We also setup a Live Blog project called Testing where we interact rapidly on issues encountered when trying out a new software release or feature. This replaces Jabber IM with the benefit that we can tag specific &quot;tweets&quot; for follow through tasking.

To your point about what customers will look at in &lt;a href=&quot;http://www.fastforwardblog.com/2008/09/15/will-you-twitter-inside-the-enterprise/&quot; title=&quot;Will you Twitter in the Enterprise&quot; rel=&quot;nofollow&quot;&gt;,&quot; I think the technology may get accepted more readily as part of an e2.0 platform that has all the relevant security, audit trail, access control, and policy issues worked out. One interesting and unexpected outcome is that some customers who do not have an approved IM platform can use tools like Live Blog for that sort of near-synchronous interactions.</description>
		<content:encoded><![CDATA[<p>I barely had  tweet of a thought about how Twitter would play in the enterprise until we added <a href="http://traction.tractionsoftware.com/traction/permalink/Blog878" title="Live Blog" rel="nofollow"> to Traction TeamPage. Since then, a few obvious and immediate use cases have emerged in our own use (and I&#8217;ve been experimenting on Twitter itself &#8211; though haven&#8217;t quite figured out yet what to &#8220;do&#8221; there). </p>
<p>First off, we setup a Live Forum (twitter style, using Live Blog) to complement our regular Forum (blog/wiki/discussion style). Interactions in Live Forum are shorter as you would expect, and more immediate. Answers offered to questions in Live Forum can easily leverage (via links) the rest of the content that is spread across documentation and support projects in Traction. </p>
<p>We also setup a Live Blog project called Testing where we interact rapidly on issues encountered when trying out a new software release or feature. This replaces Jabber IM with the benefit that we can tag specific &#8220;tweets&#8221; for follow through tasking.</p>
<p>To your point about what customers will look at in </a><a href="http://www.fastforwardblog.com/2008/09/15/will-you-twitter-inside-the-enterprise/" title="Will you Twitter in the Enterprise" rel="nofollow">,&#8221; I think the technology may get accepted more readily as part of an e2.0 platform that has all the relevant security, audit trail, access control, and policy issues worked out. One interesting and unexpected outcome is that some customers who do not have an approved IM platform can use tools like Live Blog for that sort of near-synchronous interactions.</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
