<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Suggested Best Practices?</title>
	<link>http://www.satisfice.com/blog/archives/73</link>
	<description>The Consulting Software Tester</description>
	<pubDate>Mon, 08 Sep 2008 04:31:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Christopher Ehlen</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-19280</link>
		<dc:creator>Christopher Ehlen</dc:creator>
		<pubDate>Fri, 29 Dec 2006 06:03:45 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-19280</guid>
		<description>Why does the term "best practices" get you so worked up?  If someone wants to share experiences and processes that have provided good results for them and their organization and they want to share it with rest of the world, who cares if they want to call it “best practices” or not.  Take what you can from the advice they have to offer and leave the rest behind.

&lt;em&gt;[James' Reply: "Best Practice" is not just an innocent expression. It's direct evidence of incompetence or lying or both. It corrodes our craft, to the point where the only people who aren't cynical about what almost anyone says about test methodology are people who don't know anything about it. I'd like to reverse the corrosion.&lt;/em&gt;

&lt;em&gt;At least within my community, I'd like to set a strong positive example of how competent and serious technical people should speak about methodology. Most of the world will ignore us, but more and more people will come to respect and trust us over time if we clean up our act.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Why does the term &#8220;best practices&#8221; get you so worked up?  If someone wants to share experiences and processes that have provided good results for them and their organization and they want to share it with rest of the world, who cares if they want to call it “best practices” or not.  Take what you can from the advice they have to offer and leave the rest behind.</p>
<p><em>[James&#8217; Reply: &#8220;Best Practice&#8221; is not just an innocent expression. It&#8217;s direct evidence of incompetence or lying or both. It corrodes our craft, to the point where the only people who aren&#8217;t cynical about what almost anyone says about test methodology are people who don&#8217;t know anything about it. I&#8217;d like to reverse the corrosion.</em></p>
<p><em>At least within my community, I&#8217;d like to set a strong positive example of how competent and serious technical people should speak about methodology. Most of the world will ignore us, but more and more people will come to respect and trust us over time if we clean up our act.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Phillips</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-16751</link>
		<dc:creator>Michael Phillips</dc:creator>
		<pubDate>Thu, 14 Dec 2006 15:27:35 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-16751</guid>
		<description>This is all very recognizable. Right now, I’m contracted to test in an organisation that wants me to follow their ‘Master Test Plan’ template, based on, yes, you’ve guessed; ‘Best Practices of TMap’. The template is 22 pages long, even without any content (!?!?!?!?). Having done my best to fill in only the mandatory sections, it becomes 31 pages. I now get comments sent back to me saying I should document and justify all the tests I’m NOT planning to carry out and providing justification for not filling in the paragraphs that I haven’t filled in. I’m a bit concerned here; this ‘best practice’ is going to lead to a 60 page plan, with no time for actually testing any software, which is what my customer has supposedly hired me to do.

Personally I think that the longer a plan gets, the less it reflects the real world. Thoughts?

&lt;em&gt;[James' Reply: I think your clients probably don't know what they are doing. In their ignorance they panic. They shield themselves with rhythmic patterns of ink, blessed by a technocratic priesthood. They chant and throw paper in the air, investing their resources in ways they hope will distract and confuse their tormentors. You are involved in a ritual, Michael. Whatever it means, it has little to do with testing.] &lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>This is all very recognizable. Right now, I’m contracted to test in an organisation that wants me to follow their ‘Master Test Plan’ template, based on, yes, you’ve guessed; ‘Best Practices of TMap’. The template is 22 pages long, even without any content (!?!?!?!?). Having done my best to fill in only the mandatory sections, it becomes 31 pages. I now get comments sent back to me saying I should document and justify all the tests I’m NOT planning to carry out and providing justification for not filling in the paragraphs that I haven’t filled in. I’m a bit concerned here; this ‘best practice’ is going to lead to a 60 page plan, with no time for actually testing any software, which is what my customer has supposedly hired me to do.</p>
<p>Personally I think that the longer a plan gets, the less it reflects the real world. Thoughts?</p>
<p><em>[James&#8217; Reply: I think your clients probably don&#8217;t know what they are doing. In their ignorance they panic. They shield themselves with rhythmic patterns of ink, blessed by a technocratic priesthood. They chant and throw paper in the air, investing their resources in ways they hope will distract and confuse their tormentors. You are involved in a ritual, Michael. Whatever it means, it has little to do with testing.] </em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Fredrick</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-10129</link>
		<dc:creator>Jeffrey Fredrick</dc:creator>
		<pubDate>Sat, 11 Nov 2006 14:44:53 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-10129</guid>
		<description>I agree completely, and now I get to state my punchline:  what best practices were to the 90s, patterns are becoming to the 00s, their context-free use justified because they appeared in print somewhere.

In fact, isn't using patterns a best practice?

&lt;em&gt;[James' Reply: I hear you. In my community, the word "pattern" has become slightly radioactive.] &lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I agree completely, and now I get to state my punchline:  what best practices were to the 90s, patterns are becoming to the 00s, their context-free use justified because they appeared in print somewhere.</p>
<p>In fact, isn&#8217;t using patterns a best practice?</p>
<p><em>[James&#8217; Reply: I hear you. In my community, the word &#8220;pattern&#8221; has become slightly radioactive.] </em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Fredrick</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-9176</link>
		<dc:creator>Jeffrey Fredrick</dc:creator>
		<pubDate>Tue, 07 Nov 2006 22:09:24 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-9176</guid>
		<description>and what if we replaced all instances of "best practice" with "pattern"?

Jtf

&lt;em&gt;[James' Reply: If we replace the phrase "best practice" with the word "pattern" and leave all else the same? Think about it... What would that do? I think it would make very little difference. Can you see why? (or if you you disagree, can you frame the argument on that side?)]
&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>and what if we replaced all instances of &#8220;best practice&#8221; with &#8220;pattern&#8221;?</p>
<p>Jtf</p>
<p><em>[James&#8217; Reply: If we replace the phrase &#8220;best practice&#8221; with the word &#8220;pattern&#8221; and leave all else the same? Think about it&#8230; What would that do? I think it would make very little difference. Can you see why? (or if you you disagree, can you frame the argument on that side?)]<br />
</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-8814</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Mon, 06 Nov 2006 09:50:33 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-8814</guid>
		<description>Hi,

I am a little confused about the first post:

You say you searched for:
1 - "suggested best practice" and
2 - "suggested best practices",
And then you say about differences in the results when omitting the word best (which seems to be in both queries).

"Suggested practices" search returns about 68k results and "suggested practice" about 38k

&lt;em&gt;[James' reply: I'm not talking about the differences in results. I'm talking about the fact that any results appear at all. In a world that uses words meaningfully, the queries I did should not return anything. The term "suggested practice" is fine. The term "suggested best practice" is, in most contexts, direct evidence that the term "best practice" has become marketing idiom instead of a meaningful phrase.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am a little confused about the first post:</p>
<p>You say you searched for:<br />
1 - &#8220;suggested best practice&#8221; and<br />
2 - &#8220;suggested best practices&#8221;,<br />
And then you say about differences in the results when omitting the word best (which seems to be in both queries).</p>
<p>&#8220;Suggested practices&#8221; search returns about 68k results and &#8220;suggested practice&#8221; about 38k</p>
<p><em>[James&#8217; reply: I&#8217;m not talking about the differences in results. I&#8217;m talking about the fact that any results appear at all. In a world that uses words meaningfully, the queries I did should not return anything. The term &#8220;suggested practice&#8221; is fine. The term &#8220;suggested best practice&#8221; is, in most contexts, direct evidence that the term &#8220;best practice&#8221; has become marketing idiom instead of a meaningful phrase.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael M. Butler</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-8352</link>
		<dc:creator>Michael M. Butler</dc:creator>
		<pubDate>Sat, 04 Nov 2006 03:59:29 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-8352</guid>
		<description>PS: My prior post has at least 20 too many words. :)</description>
		<content:encoded><![CDATA[<p>PS: My prior post has at least 20 too many words. <img src='http://www.satisfice.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael M. Butler</title>
		<link>http://www.satisfice.com/blog/archives/73#comment-8313</link>
		<dc:creator>Michael M. Butler</dc:creator>
		<pubDate>Fri, 03 Nov 2006 21:25:25 +0000</pubDate>
		<guid>http://www.satisfice.com/blog/archives/73#comment-8313</guid>
		<description>Overemployed catch phrases (that expression itself might be redundant) have been excoriated  by many, some of my favorites on the topic being Eric Blair ("George Orwell"), William Strunk, Jr., F. Scott Fitzgerald and Samuel Clemens ("Mark Twain"). 

If I thought simple mockery would avail anything, I'd blow off some steam by creating a "Best best practices" web page. Or write a "Practice Practical Best Best Practices Bestly" article for Stickynotes.

"Omit needless words. Vigorous writing is concise." -- W. Strunk, Jr., Chapter 13 of _Elements of Style_
link: http://www.bartleby.com/141/strunk5.html

The people who talk the "best practices" talk are often just Pointy-Haired Bosses (a la dilbert) or others trying to do verbal "primate grooming" and soothe one another, and the stockholders (or stakeholders). We've always had such bosses and such gullible stakeholders, and I expect we always will. Compare and contrast this with, say, "Management By Objective". _That_ too often turns into just another "I dictate, you perform" framework. "Management By Walking Around", likewise, turns into micromanagement with a figleaf.

"Best" anything is intended as a confidence builder. Just like the Emperor's wardrobe, it is rarely a sign of humility. The business culture doesn't especially reward humility; and it _sometimes_ punishes hubris. But businesspeople still egg each other on in these ways. And they rationalize that *this* instance of hubris is the *real* deal, not hubris at all. Sometimes I weep for the species.</description>
		<content:encoded><![CDATA[<p>Overemployed catch phrases (that expression itself might be redundant) have been excoriated  by many, some of my favorites on the topic being Eric Blair (&#8221;George Orwell&#8221;), William Strunk, Jr., F. Scott Fitzgerald and Samuel Clemens (&#8221;Mark Twain&#8221;). </p>
<p>If I thought simple mockery would avail anything, I&#8217;d blow off some steam by creating a &#8220;Best best practices&#8221; web page. Or write a &#8220;Practice Practical Best Best Practices Bestly&#8221; article for Stickynotes.</p>
<p>&#8220;Omit needless words. Vigorous writing is concise.&#8221; &#8212; W. Strunk, Jr., Chapter 13 of _Elements of Style_<br />
link: <a href="http://www.bartleby.com/141/strunk5.html" rel="nofollow">http://www.bartleby.com/141/strunk5.html</a></p>
<p>The people who talk the &#8220;best practices&#8221; talk are often just Pointy-Haired Bosses (a la dilbert) or others trying to do verbal &#8220;primate grooming&#8221; and soothe one another, and the stockholders (or stakeholders). We&#8217;ve always had such bosses and such gullible stakeholders, and I expect we always will. Compare and contrast this with, say, &#8220;Management By Objective&#8221;. _That_ too often turns into just another &#8220;I dictate, you perform&#8221; framework. &#8220;Management By Walking Around&#8221;, likewise, turns into micromanagement with a figleaf.</p>
<p>&#8220;Best&#8221; anything is intended as a confidence builder. Just like the Emperor&#8217;s wardrobe, it is rarely a sign of humility. The business culture doesn&#8217;t especially reward humility; and it _sometimes_ punishes hubris. But businesspeople still egg each other on in these ways. And they rationalize that *this* instance of hubris is the *real* deal, not hubris at all. Sometimes I weep for the species.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
