<?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: Agile UXD</title>
	<atom:link href="http://pathfindersoftware.com/2007/05/agile_uxd/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathfindersoftware.com/2007/05/agile_uxd/</link>
	<description>The Fastest Way to Launch Successful Software</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alice Toth</title>
		<link>http://pathfindersoftware.com/2007/05/agile_uxd/#comment-6606</link>
		<dc:creator>Alice Toth</dc:creator>
		<pubDate>Fri, 08 Jun 2007 04:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-6606</guid>
		<description>&lt;p&gt;For me, one of the bigger challenges is having to design and develop before all of the business requirements are known. As you stated in your post, you don&#039;t really want to refactor the UI with each public release. &lt;/p&gt;

&lt;p&gt;So we need to create a UI that&#039;s flexible enough to accommodate change gracefully without necessarily knowing if the changes will be incremental or a 180. Naturally, this can be easier said than done. The key is having an entire team that&#039;s committed to having change (or iterations) as part of the process.&lt;/p&gt;

&lt;p&gt;The value with an agile UXD, however, outweighs any discomfort. We start getting user (including developer) feedback early in the development lifecycle where we can optimize the design or a workflow at less cost to the project. In the end, I believe we create a more usable product resulting in subsequent releases that can focus on features, not fixes.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>For me, one of the bigger challenges is having to design and develop before all of the business requirements are known. As you stated in your post, you don&#8217;t really want to refactor the UI with each public release. </p>
<p>So we need to create a UI that&#8217;s flexible enough to accommodate change gracefully without necessarily knowing if the changes will be incremental or a 180. Naturally, this can be easier said than done. The key is having an entire team that&#8217;s committed to having change (or iterations) as part of the process.</p>
<p>The value with an agile UXD, however, outweighs any discomfort. We start getting user (including developer) feedback early in the development lifecycle where we can optimize the design or a workflow at less cost to the project. In the end, I believe we create a more usable product resulting in subsequent releases that can focus on features, not fixes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://pathfindersoftware.com/2007/05/agile_uxd/#comment-6605</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 07 Jun 2007 22:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-6605</guid>
		<description>&lt;p&gt;Thanks for an interesting post. What are the biggest challenges you&#039;ve had so far in incorporating the Agile approach?&lt;/p&gt;

&lt;p&gt;I&#039;ve written on this topic before here:&lt;br /&gt;
&lt;a href=&quot;http://www.infoq.com/articles/agile-useability-churchville&quot; rel=&quot;nofollow&quot;&gt;http://www.infoq.com/articles/agile-useability-churchville&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Always curious how other pracitioners are merging UX and Agile methods.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for an interesting post. What are the biggest challenges you&#8217;ve had so far in incorporating the Agile approach?</p>
<p>I&#8217;ve written on this topic before here:<br />
<a href="http://www.infoq.com/articles/agile-useability-churchville" rel="nofollow">http://www.infoq.com/articles/agile-useability-churchville</a></p>
<p>Always curious how other pracitioners are merging UX and Agile methods.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (User agent is rejected)
Page Caching using memcached (User agent is rejected)

Served from: pathfindersoftware.com @ 2012-02-09 13:28:41 -->
