<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>agile-usability at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/agile-usability/</link>
    <description>Agile Usability</description>

    <item>
      <title>Re: New to Agile Usability</title>
      <pubDate>Thu, 19 Nov 2009 10:38:06 GMT</pubDate>
      <dc:creator>Mouneer</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6619</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6619</guid>
      <description>The start could be with roles listings: &quot;Usability expert&quot; UX designer UI developer Interactive designer In Agile teams general specialists are becoming the</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Thu, 19 Nov 2009 05:25:42 GMT</pubDate>
      <dc:creator>William Pietri</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6618</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6618</guid>
      <description>... The model I teach involves as much engagement as possible. That includes enough feedback during construction that any sort of end-of-iteration feedback is</description>
    </item>
    <item>
      <title>Re: Agile UX and Digital Marketing</title>
      <pubDate>Wed, 18 Nov 2009 17:13:50 GMT</pubDate>
      <dc:creator>flaviogrupos</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6617</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6617</guid>
      <description>Hello, I think that we can adapt most of the practices of Agile (XP, Scrum, TDD, etc.) The creative area (as IA, Design, Usability) are much cognitive than a</description>
    </item>
    <item>
      <title>Re: Agile UX SIG London: pub meetup</title>
      <pubDate>Wed, 18 Nov 2009 17:03:28 GMT</pubDate>
      <dc:creator>Adrian Howard</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6616</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6616</guid>
      <description>... A rather belated &quot;bloody good idea&quot;. I&#39;m going. Hope to see others from this list there too :-) Cheers, Adrian -- http://quietstars.com  -</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 04:56:14 GMT</pubDate>
      <dc:creator>George Dinwiddie</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6615</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6615</guid>
      <description>Hi, Scott, ... I couldn&#39;t tell you how common it is, but I&#39;ve seen it.  And it was a good thing.  Not only did they reach a resolution on differences in a </description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 02:35:25 GMT</pubDate>
      <dc:creator>Cindy Lu</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6614</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6614</guid>
      <description>Sorry for the late reply.  I don&#39;t have access to my personal emails at work and my evening is very short. See the my other post to John Schrag about</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 02:31:23 GMT</pubDate>
      <dc:creator>Mike Dwyer</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6613</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6613</guid>
      <description>It might be interesting to find out what the iteration strategy was and how it was changed as well as what the new designer did that was different.  Then,</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 02:08:35 GMT</pubDate>
      <dc:creator>Ron Jeffries</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6612</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6612</guid>
      <description>Hello, Cindy.  On Tuesday, November 17, 2009, at 8:47:08 PM, you ... Those MIGHT produce a better idea. I don&#39;t see that it will improve the idea&#39;s fit with</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 02:04:43 GMT</pubDate>
      <dc:creator>Ron Jeffries</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6611</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6611</guid>
      <description>Hello, Cindy.  On Tuesday, November 17, 2009, at 8:16:11 PM, you ... Of course you should do as you feel is best. I&#39;ve noticed, however, that every specialty</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 01:56:27 GMT</pubDate>
      <dc:creator>Cindy Lu</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6610</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6610</guid>
      <description>John, In one project, the client was not happy with the final design after many frequent iterations. For the same client and another project, we changed a</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 01:47:37 GMT</pubDate>
      <dc:creator>Cindy Lu</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6609</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6609</guid>
      <description>Hi! Ron, Thanks for sharing your thought. ... better, its expression to the team any better, or the team&#39;s willingness to do more changes and better? 1) to</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 01:32:42 GMT</pubDate>
      <dc:creator>Cindy Lu</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6608</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6608</guid>
      <description>... We always started with 2-3 design options.  Sometimes, none of them are satisfying so the designer started all over again.  For a most recent project,</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Wed, 18 Nov 2009 01:17:13 GMT</pubDate>
      <dc:creator>Cindy Lu</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6607</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6607</guid>
      <description>The stakholder(s) usually have very limited time.  So when we present to them, we want to make sure the idea is well thought out.  It does not mean the design</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Tue, 17 Nov 2009 16:37:54 GMT</pubDate>
      <dc:creator>Scott Preece</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6606</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6606</guid>
      <description>So, do you (and others on this list) think it would be common practice for the PO to be sitting with developers while they&#39;re writing code? My understanding</description>
    </item>
    <item>
      <title>Re: Agile vs. Creativity</title>
      <pubDate>Tue, 17 Nov 2009 15:51:27 GMT</pubDate>
      <dc:creator>Mike Dwyer</dc:creator>
      <link>http://tech.groups.yahoo.com/group/agile-usability/message/6605</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/agile-usability/message/6605</guid>
      <description>William Your citing the Dunning-Kruger effect highlights a core change that Agile and Scrum brings about.  The Dunning-Kruger effect is an example of the </description>
    </item>

  </channel>
</rss>
<!-- wr2.grp.sp2.yahoo.com uncompressed/chunked Thu Dec 17 22:12:30 PST 2009 -->
