<?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: Units of Work</title>
	<atom:link href="http://mcherm.com/permalinks/1/units-of-work/feed" rel="self" type="application/rss+xml" />
	<link>http://mcherm.com/permalinks/1/units-of-work</link>
	<description>Adventures in Programming</description>
	<lastBuildDate>Tue, 28 Jun 2011 11:50:58 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Chase Lake</title>
		<link>http://mcherm.com/permalinks/1/units-of-work/comment-page-1#comment-170</link>
		<dc:creator>Chase Lake</dc:creator>
		<pubDate>Thu, 10 Apr 2008 23:58:26 +0000</pubDate>
		<guid isPermaLink="false">http://mcherm.com/permalinks/1/units-of-work#comment-170</guid>
		<description></description>
		<content:encoded><![CDATA[<p>Interesting discussion.  I would also be interested in seeing us start to utilize a cost metric that captures current expenditures for a given process along with an estimate of savings as part of the prioritization discussion as well.</p>
<p>Development Effort (Cost/Speed) + Business Priority + Estimated Savings</p>
<p>Let me use a money analogy – since we’re a bank?.  If you have multiple credit card bills with varying amounts due some would say that it makes sense to pay an equal amount towards each (or a ratio thereof) until one or more of the balances is paid off.</p>
<p>I would contend that it makes more sense to make minimum payments towards all of the bills except the lowest and to focus all of your remaining funds towards paying that amount off quickly.  Once paid apply the payments to the next lowest until all have been eliminated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David B. Horvath, CCP</title>
		<link>http://mcherm.com/permalinks/1/units-of-work/comment-page-1#comment-169</link>
		<dc:creator>David B. Horvath, CCP</dc:creator>
		<pubDate>Tue, 08 Apr 2008 14:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://mcherm.com/permalinks/1/units-of-work#comment-169</guid>
		<description></description>
		<content:encoded><![CDATA[<p>The other thing required is reasonable (and defendable) measures of the size/complexity of the item being implemented. To say a screen is complex but a report is not can be flawed. There are many such size/complexity measures including function points, feature points, KLOC, etc. With good historical data, estimates are easier too (“in this organization, we take X hours per function point in tool Z#++”).</p>
<p>I’ve done some function point counting and basic training. I’m not a FPA-zealot, just mentioning it as one method.</p>
<p>- David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yanning Yan</title>
		<link>http://mcherm.com/permalinks/1/units-of-work/comment-page-1#comment-168</link>
		<dc:creator>Yanning Yan</dc:creator>
		<pubDate>Tue, 08 Apr 2008 13:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://mcherm.com/permalinks/1/units-of-work#comment-168</guid>
		<description>Michael,

Thanks for sharing your Essay. 

Regards,
Yanning</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>Thanks for sharing your Essay. </p>
<p>Regards,<br />
Yanning</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcherm</title>
		<link>http://mcherm.com/permalinks/1/units-of-work/comment-page-1#comment-160</link>
		<dc:creator>mcherm</dc:creator>
		<pubDate>Tue, 01 Apr 2008 19:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://mcherm.com/permalinks/1/units-of-work#comment-160</guid>
		<description>Joe: I am pleased to hear that, because I apparently had a mistaken impression of how the prioritization is occurring. I saw the feature list being created and sorted by the product owner (who evaluates business value based on input from various people), but somehow I had failed to realize that we were &lt;em&gt;also&lt;/em&gt; estimating development time and incorporating that into the choice of what to select for inclusion in a given sprint.</description>
		<content:encoded><![CDATA[<p>Joe: I am pleased to hear that, because I apparently had a mistaken impression of how the prioritization is occurring. I saw the feature list being created and sorted by the product owner (who evaluates business value based on input from various people), but somehow I had failed to realize that we were <em>also</em> estimating development time and incorporating that into the choice of what to select for inclusion in a given sprint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Campbell</title>
		<link>http://mcherm.com/permalinks/1/units-of-work/comment-page-1#comment-159</link>
		<dc:creator>Joe Campbell</dc:creator>
		<pubDate>Tue, 01 Apr 2008 16:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://mcherm.com/permalinks/1/units-of-work#comment-159</guid>
		<description>You may have misinterpreted prioritization to only be performed by the business and the Product Owner - this is not the case.  Since the order can account for any number of inputs the speed with which something can be done is also to be considered in what order to place something in.  If it is truly the case then that the order does not change despite having the speed information then there was a conscious decision to do it that way with a valid explanation as well.</description>
		<content:encoded><![CDATA[<p>You may have misinterpreted prioritization to only be performed by the business and the Product Owner &#8211; this is not the case.  Since the order can account for any number of inputs the speed with which something can be done is also to be considered in what order to place something in.  If it is truly the case then that the order does not change despite having the speed information then there was a conscious decision to do it that way with a valid explanation as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


