<?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: Deadlines</title>
	<atom:link href="http://averyblog.com/net/deadlines/feed/" rel="self" type="application/rss+xml" />
	<link>http://averyblog.com/net/deadlines/</link>
	<description>This is not the greatest tagline in the world... this is just a tribute.</description>
	<lastBuildDate>Mon, 11 Jan 2010 16:36:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeffrey Palermo</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1879</link>
		<dc:creator>Jeffrey Palermo</dc:creator>
		<pubDate>Wed, 15 Mar 2006 15:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1879</guid>
		<description>&lt;p&gt;Deadlines are just one point in the triangle.  If there is a business deadline, the scope of work and number of developers  have to be adjusted to make it fit.  If the development team is constrained, the feature set has to flex.  If X feature just HAS to be there, then that&#039;s when you throw out the deadline and estimate your real deadline.  &lt;br /&gt;&lt;br /&gt;We do that every day.  Given a scope, we have 4 developers.  We estimate how long it will take us and give three dates:  50% probability, 70%, and 90%.  The 90% date is the date they can actually count on unless something external delays us.  We tell the higher ups that this is what they are looking at.  They appreciate the analysis, and they&#039;ve never said &quot;screw you, meet my date&quot;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Deadlines are just one point in the triangle.  If there is a business deadline, the scope of work and number of developers  have to be adjusted to make it fit.  If the development team is constrained, the feature set has to flex.  If X feature just HAS to be there, then that&#8217;s when you throw out the deadline and estimate your real deadline.  </p>
<p>We do that every day.  Given a scope, we have 4 developers.  We estimate how long it will take us and give three dates:  50% probability, 70%, and 90%.  The 90% date is the date they can actually count on unless something external delays us.  We tell the higher ups that this is what they are looking at.  They appreciate the analysis, and they&#8217;ve never said &#8220;screw you, meet my date&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Jonas</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1880</link>
		<dc:creator>Richard Jonas</dc:creator>
		<pubDate>Mon, 13 Mar 2006 22:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1880</guid>
		<description>&lt;p&gt;I think the key to avoiding your four problems is to make sure you add a new feature that means something to end users every week or so.  If you show these features to your users as you develop them the business analysts will know how fast you can work and be more realistic.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think the key to avoiding your four problems is to make sure you add a new feature that means something to end users every week or so.  If you show these features to your users as you develop them the business analysts will know how fast you can work and be more realistic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajeev Gopal</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1881</link>
		<dc:creator>Rajeev Gopal</dc:creator>
		<pubDate>Mon, 13 Mar 2006 02:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1881</guid>
		<description>&lt;p&gt;Deadlines are important, as said. In technology companies, technologies are more realistic that that made in a business driven environment. That is what I have seen. This might not be 100% true, but...&lt;br /&gt;&lt;br /&gt;Clients are dealt by mostly business analysts, who may or may not have programming background. &quot;You want this to be done by next Tuesday? What about this Friday?&quot; &lt;br /&gt;Result? Programmers burning midnight oil.&lt;br /&gt;&lt;br /&gt;This case would not be seen when BAs involve programmer leads in their deadline decision making...&lt;br /&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Deadlines are important, as said. In technology companies, technologies are more realistic that that made in a business driven environment. That is what I have seen. This might not be 100% true, but&#8230;</p>
<p>Clients are dealt by mostly business analysts, who may or may not have programming background. &#8220;You want this to be done by next Tuesday? What about this Friday?&#8221; <br />Result? Programmers burning midnight oil.</p>
<p>This case would not be seen when BAs involve programmer leads in their deadline decision making&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Avery</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1876</link>
		<dc:creator>James Avery</dc:creator>
		<pubDate>Mon, 13 Mar 2006 01:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1876</guid>
		<description>&lt;p&gt;Actually my post was pointing out that deadlines are important. I think we will be just fine, thanks for your concern. (clever name though)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Actually my post was pointing out that deadlines are important. I think we will be just fine, thanks for your concern. (clever name though)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epsilon Aurigae</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1878</link>
		<dc:creator>Epsilon Aurigae</dc:creator>
		<pubDate>Mon, 13 Mar 2006 01:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1878</guid>
		<description>&lt;p&gt;Intersting post. Do you have a deadline looming?  Are you feeling the pressure?  The end of June will be here before you know it.  Will you get it done? Or will it just be vaporware? &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Intersting post. Do you have a deadline looming?  Are you feeling the pressure?  The end of June will be here before you know it.  Will you get it done? Or will it just be vaporware? </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haacked</title>
		<link>http://averyblog.com/net/deadlines/comment-page-1/#comment-1877</link>
		<dc:creator>Haacked</dc:creator>
		<pubDate>Sun, 12 Mar 2006 23:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://averyblog.infozerk.net/?p=540#comment-1877</guid>
		<description>&lt;p&gt;Well I do believe in deadlines.  However, deadlines should be set based on realistic deadlines in which the developers give input and feedback.  A deadline should really be an agreement between developers and management.&lt;br /&gt;&lt;br /&gt;&quot;Artificial&quot; deadlines are those that are not informed by realistic estimates, but by wishful thinking.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well I do believe in deadlines.  However, deadlines should be set based on realistic deadlines in which the developers give input and feedback.  A deadline should really be an agreement between developers and management.</p>
<p>&#8220;Artificial&#8221; deadlines are those that are not informed by realistic estimates, but by wishful thinking.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

