 




<?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; customer requirement</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/customer-requirement/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>5 Top Reasons Behind All Problems In Project Management Part I</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/5-top-reasons-behind-all-problems-in-project-management-part-i/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/5-top-reasons-behind-all-problems-in-project-management-part-i/#comments</comments>
		<pubDate>Fri, 01 Jun 2012 16:55:10 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[team management]]></category>
		<category><![CDATA[team sizing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/5-top-reasons-behind-all-problems-in-project-management-part-i/</guid>
		<description><![CDATA[Though it is difficult the assume in advance what kind of problems will percolate during a particular project but more or less all kind of problems faced during a project execution/ deployment/ management can be segregated in five top most reasons or categories. These generic segments/ reasons/ categories will be able to address all issues [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/5-top-reasons-behind-all-problems-in-project-management-part-i/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sixteen Blogs On Identificaiton Of Customer Requirements</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/sixteen-blogs-on-identificaiton-of-customer-requirements/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/sixteen-blogs-on-identificaiton-of-customer-requirements/#comments</comments>
		<pubDate>Tue, 26 Jul 2011 18:07:29 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/sixteen-blogs-on-identificaiton-of-customer-requirements/</guid>
		<description><![CDATA[Customer Requirements need to be wisely analyzed before committing its fulfilment to customer. Many a times a commitment which has not been properly analyzed and assessed impacts to a large extent on completion of project. It may also happen that a requirement stated by customer at a later stage may appear to be quite genuine [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/sixteen-blogs-on-identificaiton-of-customer-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Six Sins At Product Development Stage That Can Lead Project To Disaster</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/six-sins-at-product-development-stage-that-can-lead-project-to-disaster/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/six-sins-at-product-development-stage-that-can-lead-project-to-disaster/#comments</comments>
		<pubDate>Sun, 24 Jul 2011 14:18:10 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[development plan]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Project Plan]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[team management]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/six-sins-at-product-development-stage-that-can-lead-project-to-disaster/</guid>
		<description><![CDATA[Requirement Coverage: Requirement gathering and its documentation both need to be crisply and completely covered. Any lack in either of the activity is like a volcano in the making. In fact 88 percent of project failures worldwide are due to wrong or incomplete requirement study. Team Selection: Development team need to be wisely selected keeping [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/six-sins-at-product-development-stage-that-can-lead-project-to-disaster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Requirement Based Face Saving Statements Against Customer To Hide Shortcomings</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-requirement-based-face-saving-statements-against-customer-to-hide-shortcomings/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-requirement-based-face-saving-statements-against-customer-to-hide-shortcomings/#comments</comments>
		<pubDate>Tue, 17 May 2011 09:59:06 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-requirement-based-face-saving-statements-against-customer-to-hide-shortcomings/</guid>
		<description><![CDATA[A fight between customer and vendor related to requirement keeps going on till the project finish stages starting right from the requirement study phase. Whatsoever methodology or standards you adopt to capture customer requirements, there will always remain a gap between what customer said, what you assumed he said, what you understood and what you [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-requirement-based-face-saving-statements-against-customer-to-hide-shortcomings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Segregating Customer Desire Need And Greed Carves Project Success</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/segregating-customer-desire-need-and-greed-carves-project-success/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/segregating-customer-desire-need-and-greed-carves-project-success/#comments</comments>
		<pubDate>Fri, 29 Apr 2011 09:54:22 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/segregating-customer-desire-need-and-greed-carves-project-success/</guid>
		<description><![CDATA[Customer will always be hesitant in declaring software project as complete by means of talking about more and more to be done in the software. This ‘more’ could be anything like functionality, requirements, confusion, frustration, appearance, performance and what not. Some of these ‘more’ can be addressed to easily if possible to take in objective [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/segregating-customer-desire-need-and-greed-carves-project-success/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Golden Guidelines While Heading For A New Customer Win</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-golden-guidelines-while-heading-for-a-new-customer-win/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-golden-guidelines-while-heading-for-a-new-customer-win/#comments</comments>
		<pubDate>Tue, 08 Feb 2011 12:06:50 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business model]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Software application]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software quality]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-golden-guidelines-while-heading-for-a-new-customer-win/</guid>
		<description><![CDATA[In today’s scenario there is no life on this earth without its dependency on any software in one way or the other in professional or personal front. This is what technology and its advancement does, it makes us more dependent on it by providing us more accuracy, comfort and satisfaction. We do something only because [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-golden-guidelines-while-heading-for-a-new-customer-win/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification of Customer Requirements Part X</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-x/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-x/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 12:17:55 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-x/</guid>
		<description><![CDATA[It is important to analyze any change request raised by any of the stakeholders of the product in a systematic manner. The best way would be to first differentiate business process or functional change with cosmetic or design change. Though both categories can fall into severely possible, easily possible and not possible sections depending on [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification of Customer Requirements Part IX</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ix/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ix/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 11:58:48 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[change management]]></category>
		<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ix/</guid>
		<description><![CDATA[In situations when the requirement generator cannot be ignored directly due to his potential say in the management, the role of Product Owner become prime in tackling the situation. Product owner must analyze the situation, prepare a case study and put forth his point that if such a change is incorporated, it might go wrong [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part VIII</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-viii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-viii/#comments</comments>
		<pubDate>Mon, 15 Nov 2010 08:53:01 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-viii/</guid>
		<description><![CDATA[Customer requirements management with a metrics is an important factor. Requirements raised a various levels within an organization has nothing to do directly with the seriousness of requirement. Some key users or management executives though may not go into the depth of the product they are supposed to use but to mark their impression as [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-viii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part VII</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vii/#comments</comments>
		<pubDate>Mon, 15 Nov 2010 08:48:29 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vii/</guid>
		<description><![CDATA[A proper understanding of any change required and its in-depth analysis are prime important factors. It doesn’t mean that the importance of other steps performed afterwards – like the development of change, testing of all kinds, etc. The later steps are equally important but since it s a sequential process, each of the previous step’s [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part VI</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vi/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vi/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 11:57:26 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vi/</guid>
		<description><![CDATA[A new requirement development done in already consistently stable running software may do certain good or harmful things in turn. It may turmoil; destabilize the software thereby resulting into an inconsistent and unstable product. Which in turn may result into unsatisfied users who were happy with the product before the change was performed on the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-vi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part IV</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iv/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iv/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 09:19:47 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iv/</guid>
		<description><![CDATA[The limitations of catering to new requirements may arise due to certain other factors too which might delimited at a later stage or may not be possible at all. For example an application built on client server architecture if required to be converted to a web based application later may call for a major overhaul [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part III</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iii/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 09:16:35 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iii/</guid>
		<description><![CDATA[Sometimes it might happen that the requirement by the customer exists in the product but in some other way. For instance the software product in use might be handling the same requirement already but in a different manner. In that case a person with good business knowledge knowing equally well about the product’s capabilities need [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-iii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part II</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ii/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ii/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 11:17:53 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ii/</guid>
		<description><![CDATA[Interestingly if the changes are accepted without proper analysis it results in delays in delivery, improperly woven product, un-tested product, shaken budgets. This all happens due to a later stage discovery of the change appearing not as small as anticipated earlier. So many ambiguities arise if there is a gap between customers stated requirement and [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identification Of Customer Requirements Part I</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-i/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-i/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 11:09:06 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-i/</guid>
		<description><![CDATA[Customer requirements at first instance may all appear essential. Especially the requirements listed by the top management tend to automatically fall in must-do category. But that is not so. Any requirement if without proper analysis is placed in must-do or essential requirement may create a big problem in terms of scope and budget of the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/identification-of-customer-requirements-part-i/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Wake Up Call For All Project Managers</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/a-wake-up-call-for-all-project-managers/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/a-wake-up-call-for-all-project-managers/#comments</comments>
		<pubDate>Tue, 07 Sep 2010 06:37:43 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/a-wake-up-call-for-all-project-managers/</guid>
		<description><![CDATA[Imagine yourself as a commercial builder. You are contracted for building a multi-storeyed building by the owner of that plot. The owner is too busy to concentrate on the job himself. He finds you as an expert in this line. The conceptualized model has been described to you by the owner. You are being paid [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/a-wake-up-call-for-all-project-managers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two Approaches Of Capturing Customer Requirements</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/two-approaches-of-capturing-customer-requirements/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/two-approaches-of-capturing-customer-requirements/#comments</comments>
		<pubDate>Fri, 23 Jul 2010 12:25:06 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business requirement]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/two-approaches-of-capturing-customer-requirements/</guid>
		<description><![CDATA[Let us consider a simple scenario of writing code for a new application for a customer. The process starts with a clear understanding of customer business, key user’s expectations and customer management’s expectation regarding business benefits driven out of this application. The most important journey begins with capturing all these details as minutely as possible. [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/two-approaches-of-capturing-customer-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two Questions for Quality Manager and Project Manager</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/two-questions-for-quality-manager-and-project-manager/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/two-questions-for-quality-manager-and-project-manager/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 07:09:38 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[Project Head]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project quality]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[requirement analysis]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/two-questions-for-quality-manager-and-project-manager/</guid>
		<description><![CDATA[1. At times development, requirement freezing gets done side by side and that too at customer location. In that case the product undergoes a lot of changes based on customer feedback on daily basis and finally product gets ready as per development team and customer. After that it comes to QA for testing. Is that [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/two-questions-for-quality-manager-and-project-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Development-QC-Development-QC-Dev-Product Launch</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/development-qc-development-qc-dev-product-launch/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/development-qc-development-qc-dev-product-launch/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 10:00:18 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[blackbox testing]]></category>
		<category><![CDATA[boundary value testing]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[business specification]]></category>
		<category><![CDATA[BVA]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[customer specification]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[implementation team]]></category>
		<category><![CDATA[performance testing]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[QC feedback]]></category>
		<category><![CDATA[Regression Testing]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/development-qc-development-qc-dev%e2%80%a6%e2%80%a6-product-launch/</guid>
		<description><![CDATA[The bugs or defects list is submitted back to the development team for minor to exhaustive overhaul of the product depending on the number and severity of bugs. After fixing of bugs and verifying at their end the development team invites QC team again for verification so that the product can be launched for the customer. This testing-fixing-verification may happen in one go or may require re-runs depending on the QC feedback.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/development-qc-development-qc-dev-product-launch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Project Manager – A Solid Bridge between Customer and Product Manager</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/project-manager-%e2%80%93-a-solid-bridge-between-customer-and-product-manager/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/project-manager-%e2%80%93-a-solid-bridge-between-customer-and-product-manager/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 10:00:50 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[change management]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[product manager]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/project-manager-%e2%80%93-a-solid-bridge-between-customer-and-product-manager/</guid>
		<description><![CDATA[Let us talk about existing software required to be implemented at a new geographical location. Definitely because of a different location there will be certain new requirements plus some changes here and there in the existing built to meet customer specifications.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/project-manager-%e2%80%93-a-solid-bridge-between-customer-and-product-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five ‘must-have’ skills to be a Business Analyst</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-%e2%80%98must-have%e2%80%99-skills-to-be-a-business-analyst-as-stated-in-my-previous-post-a-business-analyst-is-a-quite-powerful-role-that-establishes-the-base-of-a-project-it-is-the-first-vi/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-%e2%80%98must-have%e2%80%99-skills-to-be-a-business-analyst-as-stated-in-my-previous-post-a-business-analyst-is-a-quite-powerful-role-that-establishes-the-base-of-a-project-it-is-the-first-vi/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 10:00:03 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business analysis]]></category>
		<category><![CDATA[business analyst]]></category>
		<category><![CDATA[business knowledge]]></category>
		<category><![CDATA[business process]]></category>
		<category><![CDATA[business rule]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software requirement]]></category>
		<category><![CDATA[technical knowledge]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-%e2%80%98must-have%e2%80%99-skills-to-be-a-business-analyst-as-stated-in-my-previous-post-a-business-analyst-is-a-quite-powerful-role-that-establishes-the-base-of-a-project-it-is-the-first-v</guid>
		<description><![CDATA[As stated in my previous post, a Business Analyst is a quite powerful role that establishes the base of a project. It is the first visible pillar for a project which involves communication, leadership, writing, technical and functional skills together. A business analyst has to have a great depth of knowledge of the business on one hand, a sharp understanding power, strong writing skills, great communicator, and a good influencer. Let us see what are the ‘must-have’ skills without which a business analyst can not survive? And why are those skills so important to be a business analyst?]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-%e2%80%98must-have%e2%80%99-skills-to-be-a-business-analyst-as-stated-in-my-previous-post-a-business-analyst-is-a-quite-powerful-role-that-establishes-the-base-of-a-project-it-is-the-first-vi/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Various roles of a Business Analyst</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/various-roles-of-a-business-analyst/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/various-roles-of-a-business-analyst/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 10:00:03 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business analysis]]></category>
		<category><![CDATA[business process]]></category>
		<category><![CDATA[business rule]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/various-roles-of-a-business-analyst/</guid>
		<description><![CDATA[Business Analyst is a quite powerful role forming the base of a project. It is the first visible pillar for a project which involves communication, leadership, writing, technical and functional skills together. A business analyst has to have a great depth of knowledge of the business on one hand, a sharp understanding power, strong writing skills, great communicator, and a good influencer. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/various-roles-of-a-business-analyst/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What customer type you are?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-customer-type-you-are/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-customer-type-you-are/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 10:00:29 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business requirement]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-customer-type-you-are/</guid>
		<description><![CDATA[One customer type focuses on current requirement, rightly built, with more flexibility towards the business requirements built-in in the database rather than in the code. They believe that if the software meets their current requirements well, the future requirements will be built in at the need of the hour. The reason for this is that nobody at the moment is sure about the future requirements and when the change will be required...]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-customer-type-you-are/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What sort of driver are you?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-sort-of-driver-are-you/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-sort-of-driver-are-you/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 13:17:24 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[product quality]]></category>
		<category><![CDATA[Project Development]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project stage]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software delivery]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software quality]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-sort-of-driver-are-you/</guid>
		<description><![CDATA[I have seen different type of drivers on road: some drive very fast violating all rules and regulations to reach the destination. Can this attitude work in software development and delivery? I don’t think so, if the project manager is more worried about reaching the implementation stage without bothering about the customer requirements, probably he is calling for a big bunch of troubles...]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-sort-of-driver-are-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five ways to workout ‘testing effort”</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-ways-to-workout-%e2%80%98testing-effort%e2%80%9d/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-ways-to-workout-%e2%80%98testing-effort%e2%80%9d/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 12:00:26 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business rule]]></category>
		<category><![CDATA[business specification]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[customer specification]]></category>
		<category><![CDATA[development phase]]></category>
		<category><![CDATA[development plan]]></category>
		<category><![CDATA[functional testing]]></category>
		<category><![CDATA[load testing]]></category>
		<category><![CDATA[performance testing]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[QC head]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[team size]]></category>
		<category><![CDATA[test case]]></category>
		<category><![CDATA[test effort]]></category>
		<category><![CDATA[Test Plan]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing effort]]></category>
		<category><![CDATA[testing effort estimation]]></category>
		<category><![CDATA[testing phase]]></category>
		<category><![CDATA[testing plan]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-ways-to-workout-%e2%80%98testing-effort%e2%80%9d/</guid>
		<description><![CDATA[Customer specifications or requirements captured at the time of initial study period would be a quick reference guide for estimating testing effort. One word of caution is that incomplete or non-documented requirements may lead to wrong estimations for both – development and testing.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-ways-to-workout-%e2%80%98testing-effort%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ten facts (or myths) about developers and testers</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-facts-or-myths-about-developers-and-testers/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-facts-or-myths-about-developers-and-testers/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 13:00:21 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[business needs]]></category>
		<category><![CDATA[business requirement]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software code]]></category>
		<category><![CDATA[Software tester]]></category>
		<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/ten-facts-or-myths-about-developers-and-testers/</guid>
		<description><![CDATA[We all know developers and testers both have a tough job all the time. Developers have a key role in developing the software as per customer requirements embedding customer’s business needs into it. Similarly testers have to put all their efforts in ensuring that the software is matching customer specifications flawlessly and is bugs free. In a nutshell both developers and testers have a common goal of ensuring a superior product delivery at customer end. If that is so why there is a never-ending tussle between testers and developers.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-facts-or-myths-about-developers-and-testers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Responsibility of a tester &#8211; a different perspective</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/responsibility-of-a-tester-a-different-perspective/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/responsibility-of-a-tester-a-different-perspective/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 10:00:28 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[bugs report]]></category>
		<category><![CDATA[code writing]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[product quality]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software quality]]></category>
		<category><![CDATA[test case]]></category>
		<category><![CDATA[test report]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing report]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/responsibility-of-a-tester-a-different-perspective/</guid>
		<description><![CDATA[The overall impact of testing should be clearly visible on the product built. The bugs reported should bring a sense of belonging with the developers and customer users. Clarity of bugs in testing report should not only help developer to fix defects properly but guide him not to repeat the same type of issues in future releases. This may happen slowly but gradually should help in increasing developer's performance and quality of code writing. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/responsibility-of-a-tester-a-different-perspective/feed/</wfw:commentRss>
		<slash:comments>3</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>
	</channel>
</rss>
