 




<?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 quality assurance</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/software-quality-assurance/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>Bugs are invincible, developers have to be convincible</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/bugs-are-invincible-developers-have-to-be-convincible/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/bugs-are-invincible-developers-have-to-be-convincible/#comments</comments>
		<pubDate>Mon, 19 Jan 2009 10:14:34 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Control Management]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/bugs-are-invincible-developers-have-to-be-convincible/</guid>
		<description><![CDATA[Bugs are often invincible during development, especially in large projects when multiple sub-teams of developers are working on development of different sub-modules of the project. The software developed (or during development) will always appear innocent and bug-free to the team of developers. It is the tester’s tough task to puncture the software and find out [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/bugs-are-invincible-developers-have-to-be-convincible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top 5 Quality killers in a software product</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/top-5-quality-killers-in-a-software-product/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/top-5-quality-killers-in-a-software-product/#comments</comments>
		<pubDate>Mon, 12 Jan 2009 10:04:30 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business management]]></category>
		<category><![CDATA[business requirements]]></category>
		<category><![CDATA[customer requirements]]></category>
		<category><![CDATA[defect free software]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[Project Development]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software requirement]]></category>
		<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=83</guid>
		<description><![CDATA[In software development project what matters most is the timely accurate delivery that gives the benefit of defect free product, customer satisfaction, profits, market edge, growth, motivation across the organization etc. All this is not easy to achieve having so many enemies in and outside the organizations that mars the development progress or a sub-standard [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/top-5-quality-killers-in-a-software-product/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Quality – Overlooked or Underestimated – both are dangerous!</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/software-quality-%e2%80%93-overlooked-or-underestimated-%e2%80%93-both-are-dangerous/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/software-quality-%e2%80%93-overlooked-or-underestimated-%e2%80%93-both-are-dangerous/#comments</comments>
		<pubDate>Wed, 24 Dec 2008 10:04:09 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[ChangeManagement]]></category>
		<category><![CDATA[Development Manager]]></category>
		<category><![CDATA[Project Development]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[SQA]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/software-quality-%e2%80%93-overlooked-or-underestimated-%e2%80%93-both-are-dangerous/</guid>
		<description><![CDATA[The goal of any software organization is to develop software applications in-house, or co-develop with an external agency, that meet and exceed internationally accepted quality standards. Every one knows it, that the key role in this is of QA department. With this intention, a dedicated QA department is structured in the organization, for the purpose. [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/software-quality-%e2%80%93-overlooked-or-underestimated-%e2%80%93-both-are-dangerous/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Create, Build and Maintain Harmony between tester and developer</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/how-to-create-build-and-maintain-harmony-between-tester-and-developer/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/how-to-create-build-and-maintain-harmony-between-tester-and-developer/#comments</comments>
		<pubDate>Fri, 28 Nov 2008 09:55:03 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[developer]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software deployment]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software requirement]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/how-to-create-build-and-maintain-harmony-between-tester-and-developer/</guid>
		<description><![CDATA[‘Create’ means the first time effort to generate a harmony between a tester and a developer working on the same project. ‘Build’ is the next stage after create to harmonize the professional relationship between a tester and developer. This step will bring the strength in the relationship. ‘Maintain’ is not only the sustenance of this [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/how-to-create-build-and-maintain-harmony-between-tester-and-developer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release for testing – a tester’s paradigm</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/new-release-for-testing-%e2%80%93-a-tester%e2%80%99s-paradigm/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/new-release-for-testing-%e2%80%93-a-tester%e2%80%99s-paradigm/#comments</comments>
		<pubDate>Wed, 26 Nov 2008 10:11:50 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software release]]></category>
		<category><![CDATA[software requirement]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/new-release-for-testing-%e2%80%93-a-tester%e2%80%99s-paradigm/</guid>
		<description><![CDATA[A new software release for testing could be a new product or major changes in the existing software. In either case the bugs report should have a new version number for control purposes. Although in case of a new release of existing software, the existing bugs can be referred to but that does not mean [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/new-release-for-testing-%e2%80%93-a-tester%e2%80%99s-paradigm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Challenges of Development/Testing and Open Source Test (OST) Tools</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/challenges-of-developmenttesting-and-open-source-test-ost-tools/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/challenges-of-developmenttesting-and-open-source-test-ost-tools/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 10:14:31 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[.OST files]]></category>
		<category><![CDATA[AJAX]]></category>
		<category><![CDATA[Bug Control Management]]></category>
		<category><![CDATA[functional testing]]></category>
		<category><![CDATA[HTMLUnit]]></category>
		<category><![CDATA[load testing]]></category>
		<category><![CDATA[Open Source Testing Tools]]></category>
		<category><![CDATA[performance testing]]></category>
		<category><![CDATA[PushToTest]]></category>
		<category><![CDATA[RIA]]></category>
		<category><![CDATA[Selenium]]></category>
		<category><![CDATA[SOA]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[Software testing methodologies]]></category>
		<category><![CDATA[TestGen4Web]]></category>
		<category><![CDATA[testing tools]]></category>
		<category><![CDATA[testingtool]]></category>
		<category><![CDATA[Traditional Testing Tools]]></category>
		<category><![CDATA[volume testing]]></category>
		<category><![CDATA[Web2.0]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/challenges-of-developmenttesting-and-open-source-test-ost-tools/</guid>
		<description><![CDATA[In today’s scenario when the schedules are tight, budgets are low and different technologies being used, software developers and testers are having great challenges of building/testing/releasing bug-free software by meeting all criterions. The question arises here is – how to cover all the development/testing requirements that to in such a short span of time with [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/challenges-of-developmenttesting-and-open-source-test-ost-tools/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>20 essential points for a tester</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/20-essential-points-for-a-tester/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/20-essential-points-for-a-tester/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 10:11:19 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/20-essential-points-for-a-tester/</guid>
		<description><![CDATA[1.Focus on Quality Policy, Strategy, Test Plan, Test Cases. 2.Maintain heartfelt sympathies with developers who are developing Bugs (and their impact!). 3.Raise your anxiety higher for any software coming to you for testing. 4.Your first and foremost priority is to prevent the damage a bug spreads across the product. 5.Investigate the damage (impact of bug, [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/20-essential-points-for-a-tester/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Various Stages of a Bug</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/various-stages-of-a-bug/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/various-stages-of-a-bug/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 10:10:25 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/various-stages-of-a-bug/</guid>
		<description><![CDATA[A bug right from its insertion into the software till its removal crosses through different stages. These different stages of a bug formulate bug lifecycle. Each stage has an action and meaning connected to it. Various stages of a bug are: Unconceived: A bug that has to come into a future software, not even knowing [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/various-stages-of-a-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug Control Management &#8211; a void promise! A flawed process! Or a process insanity!</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-a-void-promise-a-flawed-process-or-a-process-insanity/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-a-void-promise-a-flawed-process-or-a-process-insanity/#comments</comments>
		<pubDate>Mon, 27 Oct 2008 10:15:04 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Control Management]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-a-void-promise-a-flawed-process-or-a-process-insanity/</guid>
		<description><![CDATA[There are three ways of functioning for any software organizations. First ways is to develop software and deliver it into the market. The survival for these sorts of organizations is too difficult and short. Second category of organization has a well placed “Quality” department in place. The quality department is responsible for ensuring a bug [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-a-void-promise-a-flawed-process-or-a-process-insanity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug Control Management vs Bug Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-vs-bug-management/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-vs-bug-management/#comments</comments>
		<pubDate>Fri, 24 Oct 2008 10:15:27 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Control Management]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-vs-bug-management/</guid>
		<description><![CDATA[Bug Management and Bug Control Management are two separate aspects in software development. Bug Control Management seeks a higher maturity level in terms of organization, developers, project managers and all others involved. On the other hand, Bug Management starts in organizations with low maturity level. Organizations that attain the Bug Management level and keep it [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-control-management-vs-bug-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BLC or Bug Lifecycle</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/blc-or-bug-lifecycle/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/blc-or-bug-lifecycle/#comments</comments>
		<pubDate>Wed, 22 Oct 2008 10:11:16 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/blc-or-bug-lifecycle/</guid>
		<description><![CDATA[In simple terms BLC or Bug lifecycle can be defined as the different stages of bug. BLC or Bug lifecycle will consist of all these stages starting from the birth of a bug till its removal from the application. The various stages of bug lifecycle or BLC can be listed as below: 1. Bug induction [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/blc-or-bug-lifecycle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug Management &#8211; Major Concerns being felt across the Globe</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-management-major-concerns-being-felt-across-the-globe/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-management-major-concerns-being-felt-across-the-globe/#comments</comments>
		<pubDate>Wed, 08 Oct 2008 10:35:30 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing projects]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing environment]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/bug-management-major-concerns-being-felt-across-the-globe/</guid>
		<description><![CDATA[Senior Management including CIOs, QA Heads, CEOs, Development Heads, Project Heads, Customers, Vendors and/or sub-contractors related to software Organizations across the globe has repeatedly displayed their concern over the Bugs Management Process from time to time. These concerns could be grouped as below: 1. The results of the Testing process are regularly inconsistent: This means [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/bug-management-major-concerns-being-felt-across-the-globe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Causes of Occurrence of a Bug in Software Testing</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/causes-of-occurrence-of-a-bug-in-software-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/causes-of-occurrence-of-a-bug-in-software-testing/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 10:18:05 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/causes-of-occurrence-of-a-bug-in-software-testing/</guid>
		<description><![CDATA[In my previous blog we tried to understand what can be termed as a Bug. Here we will (in continuation to that) try to find out the reasons of causes of generation or occurrence of a Bug. A Bug shall occur in consequence to: An effort to write a perfect code in terms of performance [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/causes-of-occurrence-of-a-bug-in-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is a Bug?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bug/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bug/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 10:15:06 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[Bug Management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bug/</guid>
		<description><![CDATA[Any defect, shortcoming or error in software (built to perform a specific function or set of functions) is known as a Bug. A bug is usually an unexpected event encountered by a tester (or sometimes a programmer himself) while testing a unit, module or a complete product. This unexpected event could be due to a [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Role of tester while verifying the closure of bugs</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-tester-while-verifying-the-closure-of-bugs/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-tester-while-verifying-the-closure-of-bugs/#comments</comments>
		<pubDate>Mon, 29 Sep 2008 10:44:51 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[Software testing methodologies]]></category>
		<category><![CDATA[software testing procedure]]></category>
		<category><![CDATA[software testing process]]></category>
		<category><![CDATA[software testing projects]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-tester-while-verifying-the-closure-of-bugs/</guid>
		<description><![CDATA[When a product gets completed, it is released for testing to QC department along with the relevant documents. The QC department based on the scope of testing, availability of testers and the time at which the product is estimated to be released to customer, prepares its test plan. After studying the business and customer requirements, [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-tester-while-verifying-the-closure-of-bugs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What next after Bug Report (or Defect report) is released?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-next-after-bug-report-or-defect-report-is-released/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-next-after-bug-report-or-defect-report-is-released/#comments</comments>
		<pubDate>Fri, 26 Sep 2008 10:42:58 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing process]]></category>
		<category><![CDATA[software testing projects]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-next-after-bug-report-or-defect-report-is-released/</guid>
		<description><![CDATA[As soon as a bug of defect report is released by Quality department to Development Team, the first task of the development team is to call for a meeting inviting all those involved in the development of the product, the project head, the quality head and the testers who have performed testing. Prior to this [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-next-after-bug-report-or-defect-report-is-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is your defect (or bugs) report serving its purpose?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/is-your-defect-or-bugs-report-serving-its-purpose/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/is-your-defect-or-bugs-report-serving-its-purpose/#comments</comments>
		<pubDate>Wed, 24 Sep 2008 10:39:42 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[developer]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/is-your-defect-or-bugs-report-serving-its-purpose/</guid>
		<description><![CDATA[Let us understand what is the purpose of bugs report or defects report? Is it serving its purpose? How much? The purpose of a bugs report or defects report is to make the intended recipients of this report to understand each and every bug reported in its perspective view. A bugs report has to be [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/is-your-defect-or-bugs-report-serving-its-purpose/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is a bugs report in software testing?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bugs-report-in-software-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bugs-report-in-software-testing/#comments</comments>
		<pubDate>Fri, 19 Sep 2008 10:55:16 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bugs-report-in-software-testing/</guid>
		<description><![CDATA[A bugs report or defects report is a list of bugs found out by testers while testing a software product in testing phase under a testing environment. The test environment is created at development site similar to the actual environment in which the software is supposed to work or run in live situation at customer [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-bugs-report-in-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why build a test environment for software testing?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/why-build-a-test-environment-for-software-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/why-build-a-test-environment-for-software-testing/#comments</comments>
		<pubDate>Mon, 15 Sep 2008 10:56:26 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing environment]]></category>
		<category><![CDATA[software testing procedure]]></category>
		<category><![CDATA[software testing process]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing environment]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/why-build-a-test-environment-for-software-testing/</guid>
		<description><![CDATA[In continuation to my previous blog – &#8220;what is a test environment?&#8221;, let us understand here why a test environment is required for testing a software product? I see two major purposes for this, one purpose catering to customer end, and the second purpose catering to the vendor end quality testing team. The vendor or [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/why-build-a-test-environment-for-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is a Testing environment for software testing?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-testing-environment-for-software-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-testing-environment-for-software-testing/#comments</comments>
		<pubDate>Fri, 12 Sep 2008 10:35:14 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing environment]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing environment]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-testing-environment-for-software-testing/</guid>
		<description><![CDATA[A testing environment is a setup of software and hardware on which the testing team is going to perform the testing of the newly built software product. This setup consists of the physical setup which includes hardware, and logical setup that includes Server Operating system, client operating system, database server, front end running environment, browser [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-testing-environment-for-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change of Career, Testing to Development and vice versa</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/change-of-career-testing-to-development-and-vice-versa/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/change-of-career-testing-to-development-and-vice-versa/#comments</comments>
		<pubDate>Thu, 04 Sep 2008 10:12:40 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/change-of-career-testing-to-development-and-vice-versa/</guid>
		<description><![CDATA[During my 20 plus years of experience in IT, from time to time I received questions from career beginners (or seekers) having spent 1 to 4 years in one stream of career with a query related to their career growth. This query came from different individuals having spent some time successfully as a developer, or [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/change-of-career-testing-to-development-and-vice-versa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twelve essential Steps of Software Testing Life Cycle (STLC)</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/twelve-essential-steps-of-software-testing-life-cycle-stlc/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/twelve-essential-steps-of-software-testing-life-cycle-stlc/#comments</comments>
		<pubDate>Thu, 14 Aug 2008 10:35:39 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[Software testing methodologies]]></category>
		<category><![CDATA[software testing procedure]]></category>
		<category><![CDATA[software testing process]]></category>
		<category><![CDATA[software testing projects]]></category>
		<category><![CDATA[software testing strategy]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>
		<category><![CDATA[STLC]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/twelve-essential-steps-of-software-testing-life-cycle-stlc/</guid>
		<description><![CDATA[STLC (Software Testing Life Cycle) is an integral component of SDLC (Software Development Life Cycle). Gone are the times when any software was made on the basis of its requirements and the moment it used to get completed by the development team, it got released to the customer. But now, Testing has become a distinct [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/twelve-essential-steps-of-software-testing-life-cycle-stlc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Eight Checkpoints for Testers during Software Testing</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-checkpoints-for-testers-during-software-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-checkpoints-for-testers-during-software-testing/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 11:00:35 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[software qa]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<category><![CDATA[Software testers]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[software testing cycle]]></category>
		<category><![CDATA[Software testing methodologies]]></category>
		<category><![CDATA[software testing procedure]]></category>
		<category><![CDATA[software testing process]]></category>
		<category><![CDATA[software testing projects]]></category>
		<category><![CDATA[software testing strategy]]></category>
		<category><![CDATA[software testing tips]]></category>
		<category><![CDATA[softwaretesting]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/eight-checkpoints-for-testers-during-software-testing/</guid>
		<description><![CDATA[Testing is a process of facilitating development team/ project team in improving the quality of software before it is released to the customer for use. Some key essential steps are always there that need to be followed by the Testers during Software Testing to streamline the process. The most important checkpoints for testers during software [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-checkpoints-for-testers-during-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
