<?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 Stephanie A</title>
    <link>http://www.boxesandarrows.com/person/31298</link>
    <pubDate>Tue, 11 Aug 2009 23:48:41 GMT</pubDate>
    <description>Comments by Stephanie A</description>
    <item>
      <description>&lt;p&gt;I really appreciate this article, and Terry&amp;#8217;s point that Agile methodology is sometimes &amp;#8220;an excuse to not document &lt;span class="caps"&gt;ANYTHING&lt;/span&gt;.&amp;#8221; Finding a lightweight documentation method is the biggest problem I&amp;#8217;ve encountered so far &amp;#8211; and I do think a wiki might be the answer not just for a UI spec, but general requirements and details as well. We&amp;#8217;ve just deployed a SharePoint-based portal internally, with wiki functionality. It has its limitations, and it&amp;#8217;s certainly not the most robust wiki tool I&amp;#8217;ve seen, but it does allow multiple/separate wikis to be created and affiliated with specific projects, which is handy. Getting everyone else on the team to use it is a whole other problem!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/using-wikis-to#content_39722</link>
      <guid>http://www.boxesandarrows.com/view/using-wikis-to#content_39722</guid>
      <pubDate>Tue, 11 Aug 2009 23:48:41 GMT</pubDate>
      <author>Stephanie A</author>
    </item>
  </channel>
</rss>

