<?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: The dilemma of &quot;good enough&quot; in software quality</title>
	<atom:link href="http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html</link>
	<description>Thoughts on IT architecture, governance, technology trends and the business value of IT</description>
	<lastBuildDate>Mon, 01 Mar 2010 14:25:03 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bola Rotibi</title>
		<link>http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html/comment-page-1#comment-345</link>
		<dc:creator>Bola Rotibi</dc:creator>
		<pubDate>Wed, 13 Aug 2008 09:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://mwdtemp.wordpress.com/2008/08/11/the-dilemma-of-good-enough-in-software-quality/#comment-345</guid>
		<description>Yes you are right, some things never change.  But then that&#039;s probably why we continue to see the same problems and frustration with delivered software applications and components over and over again.&lt;br/&gt;&lt;br/&gt;Good development teams and organisations look to break the cycle. Hard as this might be, I do however, believe that the benefits do in the short and long-term outweigh any upfront investment and resources applied to tackling the issue.  &lt;br/&gt;&lt;br/&gt;Of course there is a caveat to this and that is provided a carefully considered plan of approach and strategy to making those investments and committing the resources is followed.  As with anything that people look to change, a review of the existing environment to identify where the problems are along with a clear view of the goals is important to ensure the most effective outcome.</description>
		<content:encoded><![CDATA[<p>Yes you are right, some things never change.  But then that&#8217;s probably why we continue to see the same problems and frustration with delivered software applications and components over and over again.</p>
<p>Good development teams and organisations look to break the cycle. Hard as this might be, I do however, believe that the benefits do in the short and long-term outweigh any upfront investment and resources applied to tackling the issue.  </p>
<p>Of course there is a caveat to this and that is provided a carefully considered plan of approach and strategy to making those investments and committing the resources is followed.  As with anything that people look to change, a review of the existing environment to identify where the problems are along with a clear view of the goals is important to ensure the most effective outcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bola Rotibi</title>
		<link>http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html/comment-page-1#comment-347</link>
		<dc:creator>Bola Rotibi</dc:creator>
		<pubDate>Wed, 13 Aug 2008 09:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://mwdtemp.wordpress.com/2008/08/11/the-dilemma-of-good-enough-in-software-quality/#comment-347</guid>
		<description>Yes you are right, some things never change.  But then that&#039;s probably why we continue to see the same problems and frustration with delivered software applications and components over and over again.&lt;br/&gt;&lt;br/&gt;Good development teams and organisations look to break the cycle. Hard as this might be, I do however, believe that the benefits do in the short and long-term outweigh any upfront investment and resources applied to tackling the issue.  &lt;br/&gt;&lt;br/&gt;Of course there is a caveat to this and that is provided a carefully considered plan of approach and strategy to making those investments and committing the resources is followed.  As with anything that people look to change, a review of the existing environment to identify where the problems are along with a clear view of the goals is important to ensure the most effective outcome.</description>
		<content:encoded><![CDATA[<p>Yes you are right, some things never change.  But then that&#8217;s probably why we continue to see the same problems and frustration with delivered software applications and components over and over again.</p>
<p>Good development teams and organisations look to break the cycle. Hard as this might be, I do however, believe that the benefits do in the short and long-term outweigh any upfront investment and resources applied to tackling the issue.  </p>
<p>Of course there is a caveat to this and that is provided a carefully considered plan of approach and strategy to making those investments and committing the resources is followed.  As with anything that people look to change, a review of the existing environment to identify where the problems are along with a clear view of the goals is important to ensure the most effective outcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Baer</title>
		<link>http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html/comment-page-1#comment-344</link>
		<dc:creator>Tony Baer</dc:creator>
		<pubDate>Tue, 12 Aug 2008 19:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://mwdtemp.wordpress.com/2008/08/11/the-dilemma-of-good-enough-in-software-quality/#comment-344</guid>
		<description>Your research reminds me of a column that I wrote about a decade ago about the &quot;throw it over the wall&quot; mentality prevalent in software development. Developers just don&#039;t want to be caught dead doing QA if they can move on to the next exciting thing, and they have little respect for those that do. Some things just never change.</description>
		<content:encoded><![CDATA[<p>Your research reminds me of a column that I wrote about a decade ago about the &#8220;throw it over the wall&#8221; mentality prevalent in software development. Developers just don&#8217;t want to be caught dead doing QA if they can move on to the next exciting thing, and they have little respect for those that do. Some things just never change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Baer</title>
		<link>http://www.mwdadvisors.com/blog/2008/08/dilemma-of-good-enough-in-software.html/comment-page-1#comment-346</link>
		<dc:creator>Tony Baer</dc:creator>
		<pubDate>Tue, 12 Aug 2008 19:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://mwdtemp.wordpress.com/2008/08/11/the-dilemma-of-good-enough-in-software-quality/#comment-346</guid>
		<description>Your research reminds me of a column that I wrote about a decade ago about the &quot;throw it over the wall&quot; mentality prevalent in software development. Developers just don&#039;t want to be caught dead doing QA if they can move on to the next exciting thing, and they have little respect for those that do. Some things just never change.</description>
		<content:encoded><![CDATA[<p>Your research reminds me of a column that I wrote about a decade ago about the &#8220;throw it over the wall&#8221; mentality prevalent in software development. Developers just don&#8217;t want to be caught dead doing QA if they can move on to the next exciting thing, and they have little respect for those that do. Some things just never change.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
