<?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"
	>
<channel>
	<title>Comments on: OSCON 2007: Managing Technical Debt</title>
	<atom:link href="http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/</link>
	<description></description>
	<pubDate>Thu, 16 Oct 2008 01:11:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: mde</title>
		<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-334899</link>
		<dc:creator>mde</dc:creator>
		<pubDate>Mon, 13 Aug 2007 22:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-334899</guid>
		<description>Thanks again for the talk, Andy. A lot of excellent ideas in there.</description>
		<content:encoded><![CDATA[<p>Thanks again for the talk, Andy. A lot of excellent ideas in there.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Lester</title>
		<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-334778</link>
		<dc:creator>Andy Lester</dc:creator>
		<pubDate>Mon, 13 Aug 2007 14:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-334778</guid>
		<description>The key to stories is that it puts your concerns in terms that management can understand.  Management understands dollars and days, so your stories should tell that.  Don't say that "we have to have referential integrity in the database!"  We geeks too often feel that other people should just understand what we're saying.

Instead, say that "If we take a week to add referential integrity and foreign keys to the database, we'll make coding safer, and will probably cut down on errors.  Remember that Foo project and we blew the deadline by two weeks because we had an extra three weeks of bugs that we had to close?  Most of that was caused by bugs that would have been caught if we'd had foreign key constraints in place.  We want to prevent future screwups like that."  That's a story that your boss can get behind, and one that he can explain to his boss, too.</description>
		<content:encoded><![CDATA[<p>The key to stories is that it puts your concerns in terms that management can understand.  Management understands dollars and days, so your stories should tell that.  Don&#8217;t say that &#8220;we have to have referential integrity in the database!&#8221;  We geeks too often feel that other people should just understand what we&#8217;re saying.</p>
<p>Instead, say that &#8220;If we take a week to add referential integrity and foreign keys to the database, we&#8217;ll make coding safer, and will probably cut down on errors.  Remember that Foo project and we blew the deadline by two weeks because we had an extra three weeks of bugs that we had to close?  Most of that was caused by bugs that would have been caught if we&#8217;d had foreign key constraints in place.  We want to prevent future screwups like that.&#8221;  That&#8217;s a story that your boss can get behind, and one that he can explain to his boss, too.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-328511</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 07 Aug 2007 17:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-328511</guid>
		<description>Another point Andy made about selling your manager on changes is that it can be helpful to tell *stories*, either cautionary or exemplary, about similar events and changes that the company has been through -- stories that support the idea of doing the project you want to do.</description>
		<content:encoded><![CDATA[<p>Another point Andy made about selling your manager on changes is that it can be helpful to tell *stories*, either cautionary or exemplary, about similar events and changes that the company has been through &#8212; stories that support the idea of doing the project you want to do.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mde</title>
		<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-327924</link>
		<dc:creator>mde</dc:creator>
		<pubDate>Tue, 07 Aug 2007 03:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-327924</guid>
		<description>Exactly -- in this case 'profitable' is whatever is the most useful to you per amount of time and effort spent. So, basically, concentrate on whatever fixes will give you the most "bang for your buck."</description>
		<content:encoded><![CDATA[<p>Exactly &#8212; in this case &#8216;profitable&#8217; is whatever is the most useful to you per amount of time and effort spent. So, basically, concentrate on whatever fixes will give you the most &#8220;bang for your buck.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mrsmiley</title>
		<link>http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-326424</link>
		<dc:creator>mrsmiley</dc:creator>
		<pubDate>Sun, 05 Aug 2007 23:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/08/04/oscon-2007-managing-technical-debt/#comment-326424</guid>
		<description>I'm assuming based on your example that "profit" isn't just talking about a monetary measurement.</description>
		<content:encoded><![CDATA[<p>I&#8217;m assuming based on your example that &#8220;profit&#8221; isn&#8217;t just talking about a monetary measurement.</p>]]></content:encoded>
	</item>
</channel>
</rss>
