<?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: What Not to Do &#8211; Project Management Mistakes to Avoid</title>
	<atom:link href="http://www.hanway.co.uk/2008/11/26/what-not-to-do-project-management-mistakes-to-avoid/feed" rel="self" type="application/rss+xml" />
	<link>http://www.hanway.co.uk/2008/11/26/what-not-to-do-project-management-mistakes-to-avoid</link>
	<description>It's a Blog. It's Ciaran. It's for whatever I want it to do.</description>
	<lastBuildDate>Mon, 26 Jul 2010 04:30:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: CB</title>
		<link>http://www.hanway.co.uk/2008/11/26/what-not-to-do-project-management-mistakes-to-avoid/comment-page-1#comment-72221</link>
		<dc:creator>CB</dc:creator>
		<pubDate>Sun, 29 Nov 2009 20:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hanway.co.uk/2008/11/26/what-not-to-do-project-management-mistakes-to-avoid/#comment-72221</guid>
		<description>Ciaran:
Interesting points you&#039;ve made.  I&#039;ve worked on a few projects under a handful of very different project managers and I would say only one has correctly exercised the points you outline above.   In my most recent job, the mistakes made by the Operations Director are almost laughable.  What&#039;s even more surprising is that any comments or suggestions I have for improving the way things work are basically ignored, because they feel they must do things the way they&#039;ve always done. I&#039;m sure this is not new to you either.

Here&#039;s a list of the classic mistakes made (not in any particular order):

&lt;b&gt; #1 - Not keeping the development team informed of the requirements! &lt;/b&gt;
The management team keep themselves to themselves on the ground floor of the building.  Presumably they discuss with the customer any requirements they have for the simulators, any changes they&#039;d like implemented etc.  Amazingly, this information isn&#039;t passed on to the developers until the Ops Manager feels like it. Interesting

&lt;b&gt; #2 - Not keeping the development team informed of the deadlines! &lt;/b&gt;
Likewise, for the same reason as for #1 above, deadlines can change according to client requirements.  The developers generally do not know when they need to deliver by!

&lt;b&gt; #3 - Focusing management effort on less important tasks/costs&lt;/b&gt;
I overheard a senior manager complaining that the annual water bill had gone up by something like £1000 pa.  This is a tangible outlay that can be solved by a tangible solution, i.e. by making people use less water.  However, what if you&#039;re focusing on solving this problem and at the same time having to neglect making a £40k developer more than 50% efficient? It seems to me that £40k pa paid to the developer is written off, and his workrate is only measured on the time he attends his desk and not his output. 

These are just some points that currently frustrate me daily. Needless to say I&#039;m trying to move on!</description>
		<content:encoded><![CDATA[<p>Ciaran:<br />
Interesting points you&#8217;ve made.  I&#8217;ve worked on a few projects under a handful of very different project managers and I would say only one has correctly exercised the points you outline above.   In my most recent job, the mistakes made by the Operations Director are almost laughable.  What&#8217;s even more surprising is that any comments or suggestions I have for improving the way things work are basically ignored, because they feel they must do things the way they&#8217;ve always done. I&#8217;m sure this is not new to you either.</p>
<p>Here&#8217;s a list of the classic mistakes made (not in any particular order):</p>
<p><b> #1 &#8211; Not keeping the development team informed of the requirements! </b><br />
The management team keep themselves to themselves on the ground floor of the building.  Presumably they discuss with the customer any requirements they have for the simulators, any changes they&#8217;d like implemented etc.  Amazingly, this information isn&#8217;t passed on to the developers until the Ops Manager feels like it. Interesting</p>
<p><b> #2 &#8211; Not keeping the development team informed of the deadlines! </b><br />
Likewise, for the same reason as for #1 above, deadlines can change according to client requirements.  The developers generally do not know when they need to deliver by!</p>
<p><b> #3 &#8211; Focusing management effort on less important tasks/costs</b><br />
I overheard a senior manager complaining that the annual water bill had gone up by something like £1000 pa.  This is a tangible outlay that can be solved by a tangible solution, i.e. by making people use less water.  However, what if you&#8217;re focusing on solving this problem and at the same time having to neglect making a £40k developer more than 50% efficient? It seems to me that £40k pa paid to the developer is written off, and his workrate is only measured on the time he attends his desk and not his output. </p>
<p>These are just some points that currently frustrate me daily. Needless to say I&#8217;m trying to move on!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
