<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Technologists Are Never the Problem</title>
		<description>Discuss Technologists Are Never the Problem</description>
		<link>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05</link>
		<lastBuildDate>Sat, 18 May 2013 14:10:40 --800</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://ecaminc.com/index.php/component/jcomments/feed/com_content/300/10" rel="self" type="application/rss+xml" />
		<item>
			<title>Samad Aidane says:</title>
			<link>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-366</link>
			<description><![CDATA[Todd, Great article as usual. The attitude from the leadership of this organization is unfortunately not uncommon in some technical circles. Somehow, such technical roles believe in and live by the principle that overall success of a project is somebody else's job not theirs. Yet, they have such contempt for project managers and management in general. They folks be extremely uncooperative on projects and see project managers as an unnecessary overhead. I worked with some of these roles. They prefer to live in a detached universe as if the world around them does not exist. On projects, they are only concerned about their own tasks not how they fit in the overall scheme of the project. They can care less about what’s happening around them. It is like that old saying: as long as the operation is successful, it does not matter if the patient dies. These are the same people that will surprise the project manager at the wrong time and place with pre-requisites and interdependenci es required for them to do their job. They take no responsibility. They are the same people who will blame the PM when the project is in trouble. The sad thing is that they get away with this attitude because in most organizations this lack of accountability is an epidemic. This attitude unfortunately is what Project Managers have to deal with every day on projects. Ironically, this organization’s leadership does not see it but they clearly need your help to instill in their members attitudes and values that would make them productive citizens of project world.]]></description>
			<dc:creator>Samad Aidane</dc:creator>
			<pubDate>Sat, 24 Mar 2012 14:43:34 --800</pubDate>
			<guid>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-366</guid>
		</item>
		<item>
			<title>Simon Rhodes says:</title>
			<link>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-364</link>
			<description><![CDATA[His answer was wrong and you make good points - but it misses the fundemental issue - who owns the data. It is the business - those who transform it have no - I say again absoluletly no responsibility for the data quality. And it is data quality that is the cause of many project failures @5imonRhodes]]></description>
			<dc:creator>Simon Rhodes</dc:creator>
			<pubDate>Thu, 08 Mar 2012 00:28:28 --800</pubDate>
			<guid>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-364</guid>
		</item>
		<item>
			<title>Saurabh Gautam says:</title>
			<link>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-363</link>
			<description><![CDATA[Sir, This is an excellent read. I wish that it catches eye of every manager,PL,TL. I abide by the SDLC process but its a repetitive cycle of requirements and development and sometimes when the code is laid; we get the news that the requirements have changed. This adds to the frustation of all the team members. But I would not say that the Customer didn't care about the phases under development; there lies the miscommunicatio n between what we"team" have been doing and what they"customer" are asking us to do.]]></description>
			<dc:creator>Saurabh Gautam</dc:creator>
			<pubDate>Tue, 06 Mar 2012 10:15:01 --800</pubDate>
			<guid>http://ecaminc.com/index.php/blog/59-generalblog/300-2012-03-05#comment-363</guid>
		</item>
	</channel>
</rss>
