<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Basil Vandegriend: Professional Software Development &#187; defects</title>
	<atom:link href="http://www.basilv.com/psd/blog/tag/defects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd</link>
	<description></description>
	<lastBuildDate>Wed, 08 Sep 2010 13:44:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Defect Prevention Practices</title>
		<link>http://www.basilv.com/psd/blog/2010/defect-prevention-practices</link>
		<comments>http://www.basilv.com/psd/blog/2010/defect-prevention-practices#comments</comments>
		<pubDate>Wed, 08 Sep 2010 13:44:40 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Productivity]]></category>
		<category><![CDATA[coding standards]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=549</guid>
		<description><![CDATA[I have written numerous times about defect elimination practices such as code reviews, unit testing, and static code analysis tools. From the perspective of lean thinking, however, eliminating defects, no matter how soon after they are introduced, results in waste due to rework to fix the defects. The ideal as far as lean is concerned [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/defect-prevention-practices/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Coding is not enough</title>
		<link>http://www.basilv.com/psd/blog/2010/why-coding-is-not-enough</link>
		<comments>http://www.basilv.com/psd/blog/2010/why-coding-is-not-enough#comments</comments>
		<pubDate>Mon, 28 Jun 2010 13:30:29 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=522</guid>
		<description><![CDATA[If the goal of software development is to produce working software then developers need to know more than just how to code - they need to know how to prevent or eliminate functional and non-functional defects.
Too many developers think their job is complete once a feature has been coded. Sometimes they think that it is [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/why-coding-is-not-enough/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why You Should Be Using FindBugs</title>
		<link>http://www.basilv.com/psd/blog/2009/why-you-should-be-using-findbugs</link>
		<comments>http://www.basilv.com/psd/blog/2009/why-you-should-be-using-findbugs#comments</comments>
		<pubDate>Mon, 02 Mar 2009 14:35:48 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[FindBugs]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=284</guid>
		<description><![CDATA[Build automation has been the theme of my recent learning activities, so when I came across multiple positive references to a tool called FindBugs I decided to give it a try. My conclusion: FindBugs is worth using on all Java projects. Read below for the details.
FindBugs is a Java static analysis tool that scans compiled [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/why-you-should-be-using-findbugs/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Errors Errors Everywhere</title>
		<link>http://www.basilv.com/psd/blog/2007/errors-errors-everywhere</link>
		<comments>http://www.basilv.com/psd/blog/2007/errors-errors-everywhere#comments</comments>
		<pubDate>Mon, 11 Jun 2007 14:22:30 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[error handling]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2007/errors-errors-everywhere</guid>
		<description><![CDATA[If you are a software developer and have not maintained operational applications with real users hammering away at it, then you are missing some important lessons. You might not fully appreciate the operational challenges facing the maintenance and support team, particularly when the software in question is suffering in the areas of reliability, performance, or [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2007/errors-errors-everywhere/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Examples of Root Cause Analysis</title>
		<link>http://www.basilv.com/psd/blog/2006/examples-of-root-cause-analysis</link>
		<comments>http://www.basilv.com/psd/blog/2006/examples-of-root-cause-analysis#comments</comments>
		<pubDate>Thu, 03 Aug 2006 15:00:27 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Professional]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[Learning]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2006/examples-of-root-cause-analysis</guid>
		<description><![CDATA[This article is a continuation of my previous article on how to do root cause analysis .  As I promised, this article provides examples of root cause analysis being performed.
A famous example of root cause analysis is the presidential commission's inquiry into the 1986 US Challenger space shuttle explosion, particularly the observations of Nobel [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2006/examples-of-root-cause-analysis/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How to do Root Cause Analysis</title>
		<link>http://www.basilv.com/psd/blog/2006/how-to-do-root-cause-analysis</link>
		<comments>http://www.basilv.com/psd/blog/2006/how-to-do-root-cause-analysis#comments</comments>
		<pubDate>Thu, 27 Jul 2006 15:00:52 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Professional]]></category>
		<category><![CDATA[continuous improvement]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[Learning]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2006/how-to-do-root-cause-analysis</guid>
		<description><![CDATA[Root cause analysis is an important activity whenever a problem occurs - whether it is a defect, an operational outage, or something else. Whatever the problem, your objective should be to not only resolve the issue but also prevent it from reoccurring in the future. To do this, you need to determine the root cause [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2006/how-to-do-root-cause-analysis/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>My Defect Fixing Process</title>
		<link>http://www.basilv.com/psd/blog/2006/my-defect-fixing-process</link>
		<comments>http://www.basilv.com/psd/blog/2006/my-defect-fixing-process#comments</comments>
		<pubDate>Thu, 22 Jun 2006 15:00:15 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[Learning]]></category>
		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2006/my-defect-fixing-process</guid>
		<description><![CDATA[What's your process for fixing a defect? What do you do when you are informed that a feature you developed isn't working to the users' satisfaction, or even worse fails to work at all? Here's what I do.

Initial investigation. My goal is to reproduce the reported problem in the application in my development environment. This [...]]]></description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2006/my-defect-fixing-process/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
