<?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: One Piece Flow, One Piece At a Time</title>
	<atom:link href="http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/</link>
	<description></description>
	<lastBuildDate>Mon, 24 May 2010 08:36:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: danrough</title>
		<link>http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/#comment-1248</link>
		<dc:creator>danrough</dc:creator>
		<pubDate>Thu, 04 Jun 2009 08:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=169#comment-1248</guid>
		<description>Thanks David, it&#039;s a book that is on my list, a list which is ever growing at the moment as new and interesting techniques emerge.

I wonder, if you could take the time to outline the steps you take when setting a team up to use Kanban for Software Development? Perhaps this is something for a blog post from you or if not an email would be great.

It would be great if it covered:

How you define Standard Work, who&#039;s involved in the definition of it?

How do you get to an understanding of your Queue Limits?

Who&#039;s involved in Mapping the Value Stream?

How does the team know when to do a retrospective? What guidelines do you use for the Retrospectives, presumably they&#039;re happening a lot more often if you follow the stop the line mentality and in which case do you timebox them to a shorter period than an hour?

Anything else I&#039;ve missed?</description>
		<content:encoded><![CDATA[<p>Thanks David, it&#8217;s a book that is on my list, a list which is ever growing at the moment as new and interesting techniques emerge.</p>
<p>I wonder, if you could take the time to outline the steps you take when setting a team up to use Kanban for Software Development? Perhaps this is something for a blog post from you or if not an email would be great.</p>
<p>It would be great if it covered:</p>
<p>How you define Standard Work, who&#8217;s involved in the definition of it?</p>
<p>How do you get to an understanding of your Queue Limits?</p>
<p>Who&#8217;s involved in Mapping the Value Stream?</p>
<p>How does the team know when to do a retrospective? What guidelines do you use for the Retrospectives, presumably they&#8217;re happening a lot more often if you follow the stop the line mentality and in which case do you timebox them to a shorter period than an hour?</p>
<p>Anything else I&#8217;ve missed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Joyce</title>
		<link>http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/#comment-1247</link>
		<dc:creator>David Joyce</dc:creator>
		<pubDate>Wed, 03 Jun 2009 20:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=169#comment-1247</guid>
		<description>Can I suggest Corey Ladas Scrumban book, I think the answers to your questions may be in there.</description>
		<content:encoded><![CDATA[<p>Can I suggest Corey Ladas Scrumban book, I think the answers to your questions may be in there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
