<?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>MSDN Utopia : QA</title><link>http://blogs.msdn.com/salvapatuel/archive/tags/QA/default.aspx</link><description>Tags: QA</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSF Agile and service packs management</title><link>http://blogs.msdn.com/salvapatuel/archive/2007/04/10/msf-agile-and-service-packs-management.aspx</link><pubDate>Tue, 10 Apr 2007 18:02:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2074330</guid><dc:creator>Salva Patuel</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/salvapatuel/comments/2074330.aspx</comments><wfw:commentRss>http://blogs.msdn.com/salvapatuel/commentrss.aspx?PostID=2074330</wfw:commentRss><description>&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;Not a while ago, a customer asked me about how to incorporate the service packs and hot fixes to the agile development process, this triggered an interesting debate about the importance of a QA and release manager.&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;The UAT environment &lt;U&gt;always&lt;/U&gt;&amp;nbsp;must reflect the live environment, this means that the automatic updates should be off (or downloads without installing them), otherwise hot fixes and service packs will alter the test environment.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;Every change in the environment should go through a new iteration, this sometimes causes confusion when developers thinks that the agile iteration will be only followed if a change in the code is introduced. This is not correct, Agile is not about development only, is about a product life cycle that includes the environment where the software will run.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;A change on the environment will trigger a new iteration, where the product manager needs to approve (and justify) the change. This can be a security fix that affects the production environment. The iteration will not trigger an automatic change on the code (unless specified by the update) but the code will be included on the new iteration.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;At this stage we have a new build ready to install. The QA manager should install the service packs or hot fixes on the UAT environment and install the build. The entire test must be executed on this new environment and the QA team will raise any problem detected as a normal iteration. Once the QA manager signs off the build under the new environment this will be hand over to the release manager for the production environment upgrade.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;At the end of this iteration a new build has been generated with the upgrade notes attached, this will help in the future to track down the context where the software has been tested.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="TEXT-ALIGN: justify"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"&gt;This post should help you to understand that the MSF Agile is a full life cycle methodology that can be extended to all the areas that affects the software, including infrastructure.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2074330" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/salvapatuel/archive/tags/MSF/default.aspx">MSF</category><category domain="http://blogs.msdn.com/salvapatuel/archive/tags/Agile/default.aspx">Agile</category><category domain="http://blogs.msdn.com/salvapatuel/archive/tags/QA/default.aspx">QA</category><category domain="http://blogs.msdn.com/salvapatuel/archive/tags/TFS/default.aspx">TFS</category><category domain="http://blogs.msdn.com/salvapatuel/archive/tags/Best+practices/default.aspx">Best practices</category></item></channel></rss>