<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Asking for the wrong things</title>
	<link>http://notwaving.net/wordpress/2006/11/06/asking-for-the-wrong-things/</link>
	<description>Does any of it make any sense?</description>
	<pubDate>Tue, 06 Jan 2009 08:12:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Michael Frzak</title>
		<link>http://notwaving.net/wordpress/2006/11/06/asking-for-the-wrong-things/#comment-90</link>
		<pubDate>Tue, 14 Nov 2006 06:23:44 +0000</pubDate>
		<guid>http://notwaving.net/wordpress/2006/11/06/asking-for-the-wrong-things/#comment-90</guid>
					<description>After working with Agile methods for many years I have come to the conclusion that they do not accurately encompass the relationship between the development community and the end users.  I have always failed to be able to get the users to buy into the investment that they need to make to ensure the true agile process. The technical details of the process pail in comparison to an end user community that wants software delivered yesterday without significant investment. Also unit testing is poorly defined for many developers which means that coverage can either be poor or meaningless. As a process for certain types of projects I would recommend it but in the face of tight deadlines software development processes tend to fail (i.e. diverge from their principles).</description>
		<content:encoded><![CDATA[<p>After working with Agile methods for many years I have come to the conclusion that they do not accurately encompass the relationship between the development community and the end users.  I have always failed to be able to get the users to buy into the investment that they need to make to ensure the true agile process. The technical details of the process pail in comparison to an end user community that wants software delivered yesterday without significant investment. Also unit testing is poorly defined for many developers which means that coverage can either be poor or meaningless. As a process for certain types of projects I would recommend it but in the face of tight deadlines software development processes tend to fail (i.e. diverge from their principles).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
