Comments on: Project Risk Management: Identify and Prevent Risk Issues http://www.pmhut.com/project-risk-management-identify-and-prevent-risk-issues Thu, 24 May 2012 09:01:34 +0000 http://wordpress.org/?v=abc hourly 1 By: Srinidhi http://www.pmhut.com/project-risk-management-identify-and-prevent-risk-issues/comment-page-1#comment-864 Srinidhi Tue, 07 Oct 2008 09:08:51 +0000 http://www.pmhut.com/project-risk-management-identify-and-prevent-risk-issues#comment-864 Hi Ram, Nice write-up!! As organizations increasingly look to IT vendors to manage project risks effectively, it is becoming very important for the vendor to thoroughly understand the risk management process that is applicable to the client's business. Some of the very pertinent risks that I have come across in Software projects include: 1. Unclear requirements till well into the development phase: It is a risk to the project if this is not accepted as a risk :). This is inevitable. 2. Unclear SLA numbers: This mostly leads to ambiguity in large deals. 3. Non-uniform understanding of project risks among project members also proves to be a risk. Some of the typical categories for risks include technical, Project Management, External and customer centric. Irrespective of risk management techniques ranging from Checklists to Checkpoints, risks are an integral part of any project and are here to stay. Just my two cents!! Regards, Srinidhi Hi Ram,

Nice write-up!! As organizations increasingly look to IT vendors to manage project risks effectively, it is becoming very important for the vendor to thoroughly understand the risk management process that is applicable to the client’s business. Some of the very pertinent risks that I have come across in Software projects include:

1. Unclear requirements till well into the development phase: It is a risk to the project if this is not accepted as a risk :). This is inevitable.
2. Unclear SLA numbers: This mostly leads to ambiguity in large deals.
3. Non-uniform understanding of project risks among project members also proves to be a risk.

Some of the typical categories for risks include technical, Project Management, External and customer centric. Irrespective of risk management techniques ranging from Checklists to Checkpoints, risks are an integral part of any project and are here to stay. Just my two cents!!

Regards,
Srinidhi

]]> By: Vinny http://www.pmhut.com/project-risk-management-identify-and-prevent-risk-issues/comment-page-1#comment-863 Vinny Mon, 22 Sep 2008 14:18:16 +0000 http://www.pmhut.com/project-risk-management-identify-and-prevent-risk-issues#comment-863 Hi Ram, The drafted process looks great in proactively understanding the Risks which are gonna exist all through the Project Cycle. Keep it going... My thoughts around it, When we are talking about Risk Management, it would also help having an understanding on where to place the kind of risks which we are certain to face in a project cycle., Eliminate - Should we completely avoid it? Reduction - Can we reduce the impact of risk? Transfer - Can it be transfered to someother party? Retention - Can it be accepted? This even implies even on my domain of RIM,where we go for a transition to Onsite, we would wanna understand what can be taken over from the client and can be done back from India. For example: I go for a UNIX transition, where in I am supposed to transition work from Onsite to Offshore. I would wanna understand few things like., - Can all servers be supported back from here in India. If not can we eliminate the servers from the support, rather than carrying the Risk of affecting your own SLA. - If client insists on taking over the servers, will I able to reduce the impact by taking a waiver for those servers from the SLA. - If client insists on equal treatment of the servers, can I transfer those particular servers to a local vendor to support - If none of the above work, understanding the facts on the level of work/trend of incidents, we can decide on whether to retain or eliminate the servers. Cheers, V Hi Ram,

The drafted process looks great in proactively understanding the Risks which are gonna exist all through the Project Cycle. Keep it going…

My thoughts around it, When we are talking about Risk Management, it would also help having an understanding on where to place the kind of risks which we are certain to face in a project cycle.,

Eliminate - Should we completely avoid it?
Reduction - Can we reduce the impact of risk?
Transfer - Can it be transfered to someother party?
Retention - Can it be accepted?

This even implies even on my domain of RIM,where we go for a transition to Onsite, we would wanna understand what can be taken over from the client and can be done back from India.

For example:

I go for a UNIX transition, where in I am supposed to transition work from Onsite to Offshore. I would wanna understand few things like.,

- Can all servers be supported back from here in India. If not can we eliminate the servers from the support, rather than carrying the Risk of affecting your own SLA.
- If client insists on taking over the servers, will I able to reduce the impact by taking a waiver for those servers from the SLA.
- If client insists on equal treatment of the servers, can I transfer those particular servers to a local vendor to support
- If none of the above work, understanding the facts on the level of work/trend of incidents, we can decide on whether to retain or eliminate the servers.

Cheers,
V

]]>