<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Comments on Agile + UX: six strategies for more agile user experience</title>
    <link>http://www.thinkingandmaking.com/view/agile-ux-six</link>
    <pubDate>Sun, 01 Jun 2008 01:51:19 GMT</pubDate>
    <description>Six ways to be more agile and better integrate user experience and information architecture into agile development teams.</description>
    <item>
      <description>&lt;p&gt;Brian,&lt;/p&gt;

	&lt;p&gt;I totally agree on our primary goal as UX practitioners. If I seemed casual, that&amp;#8217;s only because I don&amp;#8217;t think the UX is the most important part of working on a team. I think the most important part is working well together.&lt;/p&gt;

	&lt;p&gt;Every one on the team makes compromises. Working well means everyone understands the best compromises to make. That&amp;#8217;s why the team&amp;#8217;s design literacy is so important.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-six#content_21722</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-six#content_21722</guid>
      <pubDate>Sun, 01 Jun 2008 01:51:19 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;There are always ways to fit user experience design into any process. Will it be &amp;#8220;good&amp;#8221; design is another matter.&lt;/p&gt;

	&lt;p&gt;Several statements in this article trouble me and almost take a very &amp;#8220;casual&amp;#8221; attitude toward the resulting quality of the user experience. Agile was developed as a method of cranking out software quickly for the sake of monetary gain, &lt;span class="caps"&gt;NOT&lt;/span&gt; for the benefit of those who would ultimately have to use it.&lt;/p&gt;

	&lt;p&gt;Can &amp;#8220;good&amp;#8221; user experience design reside in an Agile process? Yes and no. It&amp;#8217;s all about the end goal of developing the software in the first place. Is the world a perfect place in which products are developed for purely altruistic purposes? No. But user experience design and user centered design techniques were created to make software easier to use, &lt;span class="caps"&gt;NOT&lt;/span&gt; faster to develop.&lt;/p&gt;

	&lt;p&gt;&amp;#8220;Fast&amp;#8221; is not necessarily &amp;#8220;good&amp;#8221; when it comes to the end user experience. The user does not know or care if software dev takes 15 days or 15 months however, they DO care if the software sucks.&lt;/p&gt;

	&lt;p&gt;Statements like &amp;#8220;bumping lower-priority items off the sprint&amp;#8221; sound good but what usually happens is that what gets&amp;#8221;bumped&amp;#8221; ends up being careful research and design thought and application of that thought.&lt;/p&gt;

	&lt;p&gt;As the Agile process continues to grow in popularity we, as user experience designers will need to find ways to incorporate best practices into that process. Austin Govella has done a great job of doing so in this article, however, we must not lose sight of the basic goals of why there are user experience designers and the most important element of creating software in the first place&amp;#8230;.the end user.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-six#content_21620</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-six#content_21620</guid>
      <pubDate>Fri, 30 May 2008 00:17:48 GMT</pubDate>
      <author>Brian Friesen</author>
    </item>
    <item>
      <description>&lt;p&gt;Austin: My 2 cents:  Want to be more agile. Run. I have taken a bluetooth device and talk about my product experience while running with my son Rayhaan. The voice gets captured in a recording device and then we use tools to convert it to text.&lt;/p&gt;

	&lt;pre&gt;&lt;code&gt;Thus while running our concepts are finalized and our health improves. How's this for agile buddy:). Your posts are improving by leaps and bounds. Will spend more time here! The only "rule" I have for my team is to workout once a day apart from the "be an angel "guideline".&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;

	&lt;p&gt;cheers&lt;br /&gt;&lt;a href="http://masoodnasser.blogpsot.com" rel="nofollow"&gt;http://masoodnasser.blogpsot.com&lt;/a&gt;&lt;br /&gt;&lt;a href="http://artinthemake.blogspot.com" rel="nofollow"&gt;http://artinthemake.blogspot.com&lt;/a&gt;&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-six#content_20916</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-six#content_20916</guid>
      <pubDate>Mon, 19 May 2008 04:16:09 GMT</pubDate>
      <author>Masood Nasser</author>
    </item>
    <item>
      <description>&lt;p&gt;This makes sense!  I&amp;#8217;m always being asked, &amp;#8220;How do you do UX in an agile environment?&amp;#8221;  My answer is always &amp;#8220;Take time to model your users first, then get settled into cyclic design.&amp;#8221;  You say this with #1 and #2 above.  The other four points all make sense from a team standpoint, as well, and I&amp;#8217;m glad to be able to point people to them.  Also, since modeling can take a long time, I offer several recommendations: study one user segment at a time, sketch the model based on shared knowledge, then test it with some real field work, etc.  More on step 2 here: &lt;a href="http://www.rosenfeldmedia.com/books/mental-models" rel="nofollow"&gt;www.rosenfeldmedia.com/books/mental-models&lt;/a&gt;.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-six#content_20781</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-six#content_20781</guid>
      <pubDate>Fri, 16 May 2008 00:54:14 GMT</pubDate>
      <author>Indi Young</author>
    </item>
  </channel>
</rss>
