<?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: How to Piss Off Development in a Really Big Way</title>
	<atom:link href="http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/</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: How to Get the Respect of Development &#124; The Cranky Product Manager</title>
		<link>http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/comment-page-1/#comment-884</link>
		<dc:creator>How to Get the Respect of Development &#124; The Cranky Product Manager</dc:creator>
		<pubDate>Wed, 17 Sep 2008 19:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/crankypm/2006/06/how-to-piss-off-development-in-a-really-big-way/#comment-884</guid>
		<description>[...] Step 1: Stop being an Asshole.&#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Step 1: Stop being an Asshole.&nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PMPath</title>
		<link>http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/comment-page-1/#comment-857</link>
		<dc:creator>PMPath</dc:creator>
		<pubDate>Fri, 27 Jul 2007 23:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/crankypm/2006/06/how-to-piss-off-development-in-a-really-big-way/#comment-857</guid>
		<description>&lt;p&gt;That is so true, I heard it earlier in my career, all of us got together after the meeting and bitched about the APM. &quot;I&quot; have avoided saying &quot;I&quot; period, try to make &quot;I&quot;, &quot;WE&quot; wherever possible. Its not yours to begin with, well, unless you own the company.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>That is so true, I heard it earlier in my career, all of us got together after the meeting and bitched about the APM. &#8220;I&#8221; have avoided saying &#8220;I&#8221; period, try to make &#8220;I&#8221;, &#8220;WE&#8221; wherever possible. Its not yours to begin with, well, unless you own the company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A fellow, long-disgruntled product manager</title>
		<link>http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/comment-page-1/#comment-858</link>
		<dc:creator>A fellow, long-disgruntled product manager</dc:creator>
		<pubDate>Tue, 22 Aug 2006 04:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/crankypm/2006/06/how-to-piss-off-development-in-a-really-big-way/#comment-858</guid>
		<description>&lt;p&gt;Another great way to piss of your engineering team? -- ask for &quot;zero defect&quot; software. After the shock of acknowledging that the code they write is full of bugs (most devs I&#039;ve worked with seem to be able to code between 5-25 bugs per day), they&#039;ll work hard to convince you that the deferrals, the &quot;NIH&quot; bugs, the &quot;It&#039;s micosoft&#039;s fault&quot;, and the other long list of &quot;resolutions&quot; acutally result in software with no shipping bugs. &lt;/p&gt;

&lt;p&gt;It&#039;s all in how you write the spec, see.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Another great way to piss of your engineering team? &#8212; ask for &#8220;zero defect&#8221; software. After the shock of acknowledging that the code they write is full of bugs (most devs I&#8217;ve worked with seem to be able to code between 5-25 bugs per day), they&#8217;ll work hard to convince you that the deferrals, the &#8220;NIH&#8221; bugs, the &#8220;It&#8217;s micosoft&#8217;s fault&#8221;, and the other long list of &#8220;resolutions&#8221; acutally result in software with no shipping bugs. </p>
<p>It&#8217;s all in how you write the spec, see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://crankypm.com/2006/06/how-to-piss-off-development-in-a-really-big-way/comment-page-1/#comment-859</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 11 Jul 2006 14:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://crankypm.com/crankypm/2006/06/how-to-piss-off-development-in-a-really-big-way/#comment-859</guid>
		<description>&lt;p&gt;Very fun stuff.  I&#039;m enjoying your writing, and just subscribed - looking forward to more.  Thanks for adding us to your blogroll too!&lt;/p&gt;

&lt;p&gt;I always liked Lincoln&#039;s approach - share credit and take blame.  I guess that would be an LPM.  I&#039;ve been lucky enough to not run into any true APMs.  Clueless people occasionally, but not straight-up APMs.&lt;/p&gt;

&lt;p&gt;There&#039;s a saying in poker - if you don&#039;t know who the fish is, you&#039;re the fish.  I hope that doesn&#039;t apply to product management.&lt;/p&gt;

&lt;p&gt;Anyway, good writing, keep it up!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Very fun stuff.  I&#8217;m enjoying your writing, and just subscribed &#8211; looking forward to more.  Thanks for adding us to your blogroll too!</p>
<p>I always liked Lincoln&#8217;s approach &#8211; share credit and take blame.  I guess that would be an LPM.  I&#8217;ve been lucky enough to not run into any true APMs.  Clueless people occasionally, but not straight-up APMs.</p>
<p>There&#8217;s a saying in poker &#8211; if you don&#8217;t know who the fish is, you&#8217;re the fish.  I hope that doesn&#8217;t apply to product management.</p>
<p>Anyway, good writing, keep it up!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

