<?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/"
		>
<channel>
	<title>Comments on: 4 Simple Steps For Tailoring Your Methodology</title>
	<atom:link href="http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/</link>
	<description>Moving Beyond Management</description>
	<lastBuildDate>Mon, 16 Aug 2010 03:34:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Methodolo-what?? &#171; Management Straight Talk</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-317</link>
		<dc:creator>Methodolo-what?? &#171; Management Straight Talk</dc:creator>
		<pubDate>Thu, 22 Apr 2010 23:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-317</guid>
		<description>[...] Fewell, essentially titled “Methodology doesn’t matter.”&#160; You can read the gist of it here.&#160;&#160; The article itself didn’t quite go as far as the title, which was a little [...]</description>
		<content:encoded><![CDATA[<p>[...] Fewell, essentially titled “Methodology doesn’t matter.”&#160; You can read the gist of it here.&#160;&#160; The article itself didn’t quite go as far as the title, which was a little [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-205</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Wed, 20 Jan 2010 19:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-205</guid>
		<description>Ahhh. Nice distinction. My intent was to go after &quot;tailoring&quot;, rather than &quot;adapting&quot;. I guess I need to elaborate with some concrete examples.</description>
		<content:encoded><![CDATA[<p>Ahhh. Nice distinction. My intent was to go after &#8220;tailoring&#8221;, rather than &#8220;adapting&#8221;. I guess I need to elaborate with some concrete examples.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-204</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Wed, 20 Jan 2010 18:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-204</guid>
		<description>Jesse, I see tailoring as changing the methodology to align with the organization culture, adapting, on the other hand, is changing the organization culture to be fit with the methodology.</description>
		<content:encoded><![CDATA[<p>Jesse, I see tailoring as changing the methodology to align with the organization culture, adapting, on the other hand, is changing the organization culture to be fit with the methodology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-195</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Wed, 13 Jan 2010 14:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-195</guid>
		<description>PM Hut, I wonder what the difference is between tailoring and adapting. Aren&#039;t they the same thing? Namely, taking a methodololgy and adhering to the core essense, while customizing the parts that need to be fit to the current project&#039;s unique context.</description>
		<content:encoded><![CDATA[<p>PM Hut, I wonder what the difference is between tailoring and adapting. Aren&#8217;t they the same thing? Namely, taking a methodololgy and adhering to the core essense, while customizing the parts that need to be fit to the current project&#8217;s unique context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-192</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-192</guid>
		<description>This is another part of the methodology paradox: the value of a packaged product morphs into a marketing obsession. Just as organizations miss the improvement for the CMMi label, so pracitioners miss the effective management for the PMP or CSM label.</description>
		<content:encoded><![CDATA[<p>This is another part of the methodology paradox: the value of a packaged product morphs into a marketing obsession. Just as organizations miss the improvement for the CMMi label, so pracitioners miss the effective management for the PMP or CSM label.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-190</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Mon, 11 Jan 2010 22:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-190</guid>
		<description>I don&#039;t see much &quot;tailoring&quot; in this article as much as I see &quot;adapting&quot;. 

PS: I did publish a few years back a series on &lt;a href=&#039;http://www.pmhut.com/?s=%22Create+Your+Methodology+Based+on+a+Standard+Framework%22&#039; rel=&quot;nofollow&quot;&gt;creating your own methodology&lt;/a&gt;, the series is quite generic, but can be easily applied in the context of Project Management.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see much &#8220;tailoring&#8221; in this article as much as I see &#8220;adapting&#8221;. </p>
<p>PS: I did publish a few years back a series on <a href='http://www.pmhut.com/?s=%22Create+Your+Methodology+Based+on+a+Standard+Framework%22' rel="nofollow">creating your own methodology</a>, the series is quite generic, but can be easily applied in the context of Project Management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdrk60</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-189</link>
		<dc:creator>mdrk60</dc:creator>
		<pubDate>Mon, 11 Jan 2010 21:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-189</guid>
		<description>Thanks to all.
When deploying SW-CMM level 2 in a big company, I had issues with some people (e.g. sw quality assurance leader) who were so obsessed by CMM practices instead of real common sens practices. 
CMM is sometimes for the marketing image of the company.</description>
		<content:encoded><![CDATA[<p>Thanks to all.<br />
When deploying SW-CMM level 2 in a big company, I had issues with some people (e.g. sw quality assurance leader) who were so obsessed by CMM practices instead of real common sens practices.<br />
CMM is sometimes for the marketing image of the company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-186</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Sun, 10 Jan 2010 20:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-186</guid>
		<description>TV, I totally agree with your point about the intent and results of CMMI. Perhaps this is a common tragedy with most of these methodologies: what was intended to be an institutionalization of getting better, simply became institutionalization. It&#039;s a paradox I have yet to figure out.</description>
		<content:encoded><![CDATA[<p>TV, I totally agree with your point about the intent and results of CMMI. Perhaps this is a common tragedy with most of these methodologies: what was intended to be an institutionalization of getting better, simply became institutionalization. It&#8217;s a paradox I have yet to figure out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tathagat Varma</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-184</link>
		<dc:creator>Tathagat Varma</dc:creator>
		<pubDate>Sat, 09 Jan 2010 04:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-184</guid>
		<description>Jesse, and it is very heartening to see an eventual (inevitable ?) and definitive shift from being prescritive (whether Waterfall, CMM, PMI or Agile) to being pragmatic about how one should not go by the glossy marketing brochures of various snake-oil brands, but really go about tailoring the right solution from an quintessentially canned solution. You hit the nail on its head when you talk about tailoring. Incidentally, CMM was all about tailoring (especially at Level 3 and above) but sadly, people ignored that and only take home the perception that CMM is all about blind compliance to non-negotiable processes and documentation overkill. Similarly, Agile methods are built on the premise of &#039;inspect and adapt&#039; but sadly, that doesn&#039;t seem to apply to the very methods themselves! I find it not only strange, but tragic. A firm believer in &#039;horses for courses&#039;, I think it&#039;s about time we woke up to the real world and understood that customers couldn&#039;t care less what methodology we love, and any methodology is only as good as its results, not its pedigree.

~TV</description>
		<content:encoded><![CDATA[<p>Jesse, and it is very heartening to see an eventual (inevitable ?) and definitive shift from being prescritive (whether Waterfall, CMM, PMI or Agile) to being pragmatic about how one should not go by the glossy marketing brochures of various snake-oil brands, but really go about tailoring the right solution from an quintessentially canned solution. You hit the nail on its head when you talk about tailoring. Incidentally, CMM was all about tailoring (especially at Level 3 and above) but sadly, people ignored that and only take home the perception that CMM is all about blind compliance to non-negotiable processes and documentation overkill. Similarly, Agile methods are built on the premise of &#8216;inspect and adapt&#8217; but sadly, that doesn&#8217;t seem to apply to the very methods themselves! I find it not only strange, but tragic. A firm believer in &#8216;horses for courses&#8217;, I think it&#8217;s about time we woke up to the real world and understood that customers couldn&#8217;t care less what methodology we love, and any methodology is only as good as its results, not its pedigree.</p>
<p>~TV</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Fewell</title>
		<link>http://www.jessefewell.com/2010/01/08/4-simple-steps-for-tailoring-your-methodology/comment-page-1/#comment-182</link>
		<dc:creator>Jesse Fewell</dc:creator>
		<pubDate>Sat, 09 Jan 2010 01:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.jessefewell.com/?p=389#comment-182</guid>
		<description>I appreciate the affirmation. 

Hmm...How do you choose what to tailor? Well, in Step 2, choosing what to tailor should be driven first and foremost by a commitment to deliver. Many will immediately begin to shed a process document because it&#039;s just annoying, rather than asking what the impact would be to getting something approved and out the door. If your organization tells you that annoying document is needed for regulatory compliance, then in Step 3, you respond to that feedback by generating the thing. 

Yes, there is a huge sub-class of people that want to do color-by-numbers management. It can be argued that following all the rules all the time, alleviates the need to waste mental energy on the process, and focus on project delivery. However, when the process you started with (Step 1) starts to get in the way of delivery (Step 2), then you need to tailor away those obstacles to become more effective (Step 3). But, I guess I&#039;m starting to delve into another post about specifics.</description>
		<content:encoded><![CDATA[<p>I appreciate the affirmation. </p>
<p>Hmm&#8230;How do you choose what to tailor? Well, in Step 2, choosing what to tailor should be driven first and foremost by a commitment to deliver. Many will immediately begin to shed a process document because it&#8217;s just annoying, rather than asking what the impact would be to getting something approved and out the door. If your organization tells you that annoying document is needed for regulatory compliance, then in Step 3, you respond to that feedback by generating the thing. </p>
<p>Yes, there is a huge sub-class of people that want to do color-by-numbers management. It can be argued that following all the rules all the time, alleviates the need to waste mental energy on the process, and focus on project delivery. However, when the process you started with (Step 1) starts to get in the way of delivery (Step 2), then you need to tailor away those obstacles to become more effective (Step 3). But, I guess I&#8217;m starting to delve into another post about specifics.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
