<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A few things I know about lean</title>
	<atom:link href="http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/feed/" rel="self" type="application/rss+xml" />
	<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/</link>
	<description>Mostly about the management of software development</description>
	<lastBuildDate>Mon, 23 Jan 2012 19:14:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Nik</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/#comment-338</link>
		<dc:creator><![CDATA[Nik]]></dc:creator>
		<pubDate>Fri, 25 Sep 2009 17:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-338</guid>
		<description><![CDATA[Hi Rupert. Having oversight from beginning to end is part of being lean, although just saying the developer should put it live doesn&#039;t make it lean of course. Just as important (possibly more so) is the team working together, and continually putting the features live. If the developer happens to be the last person in the chain that&#039;s fine; in the lean world that go-live action should be a continuously repeating step that&#039;s part of a flow.]]></description>
		<content:encoded><![CDATA[<p>Hi Rupert. Having oversight from beginning to end is part of being lean, although just saying the developer should put it live doesn&#8217;t make it lean of course. Just as important (possibly more so) is the team working together, and continually putting the features live. If the developer happens to be the last person in the chain that&#8217;s fine; in the lean world that go-live action should be a continuously repeating step that&#8217;s part of a flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rupert</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/#comment-337</link>
		<dc:creator><![CDATA[Rupert]]></dc:creator>
		<pubDate>Wed, 23 Sep 2009 19:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-337</guid>
		<description><![CDATA[Interesting stuff. The ideas surely apply beyond the actual production of the software to the processes involved in moving it into production. The way we work usually results in the developer being the one responsible for putting code live, which has caused a few raised eyebrows over the years, but does have a number of benefits, notably that if there are problems the developer is probably the person best placed to diagnose and fix them. This would seem to resonate with the ideas you&#039;ve outlined in this post.]]></description>
		<content:encoded><![CDATA[<p>Interesting stuff. The ideas surely apply beyond the actual production of the software to the processes involved in moving it into production. The way we work usually results in the developer being the one responsible for putting code live, which has caused a few raised eyebrows over the years, but does have a number of benefits, notably that if there are problems the developer is probably the person best placed to diagnose and fix them. This would seem to resonate with the ideas you&#8217;ve outlined in this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/#comment-336</link>
		<dc:creator><![CDATA[Nik]]></dc:creator>
		<pubDate>Fri, 11 Sep 2009 17:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-336</guid>
		<description><![CDATA[Thanks for that tip, Richard, I&#039;ll follow it up. The Toyota Way seems to switch between the process of producing individual cars with the process that produced the Prius prototype, and they&#039;re clearly different kinds of things.]]></description>
		<content:encoded><![CDATA[<p>Thanks for that tip, Richard, I&#8217;ll follow it up. The Toyota Way seems to switch between the process of producing individual cars with the process that produced the Prius prototype, and they&#8217;re clearly different kinds of things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Lord</title>
		<link>http://niksilver.com/2009/09/10/a-few-things-i-know-about-lean/#comment-335</link>
		<dc:creator><![CDATA[Richard Lord]]></dc:creator>
		<pubDate>Fri, 11 Sep 2009 10:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/?p=549#comment-335</guid>
		<description><![CDATA[When considering the transition of these principles from manufacturing to software development, it&#039;s well worth checking out the Toyota Product Development System. This is Toyota&#039;s product design process, as opposed to their more famous manufacturing process called the Toyota Production System.]]></description>
		<content:encoded><![CDATA[<p>When considering the transition of these principles from manufacturing to software development, it&#8217;s well worth checking out the Toyota Product Development System. This is Toyota&#8217;s product design process, as opposed to their more famous manufacturing process called the Toyota Production System.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

