<?xml version="1.0" encoding="UTF-8"?>
<rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Basil Vandegriend: Professional Software Development</title>
	
	<link>http://www.basilv.com/psd</link>
	<description />
	<lastBuildDate>Mon, 01 Mar 2010 14:11:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ProfessionalSoftwareDevelopment" /><feedburner:info uri="professionalsoftwaredevelopment" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><image><link>http://www.basilv.com/psd/</link><url>http://www.basilv.com/psd/wp-content/themes/bvpsd/images/gears.gif</url><title>Professional Software Development</title></image><item>
		<title>Problems with Typical Definitions of Project Success</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/yQYquWJZS2o/problems-with-typical-definitions-of-project-success</link>
		<comments>http://www.basilv.com/psd/blog/2010/problems-with-typical-definitions-of-project-success#comments</comments>
		<pubDate>Mon, 01 Mar 2010 14:11:01 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=494</guid>
		<description>My previous article discussed the importance of defining success as it relates to software projects and products. Now I want to look at some typical definitions of success and identify problems or short-comings with these definitions. From this analysis I aim to point the way towards a better definition of what success entails. 
Typical Definitions [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/yQYquWJZS2o" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/problems-with-typical-definitions-of-project-success/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2010/problems-with-typical-definitions-of-project-success</feedburner:origLink></item>
		<item>
		<title>Avoiding Caching To Improve Hibernate Performance</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/pDWkSvQwcC0/avoiding-caching-to-improve-hibernate-performance</link>
		<comments>http://www.basilv.com/psd/blog/2010/avoiding-caching-to-improve-hibernate-performance#comments</comments>
		<pubDate>Mon, 08 Feb 2010 14:18:54 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Professional]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Hibernate]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=486</guid>
		<description>I was recently doing some performance tuning and made the surprising discovery that doing less caching in Hibernate actually improved performance in a particular scenario. When I discovered the problem this seemed very counter-intuitive. In fact, my original design maximized the use of caching in order to improve performance, but the opposite happened in practice. [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/pDWkSvQwcC0" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/avoiding-caching-to-improve-hibernate-performance/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2010/avoiding-caching-to-improve-hibernate-performance</feedburner:origLink></item>
		<item>
		<title>The Importance of Defining Success</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/SzxY767PpeU/the-importance-of-defining-success</link>
		<comments>http://www.basilv.com/psd/blog/2010/the-importance-of-defining-success#comments</comments>
		<pubDate>Mon, 25 Jan 2010 14:00:08 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[IT industry]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=482</guid>
		<description>Can you define what makes a successful software development project or product? Do you know the criteria by which your current assignment will be judged a success? Does everyone associated with the project or product share the same definition? Defining what it means to be successful may seem obvious or trivial, but I expect that [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/SzxY767PpeU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/the-importance-of-defining-success/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2010/the-importance-of-defining-success</feedburner:origLink></item>
		<item>
		<title>How to Become an Expert Developer</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/WyNLxuiiUgo/how-to-become-an-expert-developer</link>
		<comments>http://www.basilv.com/psd/blog/2010/how-to-become-an-expert-developer#comments</comments>
		<pubDate>Tue, 12 Jan 2010 04:46:10 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Learning]]></category>
		<category><![CDATA[continuous improvement]]></category>
		<category><![CDATA[personal development]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=474</guid>
		<description>What if I told you there was only one activity you needed to do to become an expert, high-performing software developer? You might be doubtful of my claim. Yet this is exactly the finding reported in the book Talent Is Overrated by Geoff Colvin. Across multiple professions research points to the same activity as being [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/WyNLxuiiUgo" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/how-to-become-an-expert-developer/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2010/how-to-become-an-expert-developer</feedburner:origLink></item>
		<item>
		<title>Presenting My Continuous Improvement Framework</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/NNZBjwayG8k/presenting-my-continuous-improvement-framework</link>
		<comments>http://www.basilv.com/psd/blog/2010/presenting-my-continuous-improvement-framework#comments</comments>
		<pubDate>Mon, 04 Jan 2010 14:00:39 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[continuous improvement]]></category>
		<category><![CDATA[presentations]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=478</guid>
		<description>I will be presenting my continuous improvement framework at Agile Edmonton at 12:00 noon on January 6, 2009 at the IBM Innovation Center (10044-108th Street Edmonton, Alberta). In addition to the framework itself I will be covering lessons learned from championing and implementing continuous improvement. 
I look forward to seeing you there!&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/NNZBjwayG8k" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2010/presenting-my-continuous-improvement-framework/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2010/presenting-my-continuous-improvement-framework</feedburner:origLink></item>
		<item>
		<title>Use Understood Methods Rule</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/R9q_dEjYef0/use-understood-methods-rule</link>
		<comments>http://www.basilv.com/psd/blog/2009/use-understood-methods-rule#comments</comments>
		<pubDate>Mon, 14 Dec 2009 19:19:56 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Unit Testing]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=467</guid>
		<description>Over the years I have refined the approach I use to write code.  Recently I codified a key aspect of this approach as a practice I call the Use Understood Methods Rule. The basic formulation of the rule is quite simple: when coding a method only invoke other methods whose behavior you clearly understand [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/R9q_dEjYef0" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/use-understood-methods-rule/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2009/use-understood-methods-rule</feedburner:origLink></item>
		<item>
		<title>Comparing Agile and Traditional Project Management</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/hIjkZZ5Tzb4/comparing-agile-and-traditional-project-management</link>
		<comments>http://www.basilv.com/psd/blog/2009/comparing-agile-and-traditional-project-management#comments</comments>
		<pubDate>Fri, 04 Dec 2009 08:28:25 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[scope]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=470</guid>
		<description>I just attended a great presentation about Agile project management by Mike Cottmeyer at Agile Edmonton's monthly meeting. What stood out for me were two comparisons Mike made between Agile project management and traditional approaches (e.g. waterfall project, PMI/PMP).
Dealing with Uncertainty
Mike characterized traditional approaches as trying to manage out uncertainty in the effort to achieve [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/hIjkZZ5Tzb4" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/comparing-agile-and-traditional-project-management/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2009/comparing-agile-and-traditional-project-management</feedburner:origLink></item>
		<item>
		<title>Test Driven Development – Benefits, Limitations, and Techniques</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/g5pr-_lRDkc/test-driven-development-benefits-limitations-and-techniques</link>
		<comments>http://www.basilv.com/psd/blog/2009/test-driven-development-benefits-limitations-and-techniques#comments</comments>
		<pubDate>Tue, 01 Dec 2009 20:22:15 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Unit Testing]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=463</guid>
		<description>I wrote previously about the process I went through in adopting test driven development (TDD). In this article I discuss my experience with TDD: the benefits, the limitations, and the techniques I use when doing TDD.
Benefits
This section covers the benefits, as I see them, of doing TDD. This does not include the benefits of doing [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/g5pr-_lRDkc" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/test-driven-development-benefits-limitations-and-techniques/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2009/test-driven-development-benefits-limitations-and-techniques</feedburner:origLink></item>
		<item>
		<title>Lessons Learned Championing Continuous Improvement</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/L_AYUH8CSSc/lessons-learned-championing-continuous-improvement</link>
		<comments>http://www.basilv.com/psd/blog/2009/lessons-learned-championing-continuous-improvement#comments</comments>
		<pubDate>Mon, 23 Nov 2009 13:30:10 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Learning]]></category>
		<category><![CDATA[continuous improvement]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=459</guid>
		<description>For over one year now I have been championing continuous improvement across multiple teams. I have seen and struggled with various problems, some of which I have seen reoccur time and time again, and I have identified successful strategies for dealing with some of these issues. In this article I present my lessons learned in [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/L_AYUH8CSSc" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/lessons-learned-championing-continuous-improvement/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2009/lessons-learned-championing-continuous-improvement</feedburner:origLink></item>
		<item>
		<title>Adopting Test Driven Development</title>
		<link>http://feedproxy.google.com/~r/ProfessionalSoftwareDevelopment/~3/ob274XPG4jI/adopting-test-driven-development</link>
		<comments>http://www.basilv.com/psd/blog/2009/adopting-test-driven-development#comments</comments>
		<pubDate>Tue, 17 Nov 2009 23:22:28 +0000</pubDate>
		<dc:creator>Basil Vandegriend</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Learning]]></category>
		<category><![CDATA[personal development]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Unit Testing]]></category>

		<guid isPermaLink="false">http://www.basilv.com/psd/?p=453</guid>
		<description>I have always been keen on using automated unit tests since I first heard about them almost a decade ago. I have known about test driven development (TDD) for almost as long but the practice of writing tests first before writing production code never really clicked for me when I first tried it years ago. [...]&lt;img src="http://feeds.feedburner.com/~r/ProfessionalSoftwareDevelopment/~4/ob274XPG4jI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.basilv.com/psd/blog/2009/adopting-test-driven-development/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.basilv.com/psd/blog/2009/adopting-test-driven-development</feedburner:origLink></item>
	</channel>
</rss>
