<?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 Roman Pichler</title>
	<atom:link href="http://www.romanpichler.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.romanpichler.com</link>
	<description>Roman Pichler&#039;s Thoughts on Agile Product Management</description>
	<lastBuildDate>Mon, 20 Feb 2012 08:56:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on The Highlander Principle by Roman Pichler</title>
		<link>http://www.romanpichler.com/blog/roles/the-single-product-owner/#comment-2263</link>
		<dc:creator>Roman Pichler</dc:creator>
		<pubDate>Mon, 20 Feb 2012 08:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=3007#comment-2263</guid>
		<description>Thanks for your comment, Roger. You are absolutely right: If one person makes all the product decisions, then some of the decisions are likely to be suboptimal or wrong. That&#039;s why single product ownership must be complemented by collaboration, as I&#039;ve mentioned in my post. 

However, if nobody plays the product owner role and the development team collectively manages the product, there is a danger of not paying enough attention to the user needs, the user experience, and the business model, but too much attention to the technical solution.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Roger. You are absolutely right: If one person makes all the product decisions, then some of the decisions are likely to be suboptimal or wrong. That&#8217;s why single product ownership must be complemented by collaboration, as I&#8217;ve mentioned in my post. </p>
<p>However, if nobody plays the product owner role and the development team collectively manages the product, there is a danger of not paying enough attention to the user needs, the user experience, and the business model, but too much attention to the technical solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Highlander Principle by Roger L. Cauvin</title>
		<link>http://www.romanpichler.com/blog/roles/the-single-product-owner/#comment-2262</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Sat, 18 Feb 2012 13:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=3007#comment-2262</guid>
		<description>Yes, having one person making all decisions can be efficient. But the decisions are often lower quality, and the team that needs to execute on them often operates less effectively when its members don’t feel shared ownership.

Furthermore, healthy teams can operate just as efficiently in decision-making and more effectively in execution.

Check my &lt;a href=&quot;http://blog.cauvin.org/2011/12/who-owns-product.html&quot; rel=&quot;nofollow&quot;&gt;blog entry on who really should own the product&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Yes, having one person making all decisions can be efficient. But the decisions are often lower quality, and the team that needs to execute on them often operates less effectively when its members don’t feel shared ownership.</p>
<p>Furthermore, healthy teams can operate just as efficiently in decision-making and more effectively in execution.</p>
<p>Check my <a href="http://blog.cauvin.org/2011/12/who-owns-product.html" rel="nofollow">blog entry on who really should own the product</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Product Backlog as a Learning Tool by My Homepage</title>
		<link>http://www.romanpichler.com/blog/product-backlog/product-backlog-learning-tool/#comment-2255</link>
		<dc:creator>My Homepage</dc:creator>
		<pubDate>Thu, 09 Feb 2012 02:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=2874#comment-2255</guid>
		<description>&lt;strong&gt;... [Trackback]...&lt;/strong&gt;

[...] Read More here: romanpichler.com/blog/product-backlog/product-backlog-learning-tool/ [...]...</description>
		<content:encoded><![CDATA[<p><strong>&#8230; [Trackback]&#8230;</strong></p>
<p>[...] Read More here: romanpichler.com/blog/product-backlog/product-backlog-learning-tool/ [...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Highlander Principle by The Product Owner Role at a Glance</title>
		<link>http://www.romanpichler.com/blog/roles/the-single-product-owner/#comment-2253</link>
		<dc:creator>The Product Owner Role at a Glance</dc:creator>
		<pubDate>Wed, 08 Feb 2012 16:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=3007#comment-2253</guid>
		<description>[...] the product owner role  Two common ways to apply the product owner role  The Highlander Principle Avoiding common product owner mistakes Scaling the product owner Desirable characteristics of a [...]</description>
		<content:encoded><![CDATA[<p>[...] the product owner role  Two common ways to apply the product owner role  The Highlander Principle Avoiding common product owner mistakes Scaling the product owner Desirable characteristics of a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scaling the Product Owner by The Single Product Owner</title>
		<link>http://www.romanpichler.com/blog/roles/scaling-the-product-owner/#comment-2252</link>
		<dc:creator>The Single Product Owner</dc:creator>
		<pubDate>Wed, 08 Feb 2012 14:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=21#comment-2252</guid>
		<description>[...] complex products or large projects, you have two options: You can either employ a product owner hierarchy with a chief product owner in charge of the entire product and product owners responsible for [...]</description>
		<content:encoded><![CDATA[<p>[...] complex products or large projects, you have two options: You can either employ a product owner hierarchy with a chief product owner in charge of the entire product and product owners responsible for [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

