<?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"
	>
<channel>
	<title>Comments on: No Docs = No Product</title>
	<atom:link href="http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/</link>
	<description>musings on technical communications</description>
	<pubDate>Mon, 13 Oct 2008 12:51:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: one man writes &#187; Web apps are not products</title>
		<link>http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1960</link>
		<dc:creator>one man writes &#187; Web apps are not products</dc:creator>
		<pubDate>Wed, 30 Jan 2008 16:20:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1960</guid>
		<description>[...] Let me repeat what I said previously: [...]</description>
		<content:encoded><![CDATA[<p>[...] Let me repeat what I said previously: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah</title>
		<link>http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1908</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Sat, 26 Jan 2008 23:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1908</guid>
		<description>Completely agree that no docs = no product. In fact, technical writers are the caretakers of life, the universe, and everything ;)

I'm lucky enough to be working for a company which totally gets documentation. But I have had less fortunate experiences in the past.

And currently, I'm in a very *agile* environment. It's a lot of fun, and very rewarding. We're a team of tech writers, and we're continually on the move and adapting the way we work as well as the docs themselves, to suit the agile environment.

Synchronicity rocks. Often the tech writers and the engineers find themselves working on the same aspect of the product, even when that's *not* planned.

Seeya on the page :)</description>
		<content:encoded><![CDATA[<p>Completely agree that no docs = no product. In fact, technical writers are the caretakers of life, the universe, and everything ;)</p>
<p>I&#8217;m lucky enough to be working for a company which totally gets documentation. But I have had less fortunate experiences in the past.</p>
<p>And currently, I&#8217;m in a very *agile* environment. It&#8217;s a lot of fun, and very rewarding. We&#8217;re a team of tech writers, and we&#8217;re continually on the move and adapting the way we work as well as the docs themselves, to suit the agile environment.</p>
<p>Synchronicity rocks. Often the tech writers and the engineers find themselves working on the same aspect of the product, even when that&#8217;s *not* planned.</p>
<p>Seeya on the page :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon McLean</title>
		<link>http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1894</link>
		<dc:creator>Gordon McLean</dc:creator>
		<pubDate>Fri, 25 Jan 2008 08:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1894</guid>
		<description>Where I am at present, the technical writers are well integrated into the development teams and we manage to produce some pretty good documentation by staggering (trickling as I call it) the information in throughout the dev cycle.

I think XP has a place, but I think there needs to be some additional thought on the information debt being built-up by software companies that don't agree with the title of this post.

Thankfully I'm not working at such place, nor have I!</description>
		<content:encoded><![CDATA[<p>Where I am at present, the technical writers are well integrated into the development teams and we manage to produce some pretty good documentation by staggering (trickling as I call it) the information in throughout the dev cycle.</p>
<p>I think XP has a place, but I think there needs to be some additional thought on the information debt being built-up by software companies that don&#8217;t agree with the title of this post.</p>
<p>Thankfully I&#8217;m not working at such place, nor have I!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kat</title>
		<link>http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1892</link>
		<dc:creator>Kat</dc:creator>
		<pubDate>Fri, 25 Jan 2008 07:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2008/01/24/no-docs-no-product/#comment-1892</guid>
		<description>Some people believe that XP is the Emperor's New Clothes of software development, and one of its shortcomings is that it by definition undermines the role of documentation. 

Management like it coz it's cheap and they don't want to spend money on a QS, and developers don't like writing. Matt Stephen's discusses docs in his XP critique:

"XP makes a big issue about its core value of Communication. This is wonderful, as communication is definitely a key factor to the success of any project, XP or otherwise.

Unfortunately, XP also makes a big issue about not doing any documentation (or at least very little, or none at all). I think this is partly why XP has such a broad appeal amongst earnest young programmers. After all, documentation really sucks, right? Just like homework always sucked."

You can read his full review at:
http://www.softwarereality.com/lifecycle/xp/case_against_xp.jsp</description>
		<content:encoded><![CDATA[<p>Some people believe that XP is the Emperor&#8217;s New Clothes of software development, and one of its shortcomings is that it by definition undermines the role of documentation. </p>
<p>Management like it coz it&#8217;s cheap and they don&#8217;t want to spend money on a QS, and developers don&#8217;t like writing. Matt Stephen&#8217;s discusses docs in his XP critique:</p>
<p>&#8220;XP makes a big issue about its core value of Communication. This is wonderful, as communication is definitely a key factor to the success of any project, XP or otherwise.</p>
<p>Unfortunately, XP also makes a big issue about not doing any documentation (or at least very little, or none at all). I think this is partly why XP has such a broad appeal amongst earnest young programmers. After all, documentation really sucks, right? Just like homework always sucked.&#8221;</p>
<p>You can read his full review at:<br />
<a href="http://www.softwarereality.com/lifecycle/xp/case_against_xp.jsp" rel="nofollow">http://www.softwarereality.com/lifecycle/xp/case_against_xp.jsp</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
