<?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: Things that can hamper the success of a software development project.</title>
	<atom:link href="http://blogs.circlesource.com/2009/02/03/things-that-can-hamper-the-success-of-a-software-development-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.circlesource.com/2009/02/03/things-that-can-hamper-the-success-of-a-software-development-project/</link>
	<description>CircleSource Technical Talent ShowCase</description>
	<lastBuildDate>Thu, 25 Feb 2010 15:22:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: abhishek.porwal</title>
		<link>http://blogs.circlesource.com/2009/02/03/things-that-can-hamper-the-success-of-a-software-development-project/comment-page-1/#comment-109</link>
		<dc:creator>abhishek.porwal</dc:creator>
		<pubDate>Wed, 04 Feb 2009 05:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.circlesource.com/?p=223#comment-109</guid>
		<description>Estimate is one of the reason, but i have seen other major reasons to fail projects, 1) Project Requirement. 2) Customer expectation

Some time, Requirements are not clear, or development team gets a working old application and ask to treat that as requirement. Project manager does not make SRS or get singoff for that as assuming working app as SRS. This turns out as problem later on, end client will come up with some requirement which was hidden in working application, or some security requirement or say browser compatibility. From customer point of view these hidden features or security requirements were obvious and for successful project these should be implemented, but these things are ignored by development team unknowingly.  These issues can be sorted out before starting project with SRS signoff; and all the stack holder in projects are aware off what will be the outcome of the project.</description>
		<content:encoded><![CDATA[<p>Estimate is one of the reason, but i have seen other major reasons to fail projects, 1) Project Requirement. 2) Customer expectation</p>
<p>Some time, Requirements are not clear, or development team gets a working old application and ask to treat that as requirement. Project manager does not make SRS or get singoff for that as assuming working app as SRS. This turns out as problem later on, end client will come up with some requirement which was hidden in working application, or some security requirement or say browser compatibility. From customer point of view these hidden features or security requirements were obvious and for successful project these should be implemented, but these things are ignored by development team unknowingly.  These issues can be sorted out before starting project with SRS signoff; and all the stack holder in projects are aware off what will be the outcome of the project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
