<?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>E &#187; DEVELOPMENT</title>
	<atom:link href="http://www.sabarish.com/category/development/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sabarish.com</link>
	<description></description>
	<lastBuildDate>Thu, 06 Aug 2009 19:32:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Requirements Analysis Problems</title>
		<link>http://www.sabarish.com/requirements-analysis-problems-21.html</link>
		<comments>http://www.sabarish.com/requirements-analysis-problems-21.html#comments</comments>
		<pubDate>Wed, 05 Dec 2007 14:54:00 +0000</pubDate>
		<dc:creator>Sabarish</dc:creator>
				<category><![CDATA[DEVELOPMENT]]></category>
		<category><![CDATA[REQUIREMENTS]]></category>

		<guid isPermaLink="false">http://www.sabarish.com/?p=21</guid>
		<description><![CDATA[In an earlier post I&#8217;d lamented about the problems in managing requirements, this post probably reads as a prequel to that one. What are the real problems when it comes to requirements analysis?
Meryl K. Evans of the lockergnome identifies 5 specific issues:

Customers Don’t Know What They Want
Requirements Change During the Project
Timeline Trouble
Communication Gaps
Customer Organization Politics

True, [...]]]></description>
		<wfw:commentRss>http://www.sabarish.com/requirements-analysis-problems-21.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Breaking Down Software Development Roles</title>
		<link>http://www.sabarish.com/breaking-down-software-development-roles-19.html</link>
		<comments>http://www.sabarish.com/breaking-down-software-development-roles-19.html#comments</comments>
		<pubDate>Fri, 26 Oct 2007 19:30:00 +0000</pubDate>
		<dc:creator>Sabarish</dc:creator>
				<category><![CDATA[DEVELOPMENT]]></category>
		<category><![CDATA[PROGRAMMING]]></category>
		<category><![CDATA[SOFTWARE]]></category>
		<category><![CDATA[e]]></category>

		<guid isPermaLink="false">http://www.sabarish.com/?p=19</guid>
		<description><![CDATA[As a IT professional, I&#8217;ve often found myself at a loss when I&#8217;ve had to explain my job concisely. Usually following the informal pleasantries, including hellos, name exchanges and handshakes is the dreaded &#8220;So, what do you do?&#8221;
Um&#8217; I&#8217;m an IT professional.
Okay, but what do you do?
I um.. develop software.
Develop software?
Well.. I do requirements analysis, [...]]]></description>
		<wfw:commentRss>http://www.sabarish.com/breaking-down-software-development-roles-19.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Future of Software Development</title>
		<link>http://www.sabarish.com/the-future-of-software-development-18.html</link>
		<comments>http://www.sabarish.com/the-future-of-software-development-18.html#comments</comments>
		<pubDate>Fri, 19 Oct 2007 19:35:00 +0000</pubDate>
		<dc:creator>Sabarish</dc:creator>
				<category><![CDATA[DEVELOPMENT]]></category>
		<category><![CDATA[PROCESS]]></category>
		<category><![CDATA[PROGRAMMING]]></category>
		<category><![CDATA[SOFTWARE]]></category>
		<category><![CDATA[e]]></category>

		<guid isPermaLink="false">http://www.sabarish.com/?p=18</guid>
		<description><![CDATA[Software development has come a full circle states Alex Iskold in a scathing, pull-no-punches broadside upon the Waterfall model.
Read it here: the future of software development
Alex states that arrogance was the main problem with the waterfall model. The arrogance he argues came from the fact that we believed that we could always engineer the perfect [...]]]></description>
		<wfw:commentRss>http://www.sabarish.com/the-future-of-software-development-18.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Iterative vs. waterfall software development</title>
		<link>http://www.sabarish.com/iterative-vs-waterfall-software-development-8.html</link>
		<comments>http://www.sabarish.com/iterative-vs-waterfall-software-development-8.html#comments</comments>
		<pubDate>Wed, 03 Oct 2007 22:24:00 +0000</pubDate>
		<dc:creator>Sabarish</dc:creator>
				<category><![CDATA[DEVELOPMENT]]></category>
		<category><![CDATA[PROCESS]]></category>
		<category><![CDATA[REQUIREMENTS]]></category>

		<guid isPermaLink="false">http://www.sabarish.com/?p=8</guid>
		<description><![CDATA[Nowadays, this question seems to figure at every technical interview that that I been involved with (at either side of the table). What would you choose &#8211; Waterfall model or the Iterative approach?
The correct answer &#8211; it depends.
The usual answer &#8211; some mumbling about extreme programming (followed barely disguised rant on how one was forced [...]]]></description>
		<wfw:commentRss>http://www.sabarish.com/iterative-vs-waterfall-software-development-8.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
