<?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: Communication Trumps Checklists</title>
	<atom:link href="http://www.exubero.com/joe/2009/07/communication-trumps-checklists/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.exubero.com/joe/2009/07/communication-trumps-checklists/</link>
	<description>Follically Challenged in a Hirsute World</description>
	<lastBuildDate>Fri, 19 Feb 2010 14:32:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe</title>
		<link>http://www.exubero.com/joe/2009/07/communication-trumps-checklists/comment-page-1/#comment-504</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 05 Aug 2009 08:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.exubero.com/joe/?p=335#comment-504</guid>
		<description>In the last month I&#039;ve actually just enabled a large amount of automated checks at my current client, and will be bringing some more online soon. The group management here really like these reports, as it gives them a better handle on the quality of their codebase.

In the case of the 41 point checklist I mentioned, the idea was pushed as a way to &quot;improve quality&quot;. I don&#039;t believe it was an attempt to slow down development, but rather a reaction to the perceived quality problems highlighted by the reports. &quot;We must do something to improve quality. A checklist is something. Therefore be must use a checklist&quot;.</description>
		<content:encoded><![CDATA[<p>In the last month I&#8217;ve actually just enabled a large amount of automated checks at my current client, and will be bringing some more online soon. The group management here really like these reports, as it gives them a better handle on the quality of their codebase.</p>
<p>In the case of the 41 point checklist I mentioned, the idea was pushed as a way to &#8220;improve quality&#8221;. I don&#8217;t believe it was an attempt to slow down development, but rather a reaction to the perceived quality problems highlighted by the reports. &#8220;We must do something to improve quality. A checklist is something. Therefore be must use a checklist&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Fredrick</title>
		<link>http://www.exubero.com/joe/2009/07/communication-trumps-checklists/comment-page-1/#comment-500</link>
		<dc:creator>Jeffrey Fredrick</dc:creator>
		<pubDate>Wed, 05 Aug 2009 01:48:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.exubero.com/joe/?p=335#comment-500</guid>
		<description>PJ and I came to realization that development organizations with low quality reduce risk by slowing the pace of change. Fewer committed changes means fewer new defects! And a 41 point checklist is a great way to get there...

That said, I&#039;m actually in favor of checks, they should just be automated either in the build or by the build system.</description>
		<content:encoded><![CDATA[<p>PJ and I came to realization that development organizations with low quality reduce risk by slowing the pace of change. Fewer committed changes means fewer new defects! And a 41 point checklist is a great way to get there&#8230;</p>
<p>That said, I&#8217;m actually in favor of checks, they should just be automated either in the build or by the build system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie</title>
		<link>http://www.exubero.com/joe/2009/07/communication-trumps-checklists/comment-page-1/#comment-483</link>
		<dc:creator>Bernie</dc:creator>
		<pubDate>Fri, 31 Jul 2009 09:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.exubero.com/joe/?p=335#comment-483</guid>
		<description>The same problem in another situation is getting people at the pub to wash their hands after going to the toilet. ;-)

The culture of the developers needs to change. The process should be left as simple as possible.</description>
		<content:encoded><![CDATA[<p>The same problem in another situation is getting people at the pub to wash their hands after going to the toilet. ;-)</p>
<p>The culture of the developers needs to change. The process should be left as simple as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Simpson</title>
		<link>http://www.exubero.com/joe/2009/07/communication-trumps-checklists/comment-page-1/#comment-480</link>
		<dc:creator>Julian Simpson</dc:creator>
		<pubDate>Thu, 30 Jul 2009 13:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.exubero.com/joe/?p=335#comment-480</guid>
		<description>Hi Joe,

Last year I was told that I was now the &#039;gatekeeper of quality&#039; at the IT shop I was working in.  Let&#039;s ignore the fact that you can&#039;t inspect in quality.  I wrote a checklist and clung to it.  The checklist was for all the things that broke our deployments: sql files with the wrong encodings, with commands for the wrong version of the RDBMS, etc.  

It was murder.  But it did expose just how many releases weren&#039;t ready for prime time.  I got some automated tests going with CI so that developers got the feedback.  Some things (like hopelessly inadequate deployment instructions) can&#039;t really be checklisted, though.

It was a useful tool to help screen existing, broken work.  As a way of life?  Not on your nellie.</description>
		<content:encoded><![CDATA[<p>Hi Joe,</p>
<p>Last year I was told that I was now the &#8216;gatekeeper of quality&#8217; at the IT shop I was working in.  Let&#8217;s ignore the fact that you can&#8217;t inspect in quality.  I wrote a checklist and clung to it.  The checklist was for all the things that broke our deployments: sql files with the wrong encodings, with commands for the wrong version of the RDBMS, etc.  </p>
<p>It was murder.  But it did expose just how many releases weren&#8217;t ready for prime time.  I got some automated tests going with CI so that developers got the feedback.  Some things (like hopelessly inadequate deployment instructions) can&#8217;t really be checklisted, though.</p>
<p>It was a useful tool to help screen existing, broken work.  As a way of life?  Not on your nellie.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
