 




<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Never Opposed Project Manager Is A Risky Affair</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/never-opposed-project-manager-is-a-risky-affair/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/quality-assurance/never-opposed-project-manager-is-a-risky-affair/</link>
	<description>Improvement in Quality never ends. There is always a scope of improvement in life...</description>
	<lastBuildDate>Wed, 08 May 2013 13:28:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Never Opposed Project Manager Is A Risky Affair &#8211; Quality Assurance and Project Management &#171; Pebble in the Still Waters</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/never-opposed-project-manager-is-a-risky-affair/comment-page-1/#comment-2459</link>
		<dc:creator>Never Opposed Project Manager Is A Risky Affair &#8211; Quality Assurance and Project Management &#171; Pebble in the Still Waters</dc:creator>
		<pubDate>Fri, 01 Feb 2013 17:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=968#comment-2459</guid>
		<description><![CDATA[[...] on itknowledgeexchange.techtarget.com Share this:TwitterFacebookLike this:LikeBe the first to like this.   Categories [...]]]></description>
		<content:encoded><![CDATA[<p>[...] on itknowledgeexchange.techtarget.com Share this:TwitterFacebookLike this:LikeBe the first to like this.   Categories [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/never-opposed-project-manager-is-a-risky-affair/comment-page-1/#comment-2449</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Fri, 01 Feb 2013 05:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=968#comment-2449</guid>
		<description><![CDATA[&lt;EM&gt;...timelines that you assign or decide...&lt;/EM&gt;
&#160;
Time estimates should be made by estimators, rather than by project managers or developers; and the estimators should be accountable for missed deadlines. If they can&#039;t get it right, how can anyone be expected to?
&#160;
Estimating is not a trivial task for a project. It should be done by qualified individuals who understand time studies. It definitely should not be done by the individuals doing the actual task work, though those individuals may have useful and valid input.
&#160;
A capital construction project often relies upon external professional estimating services. E.g., see &lt;a href=&quot;http://www.tempestcompany.com/estimating.asp&quot; rel=&quot;nofollow&quot;&gt;http://www.tempestcompany.com/estimating.asp&lt;/A&gt;&#160;. Professional estimators are not unheard of in many areas outside of software projects. Is there any solid reason why a software estimate should be different?
&#160;
That&#039;s not asking why external estimators are not brought in for software project estimates. It&#039;s asking why separated duties for estimates are so unusual. We just go along assuming that estimates are often meaningless.
&#160;
Tom
Tom]]></description>
		<content:encoded><![CDATA[<p><em>&#8230;timelines that you assign or decide&#8230;</em><br />
&nbsp;<br />
Time estimates should be made by estimators, rather than by project managers or developers; and the estimators should be accountable for missed deadlines. If they can&#8217;t get it right, how can anyone be expected to?<br />
&nbsp;<br />
Estimating is not a trivial task for a project. It should be done by qualified individuals who understand time studies. It definitely should not be done by the individuals doing the actual task work, though those individuals may have useful and valid input.<br />
&nbsp;<br />
A capital construction project often relies upon external professional estimating services. E.g., see <a href="http://www.tempestcompany.com/estimating.asp" rel="nofollow">http://www.tempestcompany.com/estimating.asp</a>&nbsp;. Professional estimators are not unheard of in many areas outside of software projects. Is there any solid reason why a software estimate should be different?<br />
&nbsp;<br />
That&#8217;s not asking why external estimators are not brought in for software project estimates. It&#8217;s asking why separated duties for estimates are so unusual. We just go along assuming that estimates are often meaningless.<br />
&nbsp;<br />
Tom<br />
Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>
