<?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 long does it take to make software? And how long should it take!</title>
	<atom:link href="http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/feed/" rel="self" type="application/rss+xml" />
	<link>http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/</link>
	<description>Coffee Sessions for the Industry!</description>
	<lastBuildDate>Sat, 12 May 2012 08:39:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Nash</title>
		<link>http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/comment-page-1/#comment-10908</link>
		<dc:creator>Nash</dc:creator>
		<pubDate>Sun, 27 Apr 2008 21:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/#comment-10908</guid>
		<description>&lt;blockquote&gt;Before youâ€™ve had time to think it through, you say 15 days. Your boss will think, okayâ€¦ if he can do it in 15, he can do it in 10 and goes and commits 6 days to the client.&lt;/blockquote&gt;

Doesn&#039;t seem like a case of bad estimation; sounds like a case of having an asshole for a boss. It doesn&#039;t matter what your estimation methodology is; if your bass is an ass and reduces the given estimate by a 3rd; he&#039;s screwing the company. 

Any decent engineer should put his foot down and say &quot;No, I said 15 days. This project is not doable.&quot;

Secondly, you may be committed to a timeline you have given but even the best plans can get broken real quick. General Eisenhower famously said 

&quot;In preparing for battle I have always found that plans are useless, but planning is indispensable.&quot; 

If something has changed or if you can&#039;t meet with your plans; be honest and forthcoming with the customer. Explain them what can&#039;t be met on time and why. Give them the updated timelines. People like honesty over bullshit any day.

And finally, CMM is a horrible standard that keeps your eye off the real ball. If you want people to respect you; it should be for your work which should speak for itself. Not by some stamp on you saying &quot;Hello, I&#039;m dave, CMM Level 5&quot;</description>
		<content:encoded><![CDATA[<blockquote><p>Before youâ€™ve had time to think it through, you say 15 days. Your boss will think, okayâ€¦ if he can do it in 15, he can do it in 10 and goes and commits 6 days to the client.</p></blockquote>
<p>Doesn&#8217;t seem like a case of bad estimation; sounds like a case of having an asshole for a boss. It doesn&#8217;t matter what your estimation methodology is; if your bass is an ass and reduces the given estimate by a 3rd; he&#8217;s screwing the company. </p>
<p>Any decent engineer should put his foot down and say &#8220;No, I said 15 days. This project is not doable.&#8221;</p>
<p>Secondly, you may be committed to a timeline you have given but even the best plans can get broken real quick. General Eisenhower famously said </p>
<p>&#8220;In preparing for battle I have always found that plans are useless, but planning is indispensable.&#8221; </p>
<p>If something has changed or if you can&#8217;t meet with your plans; be honest and forthcoming with the customer. Explain them what can&#8217;t be met on time and why. Give them the updated timelines. People like honesty over bullshit any day.</p>
<p>And finally, CMM is a horrible standard that keeps your eye off the real ball. If you want people to respect you; it should be for your work which should speak for itself. Not by some stamp on you saying &#8220;Hello, I&#8217;m dave, CMM Level 5&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arfeen</title>
		<link>http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/comment-page-1/#comment-10894</link>
		<dc:creator>Arfeen</dc:creator>
		<pubDate>Sun, 27 Apr 2008 04:16:40 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/#comment-10894</guid>
		<description>haha .. that old method sounds so familiar ..... I once worked for  manager that would always cut down my estimates in order to make us work harder ... it was just sooo maddening !!!!</description>
		<content:encoded><![CDATA[<p>haha .. that old method sounds so familiar &#8230;.. I once worked for  manager that would always cut down my estimates in order to make us work harder &#8230; it was just sooo maddening !!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How long does it take to make software! &#171; Usman&#8217;s Weblog</title>
		<link>http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/comment-page-1/#comment-10889</link>
		<dc:creator>How long does it take to make software! &#171; Usman&#8217;s Weblog</dc:creator>
		<pubDate>Sat, 26 Apr 2008 18:53:54 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/#comment-10889</guid>
		<description>[...] [via Green &amp; White] [...]</description>
		<content:encoded><![CDATA[<p>[...] [via Green &amp;amp; White] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: not my cuppatea</title>
		<link>http://greenwhite.org/blog/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/comment-page-1/#comment-10887</link>
		<dc:creator>not my cuppatea</dc:creator>
		<pubDate>Sat, 26 Apr 2008 13:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/04/26/how-long-does-it-take-to-make-software-and-how-long-should-it-take/#comment-10887</guid>
		<description>You can also make it a rule to always always add phrases like &#039;x to y days which may vary with the exact requirements&#039; even when giving out a rough estimate to your boss verbally. Lets face it, we DO have to make decisions in 5 minutes and commit to over-zelaous deadline at times which might run your company for the next 2-3 years. 

Assuming you are a/the PM, if your boss is setting out a unrealistic deadline, add &#039;talk to boss&#039; to your TODO list. You can push him for establishing and following proper processes for at least the major SE phases. If that doesn&#039;t work, add &#039;look for a better job&#039; to your list. Any company with such a boss wont survive for long.

My 1.29 PKR (at the going exchange rate)</description>
		<content:encoded><![CDATA[<p>You can also make it a rule to always always add phrases like &#8216;x to y days which may vary with the exact requirements&#8217; even when giving out a rough estimate to your boss verbally. Lets face it, we DO have to make decisions in 5 minutes and commit to over-zelaous deadline at times which might run your company for the next 2-3 years. </p>
<p>Assuming you are a/the PM, if your boss is setting out a unrealistic deadline, add &#8216;talk to boss&#8217; to your TODO list. You can push him for establishing and following proper processes for at least the major SE phases. If that doesn&#8217;t work, add &#8216;look for a better job&#8217; to your list. Any company with such a boss wont survive for long.</p>
<p>My 1.29 PKR (at the going exchange rate)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

