 




<?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; Risk analysis</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/risk-analysis/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>Seven Steps for Risk Management People Management and Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-steps-for-risk-management-people-management-and-project-management/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-steps-for-risk-management-people-management-and-project-management/#comments</comments>
		<pubDate>Sat, 06 Mar 2010 09:00:05 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[high risk]]></category>
		<category><![CDATA[people management]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Risk analysis]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[risk mitigation]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/seven-steps-for-risk-management-people-management-and-project-management/</guid>
		<description><![CDATA[Any project, small or big, is bound to have risks. Risks perceived can be managed well as an advanced risk management plan can be prepared with the ways to mitigate the risk. Risks that are not perceived during the risk management plan are bound to create chaos and unplanned handholding at the time of its [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-steps-for-risk-management-people-management-and-project-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10 stages of Risk in software application development and testing</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/10-stages-of-risk-in-software-application-development-and-testing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/10-stages-of-risk-in-software-application-development-and-testing/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 10:18:11 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[application testing]]></category>
		<category><![CDATA[impact analysis]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[Risk analysis]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk classification]]></category>
		<category><![CDATA[risk closure]]></category>
		<category><![CDATA[risk identification]]></category>
		<category><![CDATA[risk perception]]></category>
		<category><![CDATA[Risk Plan]]></category>
		<category><![CDATA[risk plan analysis]]></category>
		<category><![CDATA[risk plan execution]]></category>
		<category><![CDATA[Software application]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/10-stages-of-risk-in-software-application-development-and-testing/</guid>
		<description><![CDATA[A risk is a bigger than its size if it is not identified well in advance. An identified risk is as risky as unidentified if its assessment is not done. Risk assessment is useless if there is no impact analysis. Impact analysis has no worth if its countermeasure is not identified. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/10-stages-of-risk-in-software-application-development-and-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Different Software Applications have different set of Risks involved</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/different-software-applications-have-different-set-of-risks-involved/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/different-software-applications-have-different-set-of-risks-involved/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 10:06:29 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[application availability]]></category>
		<category><![CDATA[bank application]]></category>
		<category><![CDATA[high risk]]></category>
		<category><![CDATA[low risk]]></category>
		<category><![CDATA[medium risk]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[Risk analysis]]></category>
		<category><![CDATA[risk impact]]></category>
		<category><![CDATA[Software application]]></category>
		<category><![CDATA[software availability]]></category>
		<category><![CDATA[software requirement]]></category>
		<category><![CDATA[software usage]]></category>
		<category><![CDATA[software user volume]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/different-software-applications-have-different-set-of-risks-involved/</guid>
		<description><![CDATA[Any activity is never without risk involved in it. Risk could be classified in different categories like - low, medium or high depending on its impact, software’s requirements and purpose, software usage, and software user volume. Accordingly the risks are identified or rather perceived. Their impact is measured or assessed, and based in the category in which it falls into – its countermeasures are designed or defined. The right identification of risk is as important as its classification or category.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/different-software-applications-have-different-set-of-risks-involved/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>20 points for organizational self evaluation to check where it stands in Software Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/20-points-for-organizational-self-evaluation-to-check-where-it-stands-in-software-project-management/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/20-points-for-organizational-self-evaluation-to-check-where-it-stands-in-software-project-management/#comments</comments>
		<pubDate>Mon, 09 Mar 2009 10:28:51 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[1.	organizational self evaluation]]></category>
		<category><![CDATA[Code repository]]></category>
		<category><![CDATA[continuous improvement]]></category>
		<category><![CDATA[customer expectations]]></category>
		<category><![CDATA[customer feedback]]></category>
		<category><![CDATA[customer request]]></category>
		<category><![CDATA[empowerment]]></category>
		<category><![CDATA[innovation process]]></category>
		<category><![CDATA[off-site project]]></category>
		<category><![CDATA[on-site project]]></category>
		<category><![CDATA[organizational goals]]></category>
		<category><![CDATA[post implementation]]></category>
		<category><![CDATA[process integration]]></category>
		<category><![CDATA[product release]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project management evaluation checklist]]></category>
		<category><![CDATA[Project Management Methodology]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project metrics]]></category>
		<category><![CDATA[project overrun]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[Risk analysis]]></category>
		<category><![CDATA[Risk Plan]]></category>
		<category><![CDATA[roles and responsibilities]]></category>
		<category><![CDATA[software bug]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[software project management]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[test case repository]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/20-points-for-organizational-self-evaluation-to-check-where-it-stands-in-software-project-management/</guid>
		<description><![CDATA[1.	Do you see all your processes integrated going hand in hand?
2.	Do you get your payments from customer in time?
3.	Do you have a process to capture customer feedback and request?
4.	Do you have an innovation process in place?
......]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/20-points-for-organizational-self-evaluation-to-check-where-it-stands-in-software-project-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top 15 Pain Areas in a Software Project Lifecycle</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/top-15-pain-areas-in-a-software-project-lifecycle/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/top-15-pain-areas-in-a-software-project-lifecycle/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 10:43:01 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[approach and deliverables]]></category>
		<category><![CDATA[customer requirements]]></category>
		<category><![CDATA[Customer requirements understanding]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[Learning from Past]]></category>
		<category><![CDATA[Measurement of Overrun]]></category>
		<category><![CDATA[Methodology and Standards]]></category>
		<category><![CDATA[methods]]></category>
		<category><![CDATA[pain areas of a software project]]></category>
		<category><![CDATA[Post implementation support]]></category>
		<category><![CDATA[Project Repository]]></category>
		<category><![CDATA[Project Status review]]></category>
		<category><![CDATA[Quality – man]]></category>
		<category><![CDATA[Risk analysis]]></category>
		<category><![CDATA[Role clarity]]></category>
		<category><![CDATA[software metrics]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[Software Project Lifecycle]]></category>
		<category><![CDATA[software project management]]></category>
		<category><![CDATA[Team building]]></category>
		<category><![CDATA[Version Control]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=123</guid>
		<description><![CDATA[Following are the top 15 pain areas of a software project. All points listed below appear somewhere or the other in a software project lifecycle. The ratio of pain from a particular below listed item may vary from project to project within an organization, and also from organization to organization. So although the hierarchy may [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/top-15-pain-areas-in-a-software-project-lifecycle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
