<?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>Jawed's Blog &#187; Project</title>
	<atom:link href="http://www.jawed.info/blog/tag/project/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jawed.info/blog</link>
	<description>reading without reflecting is like eating without digesting</description>
	<lastBuildDate>Fri, 04 Nov 2011 07:10:39 +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>Top 10 Ways that Guarantee the Failure of a Project</title>
		<link>http://www.jawed.info/blog/2010/04/02/top-10-ways-that-guarantee-the-failure-of-a-project/</link>
		<comments>http://www.jawed.info/blog/2010/04/02/top-10-ways-that-guarantee-the-failure-of-a-project/#comments</comments>
		<pubDate>Fri, 02 Apr 2010 04:42:23 +0000</pubDate>
		<dc:creator>Jawed</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[Tools & Technologies]]></category>

		<guid isPermaLink="false">http://www.jawed.info/blog/index.php/2006/12/08/top-10-ways-that-guarantee-the-failure-of-a-project/</guid>
		<description><![CDATA[I was reading an article about why projects fail and found interesting points and the following list has been inspired by actual mistakes encountered in real-world systems projects.

1. Don’t use a specific methodology because coding is all that is really important.
2. Create the project plan by working backwards from a drop-dead system completion date.
3. Don’t bother with a data model. Just build whatever tables you need.
4. Use a Technical Lead that has never built a similar system. Hiring such talent is too expensive.
5. Hire forty developers to make the coding go faster.
6. Selecting wrong tools and technologies for development
7. Three months before the system goes live, assign one junior developer to handle the data migration.
8. Skip the testing phase because the project is way behind schedule.
9. Change the system to support critical new requirements discovered during final development.
10. Buy a commercial, off-the-shelf package and customize it... a lot.<div class="read_more"><a href="http://www.jawed.info/blog/2010/04/02/top-10-ways-that-guarantee-the-failure-of-a-project/">read more</a></div>]]></description>
		<wfw:commentRss>http://www.jawed.info/blog/2010/04/02/top-10-ways-that-guarantee-the-failure-of-a-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Communication for Project biding</title>
		<link>http://www.jawed.info/blog/2006/10/10/communication-for-project-biding/</link>
		<comments>http://www.jawed.info/blog/2006/10/10/communication-for-project-biding/#comments</comments>
		<pubDate>Tue, 10 Oct 2006 04:42:04 +0000</pubDate>
		<dc:creator>Jawed</dc:creator>
				<category><![CDATA[Fun & Humour]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Project]]></category>

		<guid isPermaLink="false">http://www.jawed.info/blog/index.php/2006/10/10/communication-for-project-biding/</guid>
		<description><![CDATA[One of my friend send me an email about how communication goes with in a company when new project proposal is under review. It is wonderful and depicts exactly what people at different level think about a new project.<div class="read_more"><a href="http://www.jawed.info/blog/2006/10/10/communication-for-project-biding/">read more</a></div>]]></description>
		<wfw:commentRss>http://www.jawed.info/blog/2006/10/10/communication-for-project-biding/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

