<?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: Guest Post: The Cranky Test for Agile Product Managers</title>
	<atom:link href="http://crankypm.com/2009/02/cranky-test-agile-product-managers/feed/" rel="self" type="application/rss+xml" />
	<link>http://crankypm.com/2009/02/cranky-test-agile-product-managers/</link>
	<description>Product management, product marketing, and the ugly side of software product development.</description>
	<lastBuildDate>Tue, 15 May 2012 21:21:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: DL Cunningham</title>
		<link>http://crankypm.com/2009/02/cranky-test-agile-product-managers/comment-page-1/#comment-3008</link>
		<dc:creator>DL Cunningham</dc:creator>
		<pubDate>Mon, 16 Feb 2009 22:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/?p=1081#comment-3008</guid>
		<description>Great article.  In Saeed&#039;s case, it definitely sounds like somebody out-paced &quot;the clue-train of understanding&quot;.   With an understanding of velocity (no, it isn&#039;t how many hours a team member can work in a day), relative sizing of backlog items (hint: &quot;13.5 hours of dev time&quot; isn&#039;t a size), and a prioritized backlog, you can actually estimate a release timeline, given the scope.  The problem here was likely compounded by the fact that scrum was new, and velocity had not emerged yet.</description>
		<content:encoded><![CDATA[<p>Great article.  In Saeed&#8217;s case, it definitely sounds like somebody out-paced &#8220;the clue-train of understanding&#8221;.   With an understanding of velocity (no, it isn&#8217;t how many hours a team member can work in a day), relative sizing of backlog items (hint: &#8220;13.5 hours of dev time&#8221; isn&#8217;t a size), and a prioritized backlog, you can actually estimate a release timeline, given the scope.  The problem here was likely compounded by the fact that scrum was new, and velocity had not emerged yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saeed Khan</title>
		<link>http://crankypm.com/2009/02/cranky-test-agile-product-managers/comment-page-1/#comment-2941</link>
		<dc:creator>Saeed Khan</dc:creator>
		<pubDate>Sat, 07 Feb 2009 00:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/?p=1081#comment-2941</guid>
		<description>My most memorable incident related to Agile was that immediately after moving to Scrum, the ability to estimate a release timeline completely vanished from the company. One project manager said (and I&#039;m trying to quote him correctly):

&quot;Now that we&#039;ve moved to Scrum, we will only estimate effort one sprint at a time.&quot;

I said that&#039;s not acceptable. I need to know when the release will be completed.

The response:

&quot;Well we can release after every sprint so why does it matter?&quot;

Argh!!!! Don&#039;t these people understand how software companies function?</description>
		<content:encoded><![CDATA[<p>My most memorable incident related to Agile was that immediately after moving to Scrum, the ability to estimate a release timeline completely vanished from the company. One project manager said (and I&#8217;m trying to quote him correctly):</p>
<p>&#8220;Now that we&#8217;ve moved to Scrum, we will only estimate effort one sprint at a time.&#8221;</p>
<p>I said that&#8217;s not acceptable. I need to know when the release will be completed.</p>
<p>The response:</p>
<p>&#8220;Well we can release after every sprint so why does it matter?&#8221;</p>
<p>Argh!!!! Don&#8217;t these people understand how software companies function?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://crankypm.com/2009/02/cranky-test-agile-product-managers/comment-page-1/#comment-2938</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 06 Feb 2009 14:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/?p=1081#comment-2938</guid>
		<description>Glorious?  Really?  Kick a55!  You just made my day.  Now I&#039;ll just wait with baited breath for &lt;em&gt;CPM Responds to Agile Cranky PM Test (Part 1)&lt;/em&gt;.  My only addition - if you score 10 or more, you can be justifiably cranky.  

FWIW, I scored a 40 on that project.  Anyone want to guess what happened immediately after 8c?</description>
		<content:encoded><![CDATA[<p>Glorious?  Really?  Kick a55!  You just made my day.  Now I&#8217;ll just wait with baited breath for <em>CPM Responds to Agile Cranky PM Test (Part 1)</em>.  My only addition &#8211; if you score 10 or more, you can be justifiably cranky.  </p>
<p>FWIW, I scored a 40 on that project.  Anyone want to guess what happened immediately after 8c?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

