<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Understanding the Customer vs Customer Value</title>
	<atom:link href="http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/</link>
	<description>Enabling the Agile Enterprise</description>
	<lastBuildDate>Sun, 06 Dec 2009 14:40:44 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dennis Stevens</title>
		<link>http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/comment-page-1/#comment-2190</link>
		<dc:creator>Dennis Stevens</dc:creator>
		<pubDate>Mon, 02 Nov 2009 17:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/#comment-2190</guid>
		<description>Josh,

Yes. The Product Owner owns the requirements and is responsible for ensuring value is being delivered. They should also provide oversight to make sure gold plating doesn&#039;t happen. 

But that&#039;s exactly the point. Agile just assumes that the Product Owner knows how to do this and is doing it. Everything about it is implicit. The ceremonies (processes) and values within the team are explicit - the ceremonies and values outside the team are left up to the product owner. 

Gilb is critical of Agile because this isn&#039;t addressed. Just saying it is someone else&#039;s responsibility doesn&#039;t make it happen effectively.</description>
		<content:encoded><![CDATA[<p>Josh,</p>
<p>Yes. The Product Owner owns the requirements and is responsible for ensuring value is being delivered. They should also provide oversight to make sure gold plating doesn&#8217;t happen. </p>
<p>But that&#8217;s exactly the point. Agile just assumes that the Product Owner knows how to do this and is doing it. Everything about it is implicit. The ceremonies (processes) and values within the team are explicit &#8211; the ceremonies and values outside the team are left up to the product owner. </p>
<p>Gilb is critical of Agile because this isn&#8217;t addressed. Just saying it is someone else&#8217;s responsibility doesn&#8217;t make it happen effectively.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Nankivel</title>
		<link>http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/comment-page-1/#comment-2180</link>
		<dc:creator>Josh Nankivel</dc:creator>
		<pubDate>Mon, 02 Nov 2009 14:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennisstevens.com/2009/11/02/understanding-the-customer-vs-customer-value/#comment-2180</guid>
		<description>Thanks Dennis, this is an interesting conversation.  As I was reading through your post I was thinking &quot;Doesn&#039;t the product owner own the requirements?  Aren&#039;t they supposed to ensure value is being delivered and work with the scrum master and team on it?&quot;

Is it just a matter of the team being so heavily focused on?  I&#039;ve seen Scrum implementations in particular where this was true.. the product owner&#039;s role was nebulous and ever changing.  Kind of like many project sponsors in general.</description>
		<content:encoded><![CDATA[<p>Thanks Dennis, this is an interesting conversation.  As I was reading through your post I was thinking &#8220;Doesn&#8217;t the product owner own the requirements?  Aren&#8217;t they supposed to ensure value is being delivered and work with the scrum master and team on it?&#8221;</p>
<p>Is it just a matter of the team being so heavily focused on?  I&#8217;ve seen Scrum implementations in particular where this was true.. the product owner&#8217;s role was nebulous and ever changing.  Kind of like many project sponsors in general.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
