<?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: Why Can&#8217;t We Get Good Product Owners?</title>
	<atom:link href="http://www.agileiq.org/2009/02/16/why-cant-we-get-good-product-owners/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileiq.org/2009/02/16/why-cant-we-get-good-product-owners/</link>
	<description>SolutionsIQ&#039;s Agile thought leaders, thinking out loud</description>
	<lastBuildDate>Mon, 30 Aug 2010 20:43:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Thomas Vollmer</title>
		<link>http://www.agileiq.org/2009/02/16/why-cant-we-get-good-product-owners/comment-page-1/#comment-9</link>
		<dc:creator>Thomas Vollmer</dc:creator>
		<pubDate>Fri, 20 Feb 2009 14:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileiq.org/?p=119#comment-9</guid>
		<description>I could not agree more. One thing to look out for when designating someone to be the proxy product owner is the risk of building up significant communication and decision debt on the business side. Taking on this debt makes the team go faster at first, but will probably have a significant negative impact on velocity when the debt comes due (usually when the developed software comes into contact with the real business stakeholder community). 

Minimizing this debt requires an empowered product owner. Empowered to make sure all business stakeholders are kept on the same page (avoiding communication debt) and empowered to make real decisions on behalf of all business stakeholders (avoiding decision debt).

If no one on the business side is empowered to be a good product owner, it&#039;s unlikely that someone farther removed from the business will be.</description>
		<content:encoded><![CDATA[<p>I could not agree more. One thing to look out for when designating someone to be the proxy product owner is the risk of building up significant communication and decision debt on the business side. Taking on this debt makes the team go faster at first, but will probably have a significant negative impact on velocity when the debt comes due (usually when the developed software comes into contact with the real business stakeholder community). </p>
<p>Minimizing this debt requires an empowered product owner. Empowered to make sure all business stakeholders are kept on the same page (avoiding communication debt) and empowered to make real decisions on behalf of all business stakeholders (avoiding decision debt).</p>
<p>If no one on the business side is empowered to be a good product owner, it&#8217;s unlikely that someone farther removed from the business will be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
