<?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 for My mind wanders...</title>
	<atom:link href="http://danrough.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://danrough.wordpress.com</link>
	<description></description>
	<lastBuildDate>Thu, 04 Jun 2009 08:40:40 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on One Piece Flow, One Piece At a Time by danrough</title>
		<link>http://danrough.wordpress.com/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>Comment on One Piece Flow, One Piece At a Time by David Joyce</title>
		<link>http://danrough.wordpress.com/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>
	<item>
		<title>Comment on The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn&#8217;t Exist by toby</title>
		<link>http://danrough.wordpress.com/2009/04/01/the-greatest-trick-the-devil-ever-pulled-was-making-people-believe-that-he-didnt-exist/#comment-1240</link>
		<dc:creator>toby</dc:creator>
		<pubDate>Thu, 02 Apr 2009 12:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=163#comment-1240</guid>
		<description>my advice to you would be to stop procrastinating and get on with it ;o)</description>
		<content:encoded><![CDATA[<p>my advice to you would be to stop procrastinating and get on with it ;o)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile: Like Fingernails On A Chalkboard by The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn&#8217;t Exist &#171; My mind wanders&#8230;</title>
		<link>http://danrough.wordpress.com/2008/05/16/agile-like-fingernails-on-a-chalkboard/#comment-1239</link>
		<dc:creator>The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn&#8217;t Exist &#171; My mind wanders&#8230;</dc:creator>
		<pubDate>Wed, 01 Apr 2009 11:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=129#comment-1239</guid>
		<description>[...] posted a while ago about the fact that I thought that all a team needed to be successful was a clear set [...]</description>
		<content:encoded><![CDATA[<p>[...] posted a while ago about the fact that I thought that all a team needed to be successful was a clear set [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Adoption &#8211; Just Say No by An Agile Adoption Pattern: Wax On, Wax Off &#171; My mind wanders&#8230;</title>
		<link>http://danrough.wordpress.com/2008/05/13/agile-adoption-just-say-no/#comment-1232</link>
		<dc:creator>An Agile Adoption Pattern: Wax On, Wax Off &#171; My mind wanders&#8230;</dc:creator>
		<pubDate>Mon, 27 Oct 2008 13:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=128#comment-1232</guid>
		<description>[...] On, Wax&#160;Off 27 October, 2008   I know I&#8217;ve said before that I don&#8217;t believe in an Agile Adoption initiative but humour me a little [...]</description>
		<content:encoded><![CDATA[<p>[...] On, Wax&nbsp;Off 27 October, 2008   I know I&#8217;ve said before that I don&#8217;t believe in an Agile Adoption initiative but humour me a little [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Adoption &#8211; Just Say No by Paulo Köch</title>
		<link>http://danrough.wordpress.com/2008/05/13/agile-adoption-just-say-no/#comment-1226</link>
		<dc:creator>Paulo Köch</dc:creator>
		<pubDate>Tue, 12 Aug 2008 20:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=128#comment-1226</guid>
		<description>Well, for a couple of reasons, firstly there are those people that you’ll come across that are naturally resistant to it and it’s better not to expose yourself to that pain in the first place and secondly, I don’t think that to be agile should be the end goal, sure business agility will deliver a lot of benefit to your organisation which they’ll thank you for but agile isn’t necessarily the only way to achieve that, by constantly reviewing what you’re doing and aspiring to do it better at all times you’ll deliver huge value, Dr Deming’s plan-do-check-act cycle (on which agile is loosely based) should help you there as a framework by which to carry that out.

Biggest sentence ever. Literally, there&#039;s only one period.</description>
		<content:encoded><![CDATA[<p>Well, for a couple of reasons, firstly there are those people that you’ll come across that are naturally resistant to it and it’s better not to expose yourself to that pain in the first place and secondly, I don’t think that to be agile should be the end goal, sure business agility will deliver a lot of benefit to your organisation which they’ll thank you for but agile isn’t necessarily the only way to achieve that, by constantly reviewing what you’re doing and aspiring to do it better at all times you’ll deliver huge value, Dr Deming’s plan-do-check-act cycle (on which agile is loosely based) should help you there as a framework by which to carry that out.</p>
<p>Biggest sentence ever. Literally, there&#8217;s only one period.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on It Was A Stone Groove&#8230; by danrough</title>
		<link>http://danrough.wordpress.com/2008/08/11/it-was-a-stone-groove/#comment-1225</link>
		<dc:creator>danrough</dc:creator>
		<pubDate>Tue, 12 Aug 2008 11:48:18 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=141#comment-1225</guid>
		<description>Thanks Rob, likewise make sure you keep in touch and let me know how things are going, I will of course continue to follow the blog.

Cheers</description>
		<content:encoded><![CDATA[<p>Thanks Rob, likewise make sure you keep in touch and let me know how things are going, I will of course continue to follow the blog.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on It Was A Stone Groove&#8230; by rob</title>
		<link>http://danrough.wordpress.com/2008/08/11/it-was-a-stone-groove/#comment-1224</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Mon, 11 Aug 2008 18:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=141#comment-1224</guid>
		<description>Was a pleasure dude. I look forward to hearing about all your new challenges. Good luck :)</description>
		<content:encoded><![CDATA[<p>Was a pleasure dude. I look forward to hearing about all your new challenges. Good luck <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile: Like Fingernails On A Chalkboard by danrough</title>
		<link>http://danrough.wordpress.com/2008/05/16/agile-like-fingernails-on-a-chalkboard/#comment-1222</link>
		<dc:creator>danrough</dc:creator>
		<pubDate>Wed, 25 Jun 2008 14:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=129#comment-1222</guid>
		<description>Right, which was my point, (which I might not have articulated all that well), applying a process is just applying a process, whether it&#039;s agile or waterfall, it&#039;s ignorant to the fact that most people on development teams want to do a good job. Give those teams the ability to be able to define how they think they can do that and let them know the parameters you expect them to be able to work within and let them get on with. BUT be there to support them if they make a mistake to ensure that they learn from it and don&#039;t make the same mistake again.</description>
		<content:encoded><![CDATA[<p>Right, which was my point, (which I might not have articulated all that well), applying a process is just applying a process, whether it&#8217;s agile or waterfall, it&#8217;s ignorant to the fact that most people on development teams want to do a good job. Give those teams the ability to be able to define how they think they can do that and let them know the parameters you expect them to be able to work within and let them get on with. BUT be there to support them if they make a mistake to ensure that they learn from it and don&#8217;t make the same mistake again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile: Like Fingernails On A Chalkboard by Gilles Ruppert</title>
		<link>http://danrough.wordpress.com/2008/05/16/agile-like-fingernails-on-a-chalkboard/#comment-1221</link>
		<dc:creator>Gilles Ruppert</dc:creator>
		<pubDate>Wed, 25 Jun 2008 14:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/?p=129#comment-1221</guid>
		<description>Agreed. On a positive note: we recently finished the 1st phase of a project &amp; it went really smoothly, with hardly any overtime at all. Good thing is that our TPM is always reigning us back in (esp. the client) when we try to go overboard/fall back into waterfall.

Still: educating the customer is very important (which we are trying to do) &amp; implementing all the goodness of Agile in big companies where processes can be lengthy is a challenge at best. Speaking to other developers in other big companies, I can only come to the conclusion that the implementation of agile is really on a per project base &amp; needs to be constantly adapted to satisfy the needs of the project. There is no &#039;One&#039; solution.</description>
		<content:encoded><![CDATA[<p>Agreed. On a positive note: we recently finished the 1st phase of a project &amp; it went really smoothly, with hardly any overtime at all. Good thing is that our TPM is always reigning us back in (esp. the client) when we try to go overboard/fall back into waterfall.</p>
<p>Still: educating the customer is very important (which we are trying to do) &amp; implementing all the goodness of Agile in big companies where processes can be lengthy is a challenge at best. Speaking to other developers in other big companies, I can only come to the conclusion that the implementation of agile is really on a per project base &amp; needs to be constantly adapted to satisfy the needs of the project. There is no &#8216;One&#8217; solution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
