Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, PMO, Risk Management
Risk Register. Who determines risk?
Network:0
I have to assist in a project manager capacity on a project.

I need to create a risk register. The company does not traditionally use formal processes such as this on projects.
The format etc is all fine.

My question is who should be responsible for identifying the risks and applying the rating?

Is it the stakeholder/representative of that part of the project?

The project team will be made up of different stakeholders in the business so obviously finance members will not be aware of IT risks etc.

I don't think it will be good enough to simply place the empty register on the drive and ask people to have a look and add anything they see relevant or it will stay empty.

Would you normally try to bring key stakeholders together to workshop and identify risks?
Sort By:
Page: 1 2 next>
Network:2537



I would definitely bring together appropriate stakeholders for the brainstorming session to discuss risks.
Additionally, if there were similar projects before, interview the members of that project team to discuss issues they may have had that you are at risk for having as well.
All member of the team are responsible for identifying risks and working with the project manager (or in this case you as the assistant to the PM) in applying the ratings.
Each risk will then be assigned a risk owner.
Network:100918



Everyone in the project is responsible and should take part in this. For identifying risks, it is best if you get all stakeholders together including the whole team and do this exercise together. You need as much stakeholders involved in risk identification as possible and this is an on going process throughout the project. As for risk rating, I would use Expert Judgement to rate the risks.
Network:733



The solution is to do a meeting or a workshop, in my opinion, gathering the stakeholders as needed. As Rami said, you should use Expert Judgement, but you should try to level the discussion and make sure that everybody understands what is a high impact on cost, for instance. You should have a scale of probability and impacts and try to do a comparison between the risks as you go along, making sure that the work is consistent.

Good luck!
Network:50



Its key that all that can contribute - does contribute in compiling the initial risk register and contributors added once the project evolves. Risk on a project can come from anywhere and at anytime so its key that participants from all fields / disciplines contribute to the risk register in each and every phase starting with the conceptual and completing with the operations phase. Each phase has its own unique risk as well as experts so its important to address those risk at the beginning of each phase while you can.
Network:1058



Paul -

a risk identification and qualitative analysis workshop is an excellent team building opportunity as it gives folks a chance to surface their fears, uncertainties and doubts.

Spread the net wide, don't scrimp on the snacks, and consider bringing in an independent facilitator so you can also contribute to the discussions...

Kiron
Network:504



Stakeholders are apart of the conversation but ultimately the project team (doing the work) is the expert. When there is disagreement within the team, the individuals closest to the work should be looked upon as the expert in assessing the risk. These risk should be reviewed by the PM with the Sponsors for their complete understanding. It's at this point the PM might be asked about making an adjustment.

We all are aware of individuals who are extremely risk adverse and will overstate the risk to their work just so they have some distance form responsibility. There are others who are overly confident and don't think through the world of possibilities before considering the actually being exposed to the risk. Before going to the sponsor the team should have talked through all of these considerations. this places the PM in a much better place to be able to explain the risk ratings being provided.
...
1 reply by Rami Kaibni
Jul 28, 2018 4:36 PM
Rami Kaibni
...
Hi Bruce,

Very interesting point of view. However, I believe all stakeholders should be part (Not apart) of the risk identification process, not only the team. The involvement of stakeholders at this stage of the project is very cruicial.
Network:34



Hi Paul, I cover this in a fair amount of detail in my book "Project Risk Management: A Practical Implementation Approach" published by PMI, Inc. in 2016.
Network:6885



These type of workshops are fantastic to break the ice and exchange ideas and views from different aspects.
Network:303



As per PMBOK, the risk will be identified by anyone by using gathering information, assumption and checklist. After that use expert judgement to rate risk and prioritize which these are most risk to make numerical analysis!!!
Network:100918



Jul 27, 2018 3:10 PM
Replying to Bruce A. Hayes
...
Stakeholders are apart of the conversation but ultimately the project team (doing the work) is the expert. When there is disagreement within the team, the individuals closest to the work should be looked upon as the expert in assessing the risk. These risk should be reviewed by the PM with the Sponsors for their complete understanding. It's at this point the PM might be asked about making an adjustment.

We all are aware of individuals who are extremely risk adverse and will overstate the risk to their work just so they have some distance form responsibility. There are others who are overly confident and don't think through the world of possibilities before considering the actually being exposed to the risk. Before going to the sponsor the team should have talked through all of these considerations. this places the PM in a much better place to be able to explain the risk ratings being provided.
Hi Bruce,

Very interesting point of view. However, I believe all stakeholders should be part (Not apart) of the risk identification process, not only the team. The involvement of stakeholders at this stage of the project is very cruicial.
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"All you need in this life is ignorance and confidence, and then success is sure."

- Mark Twain

ADVERTISEMENT

Sponsors