<?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: Pattern: The Never-Ending Story</title>
	<atom:link href="http://bfwa.com/2007/12/07/pattern-the-never-ending-story/feed/" rel="self" type="application/rss+xml" />
	<link>http://bfwa.com/2007/12/07/pattern-the-never-ending-story/</link>
	<description>We can help.</description>
	<lastBuildDate>Fri, 11 Mar 2011 04:09:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: The Wetware Crisis: the Thermocline of Truth : Bruce F. Webster</title>
		<link>http://bfwa.com/2007/12/07/pattern-the-never-ending-story/comment-page-1/#comment-6</link>
		<dc:creator>The Wetware Crisis: the Thermocline of Truth : Bruce F. Webster</dc:creator>
		<pubDate>Thu, 01 May 2008 01:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/2007/12/07/pattern-the-never-ending-story/#comment-6</guid>
		<description>[...] I have seen the same pattern repeatedly in IT systems failure lawsuits I have worked on, particularly when I&#8217;ve had large numbers of internal e-mails and memos to review. At times, I can identify right where the thermocline is and how it creeps up the management chain as the deadline draws near. In such cases, it usually doesn&#8217;t reach the top of the management chain (which, in the case of these lawsuits, means the developer notifying the customer) until shortly (&lt;1 month) before the reported deadline.  In fact,  this syndrome goes hand-in-hand with the IT system failure lawsuit pattern I call &#8220;The Never-Ending Story&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have seen the same pattern repeatedly in IT systems failure lawsuits I have worked on, particularly when I&#8217;ve had large numbers of internal e-mails and memos to review. At times, I can identify right where the thermocline is and how it creeps up the management chain as the deadline draws near. In such cases, it usually doesn&#8217;t reach the top of the management chain (which, in the case of these lawsuits, means the developer notifying the customer) until shortly (&lt;1 month) before the reported deadline.  In fact,  this syndrome goes hand-in-hand with the IT system failure lawsuit pattern I call &#8220;The Never-Ending Story&#8220;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Speaking of never-ending stories&#8230; : Webster &#38; Associates LLC</title>
		<link>http://bfwa.com/2007/12/07/pattern-the-never-ending-story/comment-page-1/#comment-4</link>
		<dc:creator>Speaking of never-ending stories&#8230; : Webster &#38; Associates LLC</dc:creator>
		<pubDate>Wed, 23 Jan 2008 18:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/2007/12/07/pattern-the-never-ending-story/#comment-4</guid>
		<description>[...] IT project out of Sydney appears to fit the bill: Ten years after it was first announced and almost $100 million later, Sydney is no closer to a [...]</description>
		<content:encoded><![CDATA[<p>[...] IT project out of Sydney appears to fit the bill: Ten years after it was first announced and almost $100 million later, Sydney is no closer to a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why software developers should spend time in SQA : Bruce F. Webster</title>
		<link>http://bfwa.com/2007/12/07/pattern-the-never-ending-story/comment-page-1/#comment-5</link>
		<dc:creator>Why software developers should spend time in SQA : Bruce F. Webster</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/2007/12/07/pattern-the-never-ending-story/#comment-5</guid>
		<description>[...] quality assurance (SQA). My experience is that many software projects get themselves into the &#8216;neverending story&#8217; pattern because of a lack of proper SQA &#8212; that is, the system under development never achieves the [...]</description>
		<content:encoded><![CDATA[<p>[...] quality assurance (SQA). My experience is that many software projects get themselves into the &#8216;neverending story&#8217; pattern because of a lack of proper SQA &#8212; that is, the system under development never achieves the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

