<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Me.Tech() &#187; Project Mgmt</title>
	<atom:link href="http://riteshnayak.com/blog/category/project-mgmt/feed/" rel="self" type="application/rss+xml" />
	<link>http://riteshnayak.com/blog</link>
	<description>my technology blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 08:01:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>10 Project Management Risks</title>
		<link>http://riteshnayak.com/blog/2007/07/06/10-project-management-risks/</link>
		<comments>http://riteshnayak.com/blog/2007/07/06/10-project-management-risks/#comments</comments>
		<pubDate>Fri, 06 Jul 2007 11:42:12 +0000</pubDate>
		<dc:creator>Ritesh</dc:creator>
				<category><![CDATA[Project Mgmt]]></category>

		<guid isPermaLink="false">http://riteshnayak.com/blog/2007/07/06/10-project-management-risks/</guid>
		<description><![CDATA[The 10 mistakes that put projects at risk of failure include: * Never committing to project success. * Freezing the schedule and budget before a project is sufficiently understood. * Overscoping a solution. * Circumventing the application development organization altogether. * Underestimating the complexity of a problem. * Being stingy with subject-matter experts, in which [...]]]></description>
			<content:encoded><![CDATA[<p>The 10 mistakes that put projects at risk of failure include:</p>
<p>* Never committing to project success.<br />
* Freezing the schedule and budget before a project is sufficiently understood.<br />
* Overscoping a solution.<br />
* Circumventing the application development organization altogether.<br />
* Underestimating the complexity of a problem.<br />
* Being stingy with subject-matter experts, in which their participation is not sufficient.<br />
* Choosing the wrong project leadership.<br />
* Distrusting managers who have had tasks delegated to them.<br />
* Jumping into development without enough research.<br />
* Suppressing bad news, in which dialogue is insufficient.</p>
<p>Courtesy : <a href="http://weblog.infoworld.com/techwatch/" target="_blank">InfoWorld TechWatch </a></p>
]]></content:encoded>
			<wfw:commentRss>http://riteshnayak.com/blog/2007/07/06/10-project-management-risks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

