<?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 UX and eyetracking</title>
	<atom:link href="http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/</link>
	<description>the personal website of Patrick Kennedy</description>
	<pubDate>Fri, 21 Nov 2008 09:49:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bookmarks about Eyetracking</title>
		<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-82080</link>
		<dc:creator>Bookmarks about Eyetracking</dc:creator>
		<pubDate>Tue, 02 Sep 2008 00:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-82080</guid>
		<description>[...] - bookmarked by 4 members originally found by sebkirche on 2008-08-14  Agile UX and eyetracking  http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/ - bookmarked by 6 members [...]</description>
		<content:encoded><![CDATA[<p>[...] - bookmarked by 4 members originally found by sebkirche on 2008-08-14  Agile UX and eyetracking  <a href="http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/" rel="nofollow">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/</a> - bookmarked by 6 members [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat</title>
		<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-76812</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Fri, 13 Jun 2008 03:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-76812</guid>
		<description>You're so bitter Shane :)</description>
		<content:encoded><![CDATA[<p>You&#8217;re so bitter Shane :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shane</title>
		<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-76796</link>
		<dc:creator>Shane</dc:creator>
		<pubDate>Fri, 13 Jun 2008 02:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-76796</guid>
		<description>I'm a big fan of agile, but you have to acknowldge the big dirty secret of Agile when it comes to UX.

They SAY it's agile, and don't worry UX guy - you can tweak/iterate/reinvent the UI in later sprints. In reality this is often not the case, because so long as a module is functionally complete, it is very hard to make a case for revisting the UI, even if your first pass was only half-baked. (unless you've been hit by the usability testing bus and have documentary evidence).

I guess this isn't the fault of agile in theory, it's just plain old human nature. Thing is, that's one of the selling points of agile methodologies, they are more compatible with human nature. Solution seems to be what we've been asking for for years, real influnce in the planning process (being able to play the UX card at critical points for example), rather than having to beg, borrow and steal UI enhanvements from the development team.

Ironic,
Shanemo</description>
		<content:encoded><![CDATA[<p>I&#8217;m a big fan of agile, but you have to acknowldge the big dirty secret of Agile when it comes to UX.</p>
<p>They SAY it&#8217;s agile, and don&#8217;t worry UX guy - you can tweak/iterate/reinvent the UI in later sprints. In reality this is often not the case, because so long as a module is functionally complete, it is very hard to make a case for revisting the UI, even if your first pass was only half-baked. (unless you&#8217;ve been hit by the usability testing bus and have documentary evidence).</p>
<p>I guess this isn&#8217;t the fault of agile in theory, it&#8217;s just plain old human nature. Thing is, that&#8217;s one of the selling points of agile methodologies, they are more compatible with human nature. Solution seems to be what we&#8217;ve been asking for for years, real influnce in the planning process (being able to play the UX card at critical points for example), rather than having to beg, borrow and steal UI enhanvements from the development team.</p>
<p>Ironic,<br />
Shanemo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat</title>
		<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-72590</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Fri, 06 Jun 2008 02:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-72590</guid>
		<description>&lt;p&gt;A thought provoking discussion as always, Angus :)&lt;/p&gt;
&lt;p&gt;I think it's crucial for UX to have an independent perspective from the design team, including visual and interaction design. Of course all design disciplines should be informed by the research and other outputs of the user experience expert, but there are advantages to this not being the same person. It's a balancing act, for sure, because ensuring the design process is benefiting from UX can be easiest if the two roles are the one person, but creativity of solution is found when they are separate.&lt;/p&gt;
&lt;p&gt;I think this is the case generally, as well as in the rapid environment of agile development. I actually followed up with John to ask about this topic, and whether it is more necessary to have this independence when talking about agile. He responded that it isn't any more important in agile, just easier to overlook in that situation. Makes sense since many things are easily overlooked when you're operating in such a fast paced, cut and thrust environment where usual practices are deliberately short-circuited.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>A thought provoking discussion as always, Angus :)</p>
<p>I think it&#8217;s crucial for UX to have an independent perspective from the design team, including visual and interaction design. Of course all design disciplines should be informed by the research and other outputs of the user experience expert, but there are advantages to this not being the same person. It&#8217;s a balancing act, for sure, because ensuring the design process is benefiting from UX can be easiest if the two roles are the one person, but creativity of solution is found when they are separate.</p>
<p>I think this is the case generally, as well as in the rapid environment of agile development. I actually followed up with John to ask about this topic, and whether it is more necessary to have this independence when talking about agile. He responded that it isn&#8217;t any more important in agile, just easier to overlook in that situation. Makes sense since many things are easily overlooked when you&#8217;re operating in such a fast paced, cut and thrust environment where usual practices are deliberately short-circuited.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: angusf</title>
		<link>http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-72153</link>
		<dc:creator>angusf</dc:creator>
		<pubDate>Thu, 05 Jun 2008 10:54:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.gurtle.com/ppov/2008/06/05/agile-ux-and-eyetracking/#comment-72153</guid>
		<description>Hi Pat

What is meant by "designer" in this point: "For best results in agile environments, UX expertise should be independent of designer (and client)". Visual designer? Interaction designer? Is it suggesting a separation between someone making/designing something and someone else expertly assessing it for UX/usability?</description>
		<content:encoded><![CDATA[<p>Hi Pat</p>
<p>What is meant by &#8220;designer&#8221; in this point: &#8220;For best results in agile environments, UX expertise should be independent of designer (and client)&#8221;. Visual designer? Interaction designer? Is it suggesting a separation between someone making/designing something and someone else expertly assessing it for UX/usability?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
