<?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 for MeetChrisBrady.com</title>
	<atom:link href="http://www.meetchrisbrady.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.meetchrisbrady.com/blog</link>
	<description>The personal website of Chris Brady.</description>
	<lastBuildDate>Thu, 16 Apr 2009 02:03:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Delivering more business value in Agile environments by Joe Little</title>
		<link>http://www.meetchrisbrady.com/blog/2009/04/14/delivering-more-business-value-in-agile-environments/comment-page-1/#comment-2</link>
		<dc:creator>Joe Little</dc:creator>
		<pubDate>Thu, 16 Apr 2009 02:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.meetchrisbrady.com/blog/?p=60#comment-2</guid>
		<description>Hi Chris,

Couple of comments.
First, great to post on this topic, which is so important.  The key meaning of BV is knowing that you gave the customers something they really wanted.
I agree with your notion of doing a cost-benefit analysis, where the SPs or the complexity for something is a proxy for the cost.  I would use Story Points as that proxy (since we already have &#039;em).
I also favor using &quot;Priority Poker&quot; to make visible the relative BV of stories.  Takes into account all definitions of BV. And works just like Planning Poker, except about BV. Mike Cohn favors this term (&quot;Priority Poker&quot;).

Having both, one can do a BV/SP factor on each story.  The &quot;highest&quot; ones probably go to the top of the PB (some human judgment to assure the stats did not lie to us).

Your last statement is the most important:  Having a clearer and clearer idea (today) where the BV is hidden (today) is ever more critical.

Thanks!
Joe</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>Couple of comments.<br />
First, great to post on this topic, which is so important.  The key meaning of BV is knowing that you gave the customers something they really wanted.<br />
I agree with your notion of doing a cost-benefit analysis, where the SPs or the complexity for something is a proxy for the cost.  I would use Story Points as that proxy (since we already have &#8216;em).<br />
I also favor using &#8220;Priority Poker&#8221; to make visible the relative BV of stories.  Takes into account all definitions of BV. And works just like Planning Poker, except about BV. Mike Cohn favors this term (&#8220;Priority Poker&#8221;).</p>
<p>Having both, one can do a BV/SP factor on each story.  The &#8220;highest&#8221; ones probably go to the top of the PB (some human judgment to assure the stats did not lie to us).</p>
<p>Your last statement is the most important:  Having a clearer and clearer idea (today) where the BV is hidden (today) is ever more critical.</p>
<p>Thanks!<br />
Joe</p>
]]></content:encoded>
	</item>
</channel>
</rss>

