<?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: Problems of Estimation</title>
	<atom:link href="http://www.productbeautiful.com/2007/12/10/problems-of-estimation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.productbeautiful.com/2007/12/10/problems-of-estimation/</link>
	<description>Building Product Management from the Ground Up by Paul Young</description>
	<lastBuildDate>Wed, 28 Jul 2010 10:21:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Switching Teams &#124; The Productologist: Exploring the Depths of Product Management</title>
		<link>http://www.productbeautiful.com/2007/12/10/problems-of-estimation/comment-page-1/#comment-1638</link>
		<dc:creator>Switching Teams &#124; The Productologist: Exploring the Depths of Product Management</dc:creator>
		<pubDate>Mon, 01 Dec 2008 13:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbeautiful.com/2007/12/10/problems-of-estimation/#comment-1638</guid>
		<description>[...] and its role and effects on Product Management on many famous Product Management blogs: CrankyPM, Product Beautiful, All About Product Management (there are many more, just click on any of the blogs on my Blogroll [...]</description>
		<content:encoded><![CDATA[<p>[...] and its role and effects on Product Management on many famous Product Management blogs: CrankyPM, Product Beautiful, All About Product Management (there are many more, just click on any of the blogs on my Blogroll [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.productbeautiful.com/2007/12/10/problems-of-estimation/comment-page-1/#comment-1294</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 24 Jan 2008 22:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbeautiful.com/2007/12/10/problems-of-estimation/#comment-1294</guid>
		<description>You&#039;re right, GUI changes are basically impossible to estimate because you can go through the entire design process, build it, and then find out that it failed - only by putting it in front of a user.

I for one would love to know where product slips happen at an aggregate level.  Even better would be to segment it by hardware companies vs. software vs. services, and/or by vertical e.g. consumer electronics vs. networking vs. Web 2.0.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, GUI changes are basically impossible to estimate because you can go through the entire design process, build it, and then find out that it failed &#8211; only by putting it in front of a user.</p>
<p>I for one would love to know where product slips happen at an aggregate level.  Even better would be to segment it by hardware companies vs. software vs. services, and/or by vertical e.g. consumer electronics vs. networking vs. Web 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Grant</title>
		<link>http://www.productbeautiful.com/2007/12/10/problems-of-estimation/comment-page-1/#comment-1293</link>
		<dc:creator>Tom Grant</dc:creator>
		<pubDate>Thu, 24 Jan 2008 19:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbeautiful.com/2007/12/10/problems-of-estimation/#comment-1293</guid>
		<description>Good suggestions, all. I&#039;d even expand the list of difficult-to-estimate projects to user experience changes. They&#039;re not as technologically dense as, say, re-building the core libraries of a complex middleware application from scratch. However, it&#039;s just as hard to estimate a UI overhaul, since you can&#039;t really tell from the beginning how many different tasks or use cases are going to need a thorough drubbing.

How valuable would it be to get hard data, across the industry, on the real sources of product slips? I think all of us in the PM profession can tell good stories, but at an aggregate level, are there any patterns? I&#039;m asking, in part, because I now have the luxury of putting my time into studying these sorts of questions.</description>
		<content:encoded><![CDATA[<p>Good suggestions, all. I&#8217;d even expand the list of difficult-to-estimate projects to user experience changes. They&#8217;re not as technologically dense as, say, re-building the core libraries of a complex middleware application from scratch. However, it&#8217;s just as hard to estimate a UI overhaul, since you can&#8217;t really tell from the beginning how many different tasks or use cases are going to need a thorough drubbing.</p>
<p>How valuable would it be to get hard data, across the industry, on the real sources of product slips? I think all of us in the PM profession can tell good stories, but at an aggregate level, are there any patterns? I&#8217;m asking, in part, because I now have the luxury of putting my time into studying these sorts of questions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
