<?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 Paul Sholar</title>
    <link>http://www.boxesandarrows.com/person/32056</link>
    <pubDate>Tue, 11 Aug 2009 23:47:51 GMT</pubDate>
    <description>Comments by Paul Sholar</description>
    <item>
      <description>&lt;p&gt;1. &amp;#8220;With wiki specs [UI spec sign-off] is unnecessary, since team members have been participating in writing the spec all along.&amp;#8221; I would say this is wishful thinking. This assumes that all significant team members have been participating fully in spec feedback all along the way. This certainly doesn&amp;#8217;t happen in a larger organization where key contributors often are involved in more than one important project simultaneously. I have seen that such a person typically gets involved toward the end of the project yet still is required to offer feedback and provide sign-off. Would like to see this scenario addressed in your manifesto.&lt;/p&gt;

	&lt;p&gt;2. My point of view is that most nontrivial apps are insufficiently well designed from the beginning, thereby making it very unlikely that proper and appropriately helpful user documentation can be developed and delivered by project end. The UI developer community needs to focus on coalescing around proven UI paradigms (patterns) and improving its own tools and techniques for spec&amp;#8217;ing and prototyping UI ideas before involving nondevelopers in the spec activity.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/using-wikis-to#content_40419</link>
      <guid>http://www.boxesandarrows.com/view/using-wikis-to#content_40419</guid>
      <pubDate>Tue, 11 Aug 2009 23:47:51 GMT</pubDate>
      <author>Paul Sholar</author>
    </item>
  </channel>
</rss>

