<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Dariusz Grabka</title>
    <link>http://www.boxesandarrows.com/person/38646</link>
    <pubDate>Wed, 23 Sep 2009 20:21:54 GMT</pubDate>
    <description>Comments by Dariusz Grabka</description>
    <item>
      <description>&lt;p&gt;Thanks for the article Fred.  I agree very much that in organisations with waterfall methods (or remnants of waterfall methods), vetting ideas with prototypes of all levels of fidelity is very valuable.&lt;/p&gt;

	&lt;p&gt;In waterfall environments the cost of barking up the wrong design tree is extremely high, so the idea of iterating a few designs amongst the design and stakeholder teams typically receives warm feedback.  This is especially true if the UX, BA, or design professional has the ability to crank out some functional options.  This is where tools such as Axure, and other tools that facilitate &amp;#8220;highly functional&amp;#8221; prototypes, are very valuable.&lt;/p&gt;

	&lt;p&gt;One problem with waterfall structures is not that there&amp;#8217;s no -desire- for user feedback, but that the viable opportunities for it tend to be limited to requirements gathering.  Introducing new places to formally accept end-user feedback (such as a prototype vetting phase of design) may not be a hard sell for the organisation.&lt;/p&gt;

	&lt;p&gt;Thanks,&lt;br /&gt;D$&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/integrating#content_41471</link>
      <guid>http://www.boxesandarrows.com/view/integrating#content_41471</guid>
      <pubDate>Wed, 23 Sep 2009 20:21:54 GMT</pubDate>
      <author>Dariusz Grabka</author>
    </item>
  </channel>
</rss>

