<?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; bug fixing</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/bug-fixing/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>Mon, 17 Jun 2013 16:21:04 +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>Each Bug Has An Element Of Cost Associated With It</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/each-bug-has-an-element-of-cost-associated-with-it/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/each-bug-has-an-element-of-cost-associated-with-it/#comments</comments>
		<pubDate>Sat, 25 Jun 2011 18:39:34 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[bug fixing]]></category>
		<category><![CDATA[bug reporting]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/each-bug-has-an-element-of-cost-associated-with-it/</guid>
		<description><![CDATA[Usually it is not the developer’s fault if he build bug in addition to writing code for any application, The seriousness of application may vary from business point of view, the way that application is going to cater to the business management. Even a game code for a gaming company could be as serious as [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/each-bug-has-an-element-of-cost-associated-with-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Benefits of Linking a Bug to its Respective Identifier, Creator and Killer</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-benefits-of-linking-a-bug-to-its-respective-identifier-creator-and-killer/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-benefits-of-linking-a-bug-to-its-respective-identifier-creator-and-killer/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 10:10:47 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[bug fixing]]></category>
		<category><![CDATA[defect]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[project cost]]></category>
		<category><![CDATA[project delay]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[time sheet]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-benefits-of-linking-a-bug-to-its-respective-identifier-creator-and-killer/</guid>
		<description><![CDATA[To evaluate an individual developer or tester at the end of a project, during a project or at the time of appraisal, this data will help in assessment. The developer generating more bugs, the tester coming out with less bugs, the developers taking more time for bug fixing etc. will help in the proper evaluation.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-benefits-of-linking-a-bug-to-its-respective-identifier-creator-and-killer/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>
	</channel>
</rss>
