 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Quality Assurance and Project Management &#187; software build</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/software-build/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/quality-assurance</link>
	<description>Improvement in Quality never ends. There is always a scope of improvement in life...</description>
	<lastBuildDate>Thu, 16 May 2013 18:52:46 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<copyright>2006-2007 </copyright>
	<managingEditor>jaideepkhanduja@gmail.com (Quality Assurance and Project Management)</managingEditor>
	<webMaster>jaideepkhanduja@gmail.com (Quality Assurance and Project Management)</webMaster>
	<image>
		<url>http://itknowledgeexchange.techtarget.com/quality-assurance/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
		<title>Quality Assurance and Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>Improvement in Quality never ends. There is always a scope of improvement in life...</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Quality Assurance and Project Management</itunes:author>
	<itunes:owner>
		<itunes:name>Quality Assurance and Project Management</itunes:name>
		<itunes:email>jaideepkhanduja@gmail.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://itknowledgeexchange.techtarget.com/quality-assurance/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<item>
		<title>Product Version should match with Feedback by Development Team</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/product-version-should-match-with-feedback-by-development-team/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/product-version-should-match-with-feedback-by-development-team/#comments</comments>
		<pubDate>Thu, 26 Nov 2009 10:00:28 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[functional testing]]></category>
		<category><![CDATA[load testing]]></category>
		<category><![CDATA[performance testing]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[product release]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[Regression Testing]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/product-version-should-match-with-feedback-by-development-team/</guid>
		<description><![CDATA[Development Team has finished with a new version of the software product. The product is ready for testing before releasing it to production team provide QC approves it after testing that no severe bugs are there. Test environment is prepared for QC team to perform the complete functional, regression, performance and load testing. Extensive testing is done by QC team and a complete list of bugs is submitted to Development Team. Since the bugs include certain serious bugs, the product can’t be released or be declared ‘ready to launch’ before fixing and verifying these bugs.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/product-version-should-match-with-feedback-by-development-team/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ten Mantras for a software developer</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/215/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/215/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 10:00:40 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[application]]></category>
		<category><![CDATA[application building]]></category>
		<category><![CDATA[Application development]]></category>
		<category><![CDATA[application functionality]]></category>
		<category><![CDATA[application performance]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[bug fixing]]></category>
		<category><![CDATA[bug identification]]></category>
		<category><![CDATA[bug-free]]></category>
		<category><![CDATA[business process]]></category>
		<category><![CDATA[business requirements]]></category>
		<category><![CDATA[Business Rules]]></category>
		<category><![CDATA[code validation]]></category>
		<category><![CDATA[code writing]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[customer experience]]></category>
		<category><![CDATA[end user]]></category>
		<category><![CDATA[process owner]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Software application]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[Software developer]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software functionality]]></category>
		<category><![CDATA[software performance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/215/</guid>
		<description><![CDATA[Lot of efforts can be saved in terms of time and money if we reach to a stage of ‘first time right’ in application development. It has been proven largely that no good application can be built and released without extensive testing. Testing is not developers’ ball game – this is also a well proven fact. Reasons are many as far as it is concerned that why developers can’t build a bug-free application, or why can’t they test on their own. We are not going to discuss those reasons here. Focus here would be on what developers should keep in mind while building an application that it requires minimum efforts and time in all testing stages. As we all know the cost of bug fixing goes manifold, depending on how much distance (in terms of time and project stages) it has covered after development for bug identification. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/215/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Acceptance Testing (UAT)</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/user-acceptance-testing-uat/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/user-acceptance-testing-uat/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 10:00:09 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[appearance testing]]></category>
		<category><![CDATA[bug fixing]]></category>
		<category><![CDATA[business process]]></category>
		<category><![CDATA[business rule]]></category>
		<category><![CDATA[customer specification]]></category>
		<category><![CDATA[defect fixing]]></category>
		<category><![CDATA[functional requirement]]></category>
		<category><![CDATA[functional specification]]></category>
		<category><![CDATA[functional testing]]></category>
		<category><![CDATA[integration test]]></category>
		<category><![CDATA[interfacing]]></category>
		<category><![CDATA[product testing]]></category>
		<category><![CDATA[software bug]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software defect]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[testing lifecycle]]></category>
		<category><![CDATA[UAT]]></category>
		<category><![CDATA[user acceptance test]]></category>
		<category><![CDATA[validation testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/user-acceptance-testing-uat/</guid>
		<description><![CDATA[UAT or user acceptance testing comes as the last exercise in software testing lifecycle. It is probably the first phase or beginning of customer preparing to takeover the charge of the product. Actually this is a sort of test drive by a perspective buyer who has studied well about a car, has made up his mind to buy it but wants to satisfy himself by actually sitting in the car and driving it. Even if you have made up your mind to buy a particular model and after sitting in the car or after having the test drive, something does not suit you, the decision can take 180 degrees turn.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/user-acceptance-testing-uat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who owns the Q-Tag in a software development company?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 10:00:20 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[bugs report]]></category>
		<category><![CDATA[business analyst]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[implementation team]]></category>
		<category><![CDATA[product approval]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project management framework]]></category>
		<category><![CDATA[project methodology]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[Q-tag]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[Quality-tag]]></category>
		<category><![CDATA[re-testing]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[team]]></category>
		<category><![CDATA[test report]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[testing team]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/</guid>
		<description><![CDATA[Q-tag has to be on each of the stakeholder in a software project. When each and every person wears a Q-tag – the analysis, building, testing and implementation will be more justified. Otherwise there will always be a big question at the time of failure of a product build – that who is responsible? 
]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>If you don’t change with the ‘Change’ you get [ex][change]d</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 10:00:17 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business requirement]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[development phase]]></category>
		<category><![CDATA[product delay]]></category>
		<category><![CDATA[product launch]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project timelines]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[test phase]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/</guid>
		<description><![CDATA[The requirements keep changing, as the business. Only thing that varies is the pace of change in requirements. Overlooking changes happening in the business process at customer end after freezing requirements will result only in undesirable product. Both customer and vendor have to understand this and keep overseeing the changes rather than overlooking.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five stages in a project when Software Tester becomes Quality Analyst</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-stages-in-a-project-when-software-tester-becomes-quality-analyst/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-stages-in-a-project-when-software-tester-becomes-quality-analyst/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 10:00:31 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[analysis]]></category>
		<category><![CDATA[customer requirement analysis]]></category>
		<category><![CDATA[functional testing]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[load testing]]></category>
		<category><![CDATA[performance testing]]></category>
		<category><![CDATA[product analysis]]></category>
		<category><![CDATA[product functionality]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[quality analyst]]></category>
		<category><![CDATA[security testing]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software document]]></category>
		<category><![CDATA[software documentation]]></category>
		<category><![CDATA[software functionality]]></category>
		<category><![CDATA[software performance]]></category>
		<category><![CDATA[Software tester]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[test case]]></category>
		<category><![CDATA[test coverage]]></category>
		<category><![CDATA[test performance]]></category>
		<category><![CDATA[Test Plan]]></category>
		<category><![CDATA[test result]]></category>
		<category><![CDATA[testing process]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-stages-in-a-project-when-software-tester-becomes-quality-analyst/</guid>
		<description><![CDATA[A software tester evaluates software based on certain parameters. These parameters are set as per product, customer and organization requirements. Testing could be just of functional features or include load, performance and security. For any parameters a tester has to work as quality analyst to understand requirements, features and accordingly build test cases and perform test. This is the quality control part. On quality assurance front the quality team has to build standards for requirement freezing, planning, development, implementation and post implementation phases of a project.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-stages-in-a-project-when-software-tester-becomes-quality-analyst/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
