<?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: Pugh Decision Matrix</title>
	<atom:link href="http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Wed, 07 Jul 2010 10:00:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Total Design &#124; Lean Software Engineering</title>
		<link>http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/comment-page-1/#comment-1696</link>
		<dc:creator>Total Design &#124; Lean Software Engineering</dc:creator>
		<pubDate>Tue, 08 Jan 2008 19:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/#comment-1696</guid>
		<description>[...] than either of those. Pugh is remembered most often for his set-based development method of Pugh Concept Selection, but there is much more to his philosophy that just that. Principles of Total [...]</description>
		<content:encoded><![CDATA[<p>[...] than either of those. Pugh is remembered most often for his set-based development method of Pugh Concept Selection, but there is much more to his philosophy that just that. Principles of Total [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie</title>
		<link>http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/comment-page-1/#comment-26</link>
		<dc:creator>Bernie</dc:creator>
		<pubDate>Wed, 09 May 2007 04:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/#comment-26</guid>
		<description>Hi Rob! It&#039;s great that you&#039;re trying personal decisions against this.  I&#039;ve found that useful at times, too (but of course, sometimes it&#039;s overkill).

I think the criteria are best when they stay qualitative .. e.g. &quot;quick to set up (~2 hours or less)&quot;.  I wouldn&#039;t use setup time as a number/weighting directly on the sheet. You saw it getting you into trouble.

Pugh is most powerful when it is applied as a supporting dose of logical/objective yin, balancing the yang of your instincts.  Getting too serious or precise about the numbers will steer you (or a group) astray.  They can never be more than approximations -- so don&#039;t take them too seriously.

How to find the &quot;missing criteria&quot; when the current best result doesn&#039;t match instinct?

It&#039;s great to be at this point, because Pugh has brought you to the verge of an insight -- something important that you haven&#039;t been able to articulate about your instinctual decision -- or, perhaps, a realization that you&#039;ve found a new, better choice. 

Let us know how it goes!
Bernie</description>
		<content:encoded><![CDATA[<p>Hi Rob! It&#8217;s great that you&#8217;re trying personal decisions against this.  I&#8217;ve found that useful at times, too (but of course, sometimes it&#8217;s overkill).</p>
<p>I think the criteria are best when they stay qualitative .. e.g. &#8220;quick to set up (~2 hours or less)&#8221;.  I wouldn&#8217;t use setup time as a number/weighting directly on the sheet. You saw it getting you into trouble.</p>
<p>Pugh is most powerful when it is applied as a supporting dose of logical/objective yin, balancing the yang of your instincts.  Getting too serious or precise about the numbers will steer you (or a group) astray.  They can never be more than approximations &#8212; so don&#8217;t take them too seriously.</p>
<p>How to find the &#8220;missing criteria&#8221; when the current best result doesn&#8217;t match instinct?</p>
<p>It&#8217;s great to be at this point, because Pugh has brought you to the verge of an insight &#8212; something important that you haven&#8217;t been able to articulate about your instinctual decision &#8212; or, perhaps, a realization that you&#8217;ve found a new, better choice. </p>
<p>Let us know how it goes!<br />
Bernie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/comment-page-1/#comment-25</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Wed, 09 May 2007 01:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/05/07/pugh-decision-matrix/#comment-25</guid>
		<description>Cool!  Inspired by this, I used Pugh to decide how to upgrade one of my machines.  It said I should buy a whole new machine, so I like this process. 

Seriously, though, I&#039;d be curious about other rules of thumb: Should criteria be entirely qualitative? How do you know when you&#039;ve got the right criteria? (e.g. you&#039;re staring at the result and it doesn&#039;t match your intuition). If you have a quantitative criterion (e.g. time or cost), how do you express values for it?

E.g. one of my criteria was setup time.  I had 1.5h, 1.75h, 4.5h (baseline was do nothing, thus 0).  If I value these proportionally, I get -1,-1.7,-3.3.  That -3 has a huge effect.  Does it really make sense that this setup time disadvantage would outweigh three other positive advantages (if I mainly use +/-1)? I can see similar quandaries with cost, or any other criteria you choose where abs(value)&gt;1.  I could adjust the weight, but there&#039;s another, qualitative, scale - is a 3x increase in setup time really 3x worse to me?

How best to deal with these?

One additional thing I find useful: don&#039;t do the sums until you&#039;re happy with the matrix.  Without this, I&#039;d have skewed my way into a dual quad-core with 4 wheel drive and a flame job.  Even if I try to ignore sums, I&#039;ll unconsciously skew results towards favorites.</description>
		<content:encoded><![CDATA[<p>Cool!  Inspired by this, I used Pugh to decide how to upgrade one of my machines.  It said I should buy a whole new machine, so I like this process. </p>
<p>Seriously, though, I&#8217;d be curious about other rules of thumb: Should criteria be entirely qualitative? How do you know when you&#8217;ve got the right criteria? (e.g. you&#8217;re staring at the result and it doesn&#8217;t match your intuition). If you have a quantitative criterion (e.g. time or cost), how do you express values for it?</p>
<p>E.g. one of my criteria was setup time.  I had 1.5h, 1.75h, 4.5h (baseline was do nothing, thus 0).  If I value these proportionally, I get -1,-1.7,-3.3.  That -3 has a huge effect.  Does it really make sense that this setup time disadvantage would outweigh three other positive advantages (if I mainly use +/-1)? I can see similar quandaries with cost, or any other criteria you choose where abs(value)&gt;1.  I could adjust the weight, but there&#8217;s another, qualitative, scale &#8211; is a 3x increase in setup time really 3x worse to me?</p>
<p>How best to deal with these?</p>
<p>One additional thing I find useful: don&#8217;t do the sums until you&#8217;re happy with the matrix.  Without this, I&#8217;d have skewed my way into a dual quad-core with 4 wheel drive and a flame job.  Even if I try to ignore sums, I&#8217;ll unconsciously skew results towards favorites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.462 seconds -->
