<?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>Reflections on Software Engineering &#187; Process</title>
	<atom:link href="http://neverletdown.net/topics/process/feed/" rel="self" type="application/rss+xml" />
	<link>http://neverletdown.net</link>
	<description>by Michael Keeling</description>
	<lastBuildDate>Wed, 14 Sep 2011 02:23:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Change Your Team&#8217;s Oil</title>
		<link>http://neverletdown.net/2011/06/change-your-teams-oil/</link>
		<comments>http://neverletdown.net/2011/06/change-your-teams-oil/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 02:45:30 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[reflection]]></category>
		<category><![CDATA[retrospectives]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=437</guid>
		<description><![CDATA[Every 5,000 miles or so I take my car in to the shop for an oil change. It&#8217;s part of the routine, preventative maintenance I do to keep my car running in tip top shape. Routine maintenance gives me the peace of mind that my car won&#8217;t leave me stranded somewhere, extends the life of [...]]]></description>
			<content:encoded><![CDATA[Every 5,000 miles or so I take my car in to the shop for an oil change.  It's part of the routine, preventative maintenance I do to keep my car running in tip top shape.  Routine maintenance gives me the peace of mind that my car won't leave me stran]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2011/06/change-your-teams-oil/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why I Pledge an Oath on Non-Allegiance</title>
		<link>http://neverletdown.net/2011/04/why-i-pledge-an-oath-on-non-allegiance/</link>
		<comments>http://neverletdown.net/2011/04/why-i-pledge-an-oath-on-non-allegiance/#comments</comments>
		<pubDate>Sat, 16 Apr 2011 03:12:23 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[relationship]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=424</guid>
		<description><![CDATA[When building relationships we look for commonalities between ourselves and others. When we have things in common it makes us feel good, like we're not alone in the world. And the things we have in common become the basis for lasting relationships.]]></description>
			<content:encoded><![CDATA[When building relationships we look for commonalities between ourselves and others.  When we have things in common it makes us feel good, like we're not alone in the world.  And the things we have in common become the basis for lasting relationships.]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2011/04/why-i-pledge-an-oath-on-non-allegiance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hacking is not a Dirty Word</title>
		<link>http://neverletdown.net/2010/07/hacking-is-not-a-dirty-word/</link>
		<comments>http://neverletdown.net/2010/07/hacking-is-not-a-dirty-word/#comments</comments>
		<pubDate>Fri, 02 Jul 2010 03:21:42 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[action research]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[myth busting]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[technical debt]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=358</guid>
		<description><![CDATA[I used to think hacking was bad. It was something you did when you didn’t have a plan, when you didn’t know what you were doing; it’s what amateurs do, noodling around the code without clear direction or intent. Or it was something you did, q]]></description>
			<content:encoded><![CDATA[I used to think hacking was bad.  It was something you did when you didn’t have a plan, when you didn’t know what you were doing; it’s what amateurs do, noodling around the code without clear direction or intent.  Or it was something you did, q]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/07/hacking-is-not-a-dirty-word/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Lightweight Experiments for Process Improvement</title>
		<link>http://neverletdown.net/2010/06/lightweight-experiments-for-process-improvement/</link>
		<comments>http://neverletdown.net/2010/06/lightweight-experiments-for-process-improvement/#comments</comments>
		<pubDate>Tue, 15 Jun 2010 13:30:43 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Talks]]></category>
		<category><![CDATA[experiment]]></category>
		<category><![CDATA[experimentation]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[measures]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[MSE]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[scientific method]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[studio]]></category>
		<category><![CDATA[XP]]></category>
		<category><![CDATA[xp2010]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=339</guid>
		<description><![CDATA[[This post is a recap on the second talk I gave at XP2010. This was the big one, the experience report talk, one of 15 experience reports published at XP2010. You can download the slides (pdf) or the full paper (pdf) from this website or from XP2010.]]></description>
			<content:encoded><![CDATA[[This post is a recap on the second talk I gave at XP2010. This was the big one, the experience report talk, one of 15 experience reports published at XP2010. You can download the slides (pdf) or the full paper (pdf) from this website or from XP2010.]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/06/lightweight-experiments-for-process-improvement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>See you at XP2010 in Trondheim, Norway!</title>
		<link>http://neverletdown.net/2010/06/see-you-at-xp2010-in-trondheim-norway/</link>
		<comments>http://neverletdown.net/2010/06/see-you-at-xp2010-in-trondheim-norway/#comments</comments>
		<pubDate>Tue, 01 Jun 2010 17:30:57 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[experiment]]></category>
		<category><![CDATA[extreme programming]]></category>
		<category><![CDATA[pair programming]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[XP]]></category>
		<category><![CDATA[xp2010]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=309</guid>
		<description><![CDATA[As I’m writing this I am making final preparations to leave for Trondheim, Norway to present an experience report at the 11th International Conference on Agile Software Development and Extreme Programming, or XP2010. After my experience report was]]></description>
			<content:encoded><![CDATA[As I’m writing this I am making final preparations to leave for Trondheim, Norway to present an experience report at the 11th International Conference on Agile Software Development and Extreme Programming, or XP2010.  After my experience report was]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/06/see-you-at-xp2010-in-trondheim-norway/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is Better the Enemy of Good Enough?</title>
		<link>http://neverletdown.net/2010/04/is-better-the-enemy-of-good-enough/</link>
		<comments>http://neverletdown.net/2010/04/is-better-the-enemy-of-good-enough/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 14:19:45 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=254</guid>
		<description><![CDATA["Better is the enemy of good enough" is a phrase often held up as the reason for not making changes on a team. If everything seems "good enough," the effort to make something better is regarded as waste. A lot of times, "good enough" is defied in te]]></description>
			<content:encoded><![CDATA["Better is the enemy of good enough" is a phrase often held up as the reason for not making changes on a team. If everything seems "good enough," the effort to make something better is regarded as waste.  A lot of times, "good enough" is defied in te]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/04/is-better-the-enemy-of-good-enough/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identifying Process Affordances: Nudging Toward Change</title>
		<link>http://neverletdown.net/2010/03/identifying-process-affordances-nudging-toward-change/</link>
		<comments>http://neverletdown.net/2010/03/identifying-process-affordances-nudging-toward-change/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 03:16:26 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Talks]]></category>
		<category><![CDATA[affordance]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Donald Norman]]></category>
		<category><![CDATA[nudge]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[studio]]></category>
		<category><![CDATA[talk]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=184</guid>
		<description><![CDATA[This post is a recap of a talk I gave this weekend at the Carnegie Mellon University Master of Software Engineering 20th Anniversary Mini-Conference. I’ve made the paper this talk is based on (pdf) as well as the slides I used during the talk (pdf]]></description>
			<content:encoded><![CDATA[This post is a recap of a talk I gave this weekend at the Carnegie Mellon University Master of Software Engineering 20th Anniversary Mini-Conference.  I’ve made the paper this talk is based on (pdf) as well as the slides I used during the talk (pdf]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/03/identifying-process-affordances-nudging-toward-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting Started with Version Control</title>
		<link>http://neverletdown.net/2010/03/getting-started-with-version-control/</link>
		<comments>http://neverletdown.net/2010/03/getting-started-with-version-control/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 04:55:19 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[CVS]]></category>
		<category><![CDATA[DRY]]></category>
		<category><![CDATA[pragmatic]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[SVN]]></category>
		<category><![CDATA[version control]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=179</guid>
		<description><![CDATA[I've had to help more than a few teams get their version control systems sorted out over the past few years, and so I thought it would be easier if I just wrote down the philosophies I use for initializing a repository and getting the whole system se]]></description>
			<content:encoded><![CDATA[I've had to help more than a few teams get their version control systems sorted out over the past few years, and so I thought it would be easier if I just wrote down the philosophies I use for initializing a repository and getting the whole system se]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/03/getting-started-with-version-control/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why don&#8217;t you use Continuous Integration?</title>
		<link>http://neverletdown.net/2010/02/why-dont-you-use-continuous-integration/</link>
		<comments>http://neverletdown.net/2010/02/why-dont-you-use-continuous-integration/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 04:22:15 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[Hudson]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=165</guid>
		<description><![CDATA[Everyone has a chore they hate doing. For me it’s cleaning the dishes. I’m a busy guy so I usually don’t get around to cooking and eating dinner until fairly late. Rather than cleaning anything, I stack the dishes in the sink and maybe soak]]></description>
			<content:encoded><![CDATA[Everyone has a chore they hate doing.   For me it’s cleaning the dishes.  I’m a busy guy so I usually don’t get around to cooking and eating dinner until fairly late.  Rather than cleaning anything, I stack the dishes in the sink and maybe soak]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/02/why-dont-you-use-continuous-integration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tracking Bugs Better</title>
		<link>http://neverletdown.net/2009/10/tracking-bugs-better/</link>
		<comments>http://neverletdown.net/2009/10/tracking-bugs-better/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 03:18:12 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[bug tracking]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[defect tracking]]></category>
		<category><![CDATA[defects]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[process tailoring]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[Team Software Process]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[XP]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=99</guid>
		<description><![CDATA[Most software processes are light in two areas: quality assurance and process improvement. Most processes prescribe specific techniques for ensuring the production of quality code. XP for example advocates unit testing with TDD, continuous integrat]]></description>
			<content:encoded><![CDATA[Most software processes are light in two areas: quality assurance and process improvement.  Most processes prescribe specific techniques for ensuring the production of quality code.  XP for example advocates unit testing with TDD, continuous integrat]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2009/10/tracking-bugs-better/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kenny Rogers&#8217; Guide to Software Process Improvement</title>
		<link>http://neverletdown.net/2009/06/kenny-rogers-guide-to-software-process-improvement/</link>
		<comments>http://neverletdown.net/2009/06/kenny-rogers-guide-to-software-process-improvement/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 00:37:26 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[CMM]]></category>
		<category><![CDATA[CMMI]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=50</guid>
		<description><![CDATA[Process improvement is a tricky mistress.  Usually it’s sufficient to feel that something can be done better, but often, especially for larger organizations or folks looking for higher CMMI rankings, it’s necessary to quantify improvements in te]]></description>
			<content:encoded><![CDATA[Process improvement is a tricky mistress.  Usually it’s sufficient to feel that something can be done better, but often, especially for larger organizations or folks looking for higher CMMI rankings, it’s necessary to quantify improvements in te]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2009/06/kenny-rogers-guide-to-software-process-improvement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Process Affordances: Ignore at Your own Peril</title>
		<link>http://neverletdown.net/2009/03/process-affordances-ignore-at-your-own-peril/</link>
		<comments>http://neverletdown.net/2009/03/process-affordances-ignore-at-your-own-peril/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 21:15:07 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[affordance]]></category>
		<category><![CDATA[Carnegie Mellon]]></category>
		<category><![CDATA[Donald Norman]]></category>
		<category><![CDATA[nudge]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[postmortem]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[studio]]></category>
		<category><![CDATA[tracking]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=26</guid>
		<description><![CDATA[The Amsterdam airport was able to reduce the amount of urine "spillage" that hit the men's room floor by 80% simply by etching a life-like image of a fly near the urinals' drains. The fly was specifically engineered into the urinals to alter gentlem]]></description>
			<content:encoded><![CDATA[The Amsterdam airport was able to reduce the amount of urine "spillage" that hit the men's room floor by 80% simply by etching a life-like image of a fly near the urinals' drains.  The fly was specifically engineered into the urinals to alter gentlem]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2009/03/process-affordances-ignore-at-your-own-peril/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

