 




<?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: What&#8217;s your beef with the agile development methodology?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/total-cio/whats-your-beef-with-the-agile-development-methodology/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/total-cio/whats-your-beef-with-the-agile-development-methodology/</link>
	<description>A SearchCIO.com blog</description>
	<lastBuildDate>Sat, 11 May 2013 17:51:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: DBAndJ2EEInstruction</title>
		<link>http://itknowledgeexchange.techtarget.com/total-cio/whats-your-beef-with-the-agile-development-methodology/#comment-481</link>
		<dc:creator>DBAndJ2EEInstruction</dc:creator>
		<pubDate>Fri, 07 Aug 2009 18:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/total-cio/?p=848#comment-481</guid>
		<description><![CDATA[Agile will save money for both the developer and the client why?
1)Stakeholder involvement states each task needs to be broken down to 2 week increments..this means that no task should take longer than 2 weeks if it does 
the bottlenecks should be identified and cleared up
2)Prioritisation of tasks..most of the time offshore houses will code up something
and toss it over the wall back to production. Stakeholders may say this is not what i asked for..if documentation and language translation come last say so in the task schedule..remember this is your money so you need to be pro-active about whats important and what can wait
3)Assignment of resources can be re-adjusted..this happens alot in offshore situations where a new recruit just off the streets doesnt undertand the intricacies of the problem domain..most acute in Scientific, Financial or HealthCare sectors..Having an Analyst that understands the domain is critical to ensuring the requirement from the business requirement translates to clear verifiable testable technical requirement
for Further information on when to use Agile Processing Methodology I invite you to look at
http://www.ambysoft.com/
Martin Gainty
(e)mgainty@hotmail.com
07 Aug 2009]]></description>
		<content:encoded><![CDATA[<p>Agile will save money for both the developer and the client why?<br />
1)Stakeholder involvement states each task needs to be broken down to 2 week increments..this means that no task should take longer than 2 weeks if it does<br />
the bottlenecks should be identified and cleared up<br />
2)Prioritisation of tasks..most of the time offshore houses will code up something<br />
and toss it over the wall back to production. Stakeholders may say this is not what i asked for..if documentation and language translation come last say so in the task schedule..remember this is your money so you need to be pro-active about whats important and what can wait<br />
3)Assignment of resources can be re-adjusted..this happens alot in offshore situations where a new recruit just off the streets doesnt undertand the intricacies of the problem domain..most acute in Scientific, Financial or HealthCare sectors..Having an Analyst that understands the domain is critical to ensuring the requirement from the business requirement translates to clear verifiable testable technical requirement<br />
for Further information on when to use Agile Processing Methodology I invite you to look at<br />
<a href="http://www.ambysoft.com/" rel="nofollow">http://www.ambysoft.com/</a><br />
Martin Gainty<br />
(e)mgainty@hotmail.com<br />
07 Aug 2009</p>
]]></content:encoded>
	</item>
</channel>
</rss>
