<?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 Gareth Morgan</title>
    <link>http://www.boxesandarrows.com/person/2915</link>
    <pubDate>Tue, 11 Aug 2009 23:48:27 GMT</pubDate>
    <description>Comments by Gareth Morgan</description>
    <item>
      <description>&lt;p&gt;Some good insight, thanks. However, having worked on and with teams that (have tried to) use both Agile techniques and wikis, and I have to say that in most cases, the wikis quickly become an incoherent warren of unstructured chaos. As has already been mentioned, wikis take an enormous amount of discipline to organize and keep tidy, which is more or less equivalent to saying a lot of time and effort. In my experience, this almost never happens consistently, particularly among Agile practitioners who adhere to the misconception that documenting one&amp;#8217;s objectives is optional. What has worked better? Well, basically anything that&amp;#8217;s (a) &lt;span class="caps"&gt;MUCH&lt;/span&gt; more visual, and (b) mandates that teams stick to an agreed framework.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/using-wikis-to#content_39726</link>
      <guid>http://www.boxesandarrows.com/view/using-wikis-to#content_39726</guid>
      <pubDate>Tue, 11 Aug 2009 23:48:27 GMT</pubDate>
      <author>Gareth Morgan</author>
    </item>
  </channel>
</rss>

