<?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"
	>
<channel>
	<title>Comments on: Agile User Experience: If you have a silo, knock it down</title>
	<atom:link href="http://www.pathf.com/blogs/2008/01/agile-user-ex-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/01/agile-user-ex-1/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 18:23:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: David SL</title>
		<link>http://www.pathf.com/blogs/2008/01/agile-user-ex-1/#comment-122</link>
		<dc:creator>David SL</dc:creator>
		<pubDate>Wed, 12 Mar 2008 16:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=98#comment-122</guid>
		<description>&lt;p&gt;I couldn't agree more with your views on ensuring that workers in separate areas of a project need to be able to collaborate interactively. My company has designed a framework that facilitates this team collaboration in a distributed fashion from the ground up. The key lies in allowing the creation of implicit workflows that span individuals across different work groups. It allows individuals who may not necessarily have edit or publish permissions to view and comment on change requests between workers in other areas. This allows issues to be identified and eliminated before they become a problem while ensuring total visibility into the running of the process. &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more with your views on ensuring that workers in separate areas of a project need to be able to collaborate interactively. My company has designed a framework that facilitates this team collaboration in a distributed fashion from the ground up. The key lies in allowing the creation of implicit workflows that span individuals across different work groups. It allows individuals who may not necessarily have edit or publish permissions to view and comment on change requests between workers in other areas. This allows issues to be identified and eliminated before they become a problem while ensuring total visibility into the running of the process. </p>
]]></content:encoded>
	</item>
</channel>
</rss>
