<?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: Trickle vs Traditional</title>
	<atom:link href="http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/</link>
	<description>musings on technical communications</description>
	<pubDate>Tue, 07 Oct 2008 03:02:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Driving Development &#124; one man writes</title>
		<link>http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-5544</link>
		<dc:creator>Driving Development &#124; one man writes</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-5544</guid>
		<description>[...] eschew traditional writing processes and aim to grab and pillage information from wherever you can, trickling into what will become the final [...]</description>
		<content:encoded><![CDATA[<p>[...] eschew traditional writing processes and aim to grab and pillage information from wherever you can, trickling into what will become the final [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TanjaK</title>
		<link>http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-3072</link>
		<dc:creator>TanjaK</dc:creator>
		<pubDate>Thu, 01 May 2008 18:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-3072</guid>
		<description>Interesting reading, thanks for the tip! This is one more confirmation to what people were saying in a seminar that had several agile presentations. Things like modular documentation, reuse, and writing features (instead of products or books) are very well suited for an agile environment.</description>
		<content:encoded><![CDATA[<p>Interesting reading, thanks for the tip! This is one more confirmation to what people were saying in a seminar that had several agile presentations. Things like modular documentation, reuse, and writing features (instead of products or books) are very well suited for an agile environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: one man writes &#187; Trickle and Blink</title>
		<link>http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-1854</link>
		<dc:creator>one man writes &#187; Trickle and Blink</dc:creator>
		<pubDate>Sun, 20 Jan 2008 17:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/2007/09/19/trickle-vs-traditional/#comment-1854</guid>
		<description>[...] how to integrate an authoring team into an Extreme Programming (Agile) development group. The post Trickle vs Traditional outlined a basic way of building up the required content throughout the various stages of an XP [...]</description>
		<content:encoded><![CDATA[<p>[...] how to integrate an authoring team into an Extreme Programming (Agile) development group. The post Trickle vs Traditional outlined a basic way of building up the required content throughout the various stages of an XP [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
