Project risk management- DB-2

Primary Post:  By Wednesday, What risk identification techniques do you find most applicable in your project work?   How do you/ could you use these techniques to identify and communicate "politically charged" risks?  For your term project, write one risk statement in the Cause-Condition-Conclusion format.  How did you identify this risk?   

Secondary Post:   respond to at least 1 primary posts.  What is effective about the techniques noted?  What additional actions can you suggest to identify and communicate risks that are sensitive within the organization?

Hi Nicole! Someone already posted, so you can write a secondary post for below.

The risk identification techniques that I have found to be most applicable are the survey and brainstorming and interviewing. In my experience, I have found that extracting information about from the team as a whole works well when you start engaging the team and getting them to talk and generate idea’s and processes so that they start thinking. In addition, I have found working individually with people have brought out ideas and potential risks that may are relevant to the project objectives. One way for project managers to identify and communicate politically charged risks is to know the organization that they work in and be as transparent as possible with all stakeholders so they know you are not taking sides on the playing field. Be aware of how politics are unfolding around you and determine the political players in your organization (Franklin, 2012).

If I were to apply the cause-condition-conclusion format to my Project Portfolio Management Implementation, I would say that because this is a new system we are implementing into our production environment (root cause), it may affect other services and impact them negatively (risk). That said, we may not be able to implement the Project Portfolio Management tool due to the negative impact it may have with other systems or feeds so we will need to have a back-out plan(impact). A risk such as this can be identified early on by the project team, or throughout the monitoring or controlling phase of the project. Project risks are generally brought up during collaborative team meetings and should be noted down as they surface in order to mitigate the project risk and enhance the chances of the overall project success rate.