<?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: Performance Requirements and Jedi Mind Tricks</title>
	<atom:link href="http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/</link>
	<description>Performance Testing with a LoadRunner focus</description>
	<lastBuildDate>Sun, 25 Jul 2010 20:27:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: BDB</title>
		<link>http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-566</link>
		<dc:creator>BDB</dc:creator>
		<pubDate>Thu, 07 Sep 2006 14:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-566</guid>
		<description>CCAL Ninth Rule of Testing: When &quot;Accepted by the Business&quot; is used to close defects, you know for a fact that many long overtime testing shifts  are coming soon. 

The CRUNCH always occurs at testing. Development gets behind.... code is not delivered on time.... defects abound.... development can&#039;t keep up.... red flags start to raise.... implementation is threatened.... execs vow to &quot;keep on schedule&quot;.... development needs to cover their hineys.... the business is under pressure.... &quot;Ok, we&#039;ll go with what we have and fix the rest in place&quot;.... 

Mean while, the testers are doing the best they can just to get any test cases or scripts to run while everyone jacks with the testing environment, rolling new code every hour, and oh yes....... let&#039;s just go into 24 hour mode and test around the clock. Uh, yes.... that&#039;s the ticket.

Good grief. When will they ever learn.</description>
		<content:encoded><![CDATA[<p>CCAL Ninth Rule of Testing: When &#8220;Accepted by the Business&#8221; is used to close defects, you know for a fact that many long overtime testing shifts  are coming soon. </p>
<p>The CRUNCH always occurs at testing. Development gets behind&#8230;. code is not delivered on time&#8230;. defects abound&#8230;. development can&#8217;t keep up&#8230;. red flags start to raise&#8230;. implementation is threatened&#8230;. execs vow to &#8220;keep on schedule&#8221;&#8230;. development needs to cover their hineys&#8230;. the business is under pressure&#8230;. &#8220;Ok, we&#8217;ll go with what we have and fix the rest in place&#8221;&#8230;. </p>
<p>Mean while, the testers are doing the best they can just to get any test cases or scripts to run while everyone jacks with the testing environment, rolling new code every hour, and oh yes&#8230;&#8230;. let&#8217;s just go into 24 hour mode and test around the clock. Uh, yes&#8230;. that&#8217;s the ticket.</p>
<p>Good grief. When will they ever learn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Moncrieff</title>
		<link>http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-561</link>
		<dc:creator>Stuart Moncrieff</dc:creator>
		<pubDate>Wed, 06 Sep 2006 12:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-561</guid>
		<description>Yep, much catchier.</description>
		<content:encoded><![CDATA[<p>Yep, much catchier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stu (uk)</title>
		<link>http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-558</link>
		<dc:creator>Stu (uk)</dc:creator>
		<pubDate>Tue, 05 Sep 2006 14:54:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.myloadtest.com/performance-requirements-and-jedi-mind-tricks/#comment-558</guid>
		<description>These aren&#039;t the defects you are looking for.....</description>
		<content:encoded><![CDATA[<p>These aren&#8217;t the defects you are looking for&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
