<?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: Does it Really Work?</title>
	<atom:link href="http://blog.franktrindade.com/2009/03/05/does-it-really-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.franktrindade.com/2009/03/05/does-it-really-work/</link>
	<description>Agile, software and some non-sense</description>
	<lastBuildDate>Thu, 17 Jun 2010 09:41:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: anton</title>
		<link>http://blog.franktrindade.com/2009/03/05/does-it-really-work/comment-page-1/#comment-1015</link>
		<dc:creator>anton</dc:creator>
		<pubDate>Thu, 16 Apr 2009 14:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.franktrindade.com/?p=206#comment-1015</guid>
		<description>I think the the truth is in the middle: the testers should be almost customer and in the same time with technical experience</description>
		<content:encoded><![CDATA[<p>I think the the truth is in the middle: the testers should be almost customer and in the same time with technical experience</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: franktrindade</title>
		<link>http://blog.franktrindade.com/2009/03/05/does-it-really-work/comment-page-1/#comment-404</link>
		<dc:creator>franktrindade</dc:creator>
		<pubDate>Sun, 08 Mar 2009 13:45:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.franktrindade.com/?p=206#comment-404</guid>
		<description>@David,

it depends if the customer knows how to evaluate usability, and my point is exactly that this isn&#039;t always true (and its is not his/her job to do it anyway).

If you say to the customer &quot;Let&#039;s stop testing, it will make us go faster&quot;, he won&#039;t have a clue either, but traditionally in Agile testing is considered very important and under the team&#039;s responsibility, but UX not.

Carlos gives a really simple example in this post (http://www.lixo.org/archives/2008/11/27/balances-between-agile-and-usability/), which I have seen happening in projects, that is delivering lists without search or pagination.

The customer is very happy and cheerful, until he has a lot of data in his system and can&#039;t find anything anymore, but then it is too late to complain about it.

Regards,
Francisco</description>
		<content:encoded><![CDATA[<p>@David,</p>
<p>it depends if the customer knows how to evaluate usability, and my point is exactly that this isn&#8217;t always true (and its is not his/her job to do it anyway).</p>
<p>If you say to the customer &#8220;Let&#8217;s stop testing, it will make us go faster&#8221;, he won&#8217;t have a clue either, but traditionally in Agile testing is considered very important and under the team&#8217;s responsibility, but UX not.</p>
<p>Carlos gives a really simple example in this post (<a href="http://www.lixo.org/archives/2008/11/27/balances-between-agile-and-usability/" rel="nofollow">http://www.lixo.org/archives/2008/11/27/balances-between-agile-and-usability/</a>), which I have seen happening in projects, that is delivering lists without search or pagination.</p>
<p>The customer is very happy and cheerful, until he has a lot of data in his system and can&#8217;t find anything anymore, but then it is too late to complain about it.</p>
<p>Regards,<br />
Francisco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jacksguides.com</title>
		<link>http://blog.franktrindade.com/2009/03/05/does-it-really-work/comment-page-1/#comment-390</link>
		<dc:creator>jacksguides.com</dc:creator>
		<pubDate>Sat, 07 Mar 2009 11:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.franktrindade.com/?p=206#comment-390</guid>
		<description>Given that Agile software development is constantly allowing for users to test and comment on the system, before it is handed over at the end of a traditional waterfall project, how is the user considered left out?
The useability isn&#039;t at the end of the day, up to the developers. If the customer is not happy with it, they  will being it up at the end of the iteration and this can be resolved.
Maybe I am missing the point of the post?

Regards
David
jacksguides.com</description>
		<content:encoded><![CDATA[<p>Given that Agile software development is constantly allowing for users to test and comment on the system, before it is handed over at the end of a traditional waterfall project, how is the user considered left out?<br />
The useability isn&#8217;t at the end of the day, up to the developers. If the customer is not happy with it, they  will being it up at the end of the iteration and this can be resolved.<br />
Maybe I am missing the point of the post?</p>
<p>Regards<br />
David<br />
jacksguides.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Does it Really Work? &#124; Agile bSoftware Development/b &#171; topsoft.us</title>
		<link>http://blog.franktrindade.com/2009/03/05/does-it-really-work/comment-page-1/#comment-373</link>
		<dc:creator>Does it Really Work? &#124; Agile bSoftware Development/b &#171; topsoft.us</dc:creator>
		<pubDate>Thu, 05 Mar 2009 10:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.franktrindade.com/?p=206#comment-373</guid>
		<description>[...] here:  Does it Really Work? &#124; Agile bSoftware Development/b   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] here:  Does it Really Work? | Agile bSoftware Development/b   Share and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
