<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>&amp;quot;What is QA doing?!?&amp;quot;:  Moving QA into an iterative, Agile environment with 'P0' testing</title><link>http://blogs.msdn.com/jeffdw/archive/2007/09/23/what-is-qa-doing-kill-this-question-quickly-or-it-will-kill-you.aspx</link><description>Our single biggest misstep in our test approach last version was that we failed to sufficiently change our testing methodologies to fit the Agile environment under which we developed our V1 product. As we had done in our previous years here at MS, we</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: "What is QA doing?!?":  Moving QA into an iterative, Agile environment with 'P0' testing</title><link>http://blogs.msdn.com/jeffdw/archive/2007/09/23/what-is-qa-doing-kill-this-question-quickly-or-it-will-kill-you.aspx#5846727</link><pubDate>Sat, 03 Nov 2007 01:48:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5846727</guid><dc:creator>xuanthy</dc:creator><description>&lt;p&gt;Interesting blog. &amp;nbsp;We are also testing in a scrum environment and running into the same challenges.&lt;/p&gt;</description></item><item><title>re: "What is QA doing?!?":  Moving QA into an iterative, Agile environment with 'P0' testing</title><link>http://blogs.msdn.com/jeffdw/archive/2007/09/23/what-is-qa-doing-kill-this-question-quickly-or-it-will-kill-you.aspx#6024957</link><pubDate>Fri, 09 Nov 2007 21:49:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6024957</guid><dc:creator>Randy Eppinger</dc:creator><description>&lt;P&gt;OK. &amp;nbsp;This is a little scary. &amp;nbsp;What you describe in V1 sounds an awful lot like what I had planned. &amp;nbsp;We do more of an XP like agile with one week iterations. &amp;nbsp;The QA team is going to test each story as it was completed, updating web tests written with VS2005 for Testers. &amp;nbsp;It is expected they will lag behind, but it sounds like they may quickly fall far enough behind that it will be problematic. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;Keep it coming, I'm ready to hear more about the new way and why it works better!&lt;/P&gt;</description></item></channel></rss>