<?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/"
	>

<channel>
	<title>Project Management Guide &#187; Risk Tracking</title>
	<atom:link href="http://www.pmvista.com/tag/risk-tracking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pmvista.com</link>
	<description>- a comprehensive blog for all Software Project Managers and aspiring PMs</description>
	<lastBuildDate>Mon, 21 Nov 2011 16:31:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Risk Categories</title>
		<link>http://www.pmvista.com/risk-categories/</link>
		<comments>http://www.pmvista.com/risk-categories/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 01:22:55 +0000</pubDate>
		<dc:creator>P</dc:creator>
				<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Risk Tracking]]></category>

		<guid isPermaLink="false">http://www.pmvista.com/?p=48</guid>
		<description><![CDATA[Risk management is an essential activity of project management. It is important to classify risks into appropriate categories. Risks can be classified into following 13 categories: 1. Operational Risk: Risks of loss due to improper process implementation, failed system or some external events risks. Examples can be Failure to address priority conflicts, Insufficient resources or No proper subject [...]]]></description>
			<content:encoded><![CDATA[<p>Risk management is an essential activity of project management. It is important to classify risks into appropriate categories. Risks can be classified into following 13 categories:</p>
<p><strong>1. Operational Risk:</strong> Risks of loss due to improper process implementation, failed system or some external events risks. Examples can be Failure to address priority conflicts, Insufficient resources or No proper subject training etc.</p>
<p><span id="more-48"></span></p>
<p><strong>2. Schedule Risk:</strong> Project schedule get slip when project tasks and schedule release risks are not addressed properly. Schedule risks mainly affect on project and finally on company economy and may lead to project failure</p>
<p><strong>3. Budget Risk:</strong> Wrong budget estimation or Project scope expansion leads to Budget / Cost Risk.  This risk may lead to either a delay in the delivery of the project or sometimes even an incomplete closure of the project.</p>
<p><strong>4. Business Risk:</strong> Non-availability of contracts or purchase order at the start of the project or delay in receiving proper inputs from the customer or business analyst may lead to business risks.</p>
<p><strong>5. Technical Environment Risk:</strong> These are the risks related to the environment under which both the client and the customer work. For example, constantly changing development or production  or testing environment can lead to this risk.</p>
<p><strong>6. Information Security Risk:</strong> The risks related to the security of information like confidentiality or integrity of customer&#8217;s personal / business data. The Access rights / privileges failure will lead to leakage of confidential data.</p>
<p><strong>7. Programmatic Risks:</strong> The external risks beyond the operational limits. These are outside the control of the program. These external events can be Running out of fund or Changing customer product strategy and priority or Government rule changes etc.</p>
<p><strong>8. Infrastructure Risk:</strong> Improper planning of infrastructure / resources may lead to risks related to slow network connectivity or complete failure of connectivity at both the client and the customer sites. So, it is important to do proper planning of infrastructure for the efficient development of a project.</p>
<p><strong>9. Quality and Process Risk:</strong> This risk occures due to</p>
<ol>
<li>Incorrect application of process tailoring and deviation guidelines</li>
<li>New employees allocated to the project not trained in the quality processes and procedures adopted by the organization</li>
</ol>
<p><strong>10. Resource Risk:</strong> This risk depends on factors like Schedule, Staff, Budget and Facilities. Improper management of any of these factors leads to resource risk.</p>
<p><strong>11. Supplier Risk:</strong> This type of risk may occurs when some third party supplier is involved in the development of the project. This risk occurs due to the uncertain or inadequate capability of supplier.</p>
<p><strong>12. Technology Risk:</strong> It is related to the complete change in technology or introduction of a new technology.</p>
<p><strong>13. Technical and Architectural Risk:</strong> These types of risks generally generally leads to failure of functionality and performance. It addresses the hardware and software tools &amp; supporting equipments used in the project. The risk for this category may be due to &#8212; Capacity, Suitability, usability, Familiarity, Reliability, System Support and deliverability.</p>
<p>Apart from the above mentioned project risks, there is a common type of risk: Project Management Risk. This risk is related to following attributes:</p>
<ol>
<li>Project Planning</li>
<li>Project Organization</li>
<li>Management Experience &amp; Program Interfaces</li>
<li>Delay in getting approval for some of the work products from the customer or more requirement changes</li>
</ol>
<div style='clear:both'></div>]]></content:encoded>
			<wfw:commentRss>http://www.pmvista.com/risk-categories/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Risk Management Planning</title>
		<link>http://www.pmvista.com/risk-management-planning/</link>
		<comments>http://www.pmvista.com/risk-management-planning/#comments</comments>
		<pubDate>Wed, 15 Apr 2009 03:59:05 +0000</pubDate>
		<dc:creator>P</dc:creator>
				<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[Risk Tracking]]></category>

		<guid isPermaLink="false">http://www.pmvista.com/?p=45</guid>
		<description><![CDATA[Risk Management Planning is the process of developing an approach and executing risk management activities for a project. Inputs to Project Risk Management Planning: The inputs to Risk Management Planning include: Environmental factors Organizational process assets Project Scope Statement Project management plan Project Risk Management Planning Tools and Techniques: Meetings for planning and analysis are the [...]]]></description>
			<content:encoded><![CDATA[<p>Risk Management Planning is the process of developing an approach and executing risk management activities for a project. Inputs to Project Risk Management Planning: The inputs to Risk Management Planning include:</p>
<p><span id="more-45"></span></p>
<ol>
<li>Environmental factors</li>
<li>Organizational process assets</li>
<li>Project Scope Statement</li>
<li>Project management plan</li>
</ol>
<p>Project Risk Management Planning Tools and Techniques: Meetings for planning and analysis are the primary tools for creating the Risk Management Plan, which is the output of this process. One of the ways that a project team can begin to define the types and sources of risk events is to create a Risk Breakdown Structure (RBS).</p>
<p>The Risk Breakdown Structure is one way to identify risks in a structured manner. It assists the team in conducting a systematic review of risks and development of responses to risks.</p>
<p>The Risk Management Plan can include a Probability and/or Impact Matrix for organizing the information that will be used during the Risk Identification process to prioritize and quantify risks, and it may in some cases show opportunities for the project as well. Common information in the matrix includes numerical and/or descriptive definitions of impact, negative and positive, and the probability of occurrence. The combination of probability and impact determines whether a risk is rated high, moderate, or low. These descriptors are rank ordered in a relative scale. Numerical scales can also be used.</p>
<p>Outputs of Risk Management Planning: The Risk Management Plan should describe the entire risk management process, including auditing of the process. It should also define the content and format of the Risk Register, reporting, and risk tracking.</p>
<ol>
<li>Methodology Describes how risk management will be done on the project</li>
<li>Roles and responsibilities Defines the risk management team and their responsibilities for risk management activities</li>
<li>Budgeting Assigns budget for risk management activities to be included into the project cost baseline (project budget)</li>
<li>Timing Specifies when and how often the risk management activities appear in the project schedule</li>
<li>Risk categories Defines types and sources of risks to guide the Risk Identification process</li>
<li>Definitions Operational definitions for the project team to use to ensure consistency in the assessment of risks and opportunities</li>
<li>Probability and Impact Matrix Specific combinations of impact and probability, which lead to risk ratings such as high, medium, or low</li>
<li>Revised thresholds Revised or validated descriptions that trigger taking action; scope, quality, cost, and time thresholds may be different from each other</li>
<li>Reporting formats How to communicate risk activities and their results</li>
<li>Tracking How to document risk monitoring and management activities</li>
</ol>
<p>The Risk Management Plan will be used throughout the life cycle of the project. As the team moves through the subsequent Risk Management Processes, the plan will be revised, updated, and improved.</p>
<div style='clear:both'></div>]]></content:encoded>
			<wfw:commentRss>http://www.pmvista.com/risk-management-planning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

