<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Just enough</title>
	<atom:link href="http://www.onemanwrites.co.uk/2008/09/10/just-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onemanwrites.co.uk/2008/09/10/just-enough/</link>
	<description>musings on technical communications</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:40:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: UA Conference Notes - Day 1 &#124; one man writes</title>
		<link>http://www.onemanwrites.co.uk/2008/09/10/just-enough/comment-page-1/#comment-6111</link>
		<dc:creator>UA Conference Notes - Day 1 &#124; one man writes</dc:creator>
		<pubDate>Sun, 21 Sep 2008 16:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/?p=190#comment-6111</guid>
		<description>[...] then he hit on something that I&#8217;ve previously mentioned here (although Joe nailed it much better than I did), namely allocating writing resource to the highest [...]</description>
		<content:encoded><![CDATA[<p>[...] then he hit on something that I&#8217;ve previously mentioned here (although Joe nailed it much better than I did), namely allocating writing resource to the highest [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kai</title>
		<link>http://www.onemanwrites.co.uk/2008/09/10/just-enough/comment-page-1/#comment-5934</link>
		<dc:creator>Kai</dc:creator>
		<pubDate>Thu, 11 Sep 2008 09:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/?p=190#comment-5934</guid>
		<description>Gordon, I think learning from our own mistakes is one of the most effective, if painful learning experiences! So thanks for sharing and reminding me of it.

I&#039;m a bit uneasy with the question of how much documentation is &quot;enough&quot; or &quot;just enough&quot;. It feeds too much into the &quot;more faster&quot; frenzy. Maybe a better phrase would be &quot;good enough&quot;? Within time and project constraints, I&#039;d rather go for quality than quantity any day...

Incidentally, there was a related discussion over at Tom Johnson&#039;s blog: &quot;How Much Should You Document? Everything? Strategies for an Agile Environment&quot; (http://www.idratherbewriting.com/2008/09/09/how-much-should-you-document-strategies-for-an-agile-environment/).</description>
		<content:encoded><![CDATA[<p>Gordon, I think learning from our own mistakes is one of the most effective, if painful learning experiences! So thanks for sharing and reminding me of it.</p>
<p>I&#8217;m a bit uneasy with the question of how much documentation is &#8220;enough&#8221; or &#8220;just enough&#8221;. It feeds too much into the &#8220;more faster&#8221; frenzy. Maybe a better phrase would be &#8220;good enough&#8221;? Within time and project constraints, I&#8217;d rather go for quality than quantity any day&#8230;</p>
<p>Incidentally, there was a related discussion over at Tom Johnson&#8217;s blog: &#8220;How Much Should You Document? Everything? Strategies for an Agile Environment&#8221; (<a href="http://www.idratherbewriting.com/2008/09/09/how-much-should-you-document-strategies-for-an-agile-environment/" rel="nofollow">http://www.idratherbewriting.com/2008/09/09/how-much-should-you-document-strategies-for-an-agile-environment/</a>).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

