<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clarrus &#187; Process</title>
	<atom:link href="http://www.clarrus.com/category/process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clarrus.com</link>
	<description>The Results are in the Team</description>
	<lastBuildDate>Mon, 05 Jul 2010 23:56:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Leveraging the Frog in the Pot</title>
		<link>http://www.clarrus.com/2010/07/leveraging-the-frog-in-the-pot/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=leveraging-the-frog-in-the-pot</link>
		<comments>http://www.clarrus.com/2010/07/leveraging-the-frog-in-the-pot/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 19:33:41 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Teamwork]]></category>
		<category><![CDATA[Change]]></category>
		<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1246</guid>
		<description><![CDATA[Everyone has heard of that metaphor of a frog in a pot of water: put the little guy in hot water and he&#8217;ll jump right out, heat the water gradually and he&#8217;ll just hang out there. The gradual changes are too subtle for him to perceive them and do anything about it. This explains why [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2010/07/leveraging-the-frog-in-the-pot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Work Breakdown Breakdown</title>
		<link>http://www.clarrus.com/2010/04/work-breakdown-breakdown/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=work-breakdown-breakdown</link>
		<comments>http://www.clarrus.com/2010/04/work-breakdown-breakdown/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 17:18:32 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Planning]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1230</guid>
		<description><![CDATA[One of the most useful tools to support consistency across projects is also one of the most misunderstood and widely overloaded tools: the work breakdown structure. Let&#8217;s tear this thing apart and look inside. First off, it is important to recognize that this WBS is a Work Breakdown Structure, not a Work Breakdown Schedule. What [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2010/04/work-breakdown-breakdown/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Rule of Three</title>
		<link>http://www.clarrus.com/2010/01/the-rule-of-three/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-rule-of-three</link>
		<comments>http://www.clarrus.com/2010/01/the-rule-of-three/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 03:07:57 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Change]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1177</guid>
		<description><![CDATA[When I first started focusing on improvement initiatives (over a dozen years ago now), the typical approach was to perform a deep analysis and come up with a big laundry list of recommended changes. That never did much more than pad the wallets of the consulting firm that provided the recommendations. For that reason alone, [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2010/01/the-rule-of-three/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Many Sources, One List</title>
		<link>http://www.clarrus.com/2010/01/many-sources-one-list/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=many-sources-one-list</link>
		<comments>http://www.clarrus.com/2010/01/many-sources-one-list/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 02:19:19 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Change]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1175</guid>
		<description><![CDATA[On any project, regardless of the size or complexity or uncertainty involved, there is one thing you know darned well to expect: things will change. To ignore or be surprised by potential changes is to set yourself up for heaps of trouble. It is important to recognize that change can come from many different directions. [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2010/01/many-sources-one-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Misguided Consistency</title>
		<link>http://www.clarrus.com/2009/12/misguided-consistency/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=misguided-consistency</link>
		<comments>http://www.clarrus.com/2009/12/misguided-consistency/#comments</comments>
		<pubDate>Sun, 06 Dec 2009 21:52:35 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Agility]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Teamwork]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1158</guid>
		<description><![CDATA[In almost every process improvement initiative I have seen, whether based on some sort of guidance (such as CMMI, ISO, RUP, Scrum, or&#8230;pick your favourite) or not, there is significant emphasis on standardization of process. PMO implementations usually provide a process binder, maybe a bunch of templates to complete on each project. Often, the people [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/12/misguided-consistency/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Top of Mind</title>
		<link>http://www.clarrus.com/2009/11/top-of-mind/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=top-of-mind</link>
		<comments>http://www.clarrus.com/2009/11/top-of-mind/#comments</comments>
		<pubDate>Sun, 15 Nov 2009 00:05:24 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1150</guid>
		<description><![CDATA[A few months ago, I posted some data that suggests that when we compare performance against different approaches to developing software, no particular brand stands out. Each approach appears to provide some net value in some area of performance, but there is no clear winner in the broad-based &#8220;this is the best way to develop [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/11/top-of-mind/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Best Foot Forward</title>
		<link>http://www.clarrus.com/2009/11/best-foot-forward/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=best-foot-forward</link>
		<comments>http://www.clarrus.com/2009/11/best-foot-forward/#comments</comments>
		<pubDate>Sat, 07 Nov 2009 21:43:45 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Change]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1146</guid>
		<description><![CDATA[There are many approaches that teams can take to improve. One thing that any team needs to understand before they should even try to get better is to understand why they would even bother to do so. There needs to be a clear and compelling reason for doing something different than they are currently doing, [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/11/best-foot-forward/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking Forward</title>
		<link>http://www.clarrus.com/2009/10/looking-forward/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=looking-forward</link>
		<comments>http://www.clarrus.com/2009/10/looking-forward/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 17:54:51 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Agility]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Teamwork]]></category>
		<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1135</guid>
		<description><![CDATA[As usual, heading down to Portland for the PNSQC conference this week provided me with a great deal of food for thought. This year, more than ever, I see signs that this industry might finally be maturing, getting over some of the bickering and posturing that seems to characterize the software sector more than anywhere [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/10/looking-forward/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Control and Management</title>
		<link>http://www.clarrus.com/2009/10/control-and-management/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=control-and-management</link>
		<comments>http://www.clarrus.com/2009/10/control-and-management/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 23:21:47 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Change]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1132</guid>
		<description><![CDATA[The terms Control and Management are often used interchangeably for a variety of activities in product development: configuration, change, risk, process, and so on. From my perspective, there is a difference between the attitude (implied or expressed) with these words, and for a couple of reasons, I tend to lean towards management over control. In [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/10/control-and-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Norms and Rules</title>
		<link>http://www.clarrus.com/2009/10/norms-and-rules/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=norms-and-rules</link>
		<comments>http://www.clarrus.com/2009/10/norms-and-rules/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 22:21:43 +0000</pubDate>
		<dc:creator>Jim Brosseau</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Change]]></category>
		<category><![CDATA[Culture]]></category>

		<guid isPermaLink="false">http://www.clarrus.com/?p=1130</guid>
		<description><![CDATA[I was chatting with someone the other day about my upcoming trip to Germany (I&#8217;m actually writing this one in the departure lounge). He was over there during the summer, and as a way of helping me ensure I had a good time, he noted &#8220;just remember, there are social norms over there, but there [...]]]></description>
		<wfw:commentRss>http://www.clarrus.com/2009/10/norms-and-rules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
