<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Thinking and Making: Comments by Dan Willis</title>
    <link>http://www.thinkingandmaking.com/person/28334</link>
    <pubDate>Fri, 07 Jan 2011 19:49:18 GMT</pubDate>
    <description>Comments by Dan Willis</description>
    <item>
      <description>&lt;p&gt;I&amp;#8217;m buying Austin&amp;#8217;s one sprint lag. The argument over the creation of story cycles &amp;gt;1 can actually be pretty simple: &amp;#8220;Okay,we can get the story cycle number back down, just add 4-6 weeks to the sprint.&amp;#8221; Nobody&amp;#8217;s going to want that.&lt;/p&gt;

	&lt;p&gt;There is one line in Austin&amp;#8217;s new post that I think is a little hinky. When he says &amp;#8220;Design and architecture &lt;span class="caps"&gt;CAN&lt;/span&gt;&amp;#8217;T be managed using agile methods&amp;#8221; I think an absolute statement like that wastes the most useful commonality between design and agile development, that they are both iterative. That&amp;#8217;s not a minor point.&lt;/p&gt;

	&lt;p&gt;In an agile environment, some part of the design solution should be flexible enough to allow for things that are discovered from one sprint to the next. This requires making an educated guess on the overall design so as not to hold each sprint&amp;#8217;s development hostage to that design.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-un#content_35510</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-un#content_35510</guid>
      <pubDate>Fri, 07 Jan 2011 19:49:18 GMT</pubDate>
      <author>Dan Willis</author>
    </item>
  </channel>
</rss>

