Risk management meeting should be ran by sharing the complied list of risks from previous project, if any in order to identify some common risks but also as a catalyst to get the participants thinking about risks. Identify duplicate risks and work as a team to determine other risk associated with the product. Assign impact of each risk and determine proper response.
I believe the best results from a risk analysis meeting come from minimizing bias. The beginning of the meeting is about finding hazards by going through the chronological life cycle of the project. Starting with the machining/manufacturing process and following through till contact with end user. Once all the possible hazards are known, then break the meeting up into two groups. One assigns the hazards severity numbers and the other assigns frequency numbers. After both groups are finished, come back into one group to go over the numbers. Breaking into two smaller groups ensures that there is little bias in which hazards are the most risky. This makes it more believable when the group decides that some hazards are not risky enough to warrant a change.
In order to run a risk management meeting I think the risk manager must first take time to assess all possible rise, give them a severity ranking and point out areas where risk are more likely to occur. Then once you get to your weekly meeting, I would bring up these risk and my assessment of them, and talk to my members about my assessments, and see if assessed a risk as too severe or too likely. We would also brainstorm other possible risk from areas that can cause more negative outcomes in the future. After assessing all risk we will group them and discuss the most severe risks first. By assessing the most severe risks first we can decide if we are able to mitigate risk and if not then we must decide to avoid the risk. By choosing to avoid the risk, we may have to make changes to our design, which can affect or get rid of other risks to our model. After looking at what the adjustments will bring, we can assess the, new risk and lower level risk, and decide how to mitigate them, or if we are able to accept them. At the end we will make note of possible future risk, decide how to monitor them going forward, and look at what changes we may have to make later on.
The key to a successful risk assessment meeting is to be sure that the Risk Assessment Meeting includes Key Project Team Members and Key Stakeholders. By conducting a risk assessment meeting the Project Manager will be able to identify the greatest number of risks for a project. The project manager should review risk that happens in last project so that common risk can be evaluated and mitigate at the very beginning. Risks require clear descriptions and robust assessments as they indicate the areas requiring particular focused attention and action. Risk responses define what needs to be done in order to minimise avoidable problems and maximise achievable benefits.Take a full account of group behaviour throughout the workshop, maintaining a high degree of awareness of what is going on and gather an appreciation of the underlying reasons why it is happening.
To run a risk management meeting, always follow the cycle of assess-evaluate-manage-measure. First thing you should do is to have quality member gather all members in the project team, because it is important to make everyone get the information of potential risks. Second thing is brainstorming the risks that could happen in the product, product design and manufacturing process, this is called assessment. Thirdly, quality member need to evaluate the potential risks in its generation mechanism, severity and probability so that we could put our attentions accordingly and make most of it to expedite the project progression without ignoring risks. The fourth point comes to how to manage those risks after knowing their existence, four general strategies commonly used are avoidance, mitigation, acceptance, and transference. Then the last thing in the cycle is measurement, which is to confirm whether the management is effective in lowering the risks and how much does it reduce. This cycle will keep rolling throughout the project in order to deal with any new risks that could emerge in the progress.
Personally, for any business/professional meeting I think it would be most effective to follow Robert's Rules of Order. (At the end of the post I will link a basic overview of what that is)
The first thing you will need to do is make an agenda to send out prior to the meeting. In the agenda, everything that needs to be addressed should be displayed so everyone is on the same page. Make sure someone takes meeting minutes and distributes them to the necessary parties after the meeting is adjourned (in a reasonable timeframe). Whoever is leading the meeting needs to make sure the conversation doesn't stray too much from the agenda so that time isn't wasted. As long as everyone respects everyone's turn to speak, using Robert's Rules of Order is the best way to run a meeting (that I know of).
Every company needs a risk meeting, it is important because all the product that is being produced is for someone or something. We must keep the consumer safe, which is the main focus of the meeting. In the risk meeting, the head of each department should make a list of any possible way how the product can go wrong by harming people. A company would not want to sell a bad product without advising the risk because numerous outcomes can affect the company like bad reputation, credibility, lawsuits, or even money lost. The group must review all risk and must have the public aware the possible risk in using their product.
Once the meeting is set up and the purpose and function of the device is fully understood, it would be a good idea to have a group discussion about the potential risks associated with that product. Once the basic ones are identified, have everyone in the group fill out a risk analysis questionnaire that further uncovers any and all risks that could happen. Once the "quality person" compiles this information together, that is when the risk analysis should be done and each risk is categorized into a risk matrix.
Risk amangement is nessecary for every company. The risk assessment meeting should be a formal meeting conducted during the project’s planning process. By conducting a risk assessment meeting the Project Manager will be able to identify the greatest number of risks for a project. The project manager should review risk that happens in last project so that common risk can be evaluated and mitigate at the very beginning.Important risk management actions should be documented as soon as they arise in every risk management meeting because this helps to speed up the meeting. I do also agree with my classmates that a strategy for breaking down the risks should be in place and that people should be prepared.
Risk meetings should have an agenda that everyone is already aware of. This way all attendees know what the meeting will be about. I think breaking down the risks in categories is a good idea because people can focus on the different aspects and contribute as needed. There are many options as to how to categorize the risks, some can be by severity. Throughout the meeting, notes are highly important so that the risks that are being evaluated can be noted down in charts along with any side comments that attendees may have added. Group discussions about potential risks can be very helpful, these can be done using questionaries. A quality person will take note of everything and use the information gathered for further risk analysis.
A good way to run a risk management meeting is to plan ahead of time and leave the meeting with enough information to write a risk management plan. As part of the quality department, it is imperative to ensure that there are no risks taken when developing a new device to avoid any legal issues. Prior to the first risk management meeting, a solid understanding of the device should be known as well as writing down a list of potential risks. This list should be brought up at the meeting and investigated in front of all those that are involved. Holding a discussion on all the possible risks can better gauge what the risk matrix will look like, and will ultimately aid in sketching out the risks and their corresponding severity.
I think planning is the key to reach the goal of a successful project. The first thing in the process is identifying risks in the project, and understanding each risk and its cause and effect later on the project. Then I would simplify the needed process depending on the output from step one, in which I would be able to assign tasks to each member of the group as I already have a detailed background about the project and the possible risks. Assigning tasks and recording all that would ease the process as everyone would focus in particular on a specific task and discuss the result later. Next, will qualify risks in the project, and would study the risk level and its consequences from this point, and possible solutions. This would add some additional needs to the project such as an extra fund or extra resources to avoid these risks. Then I would plan a meeting (or may be in the same one) to perform risk evaluation in which members could discuss findings and outputs and what to do next.
As a project manager, the main this I would be looking for in a risk assessment meeting is input and feedback from everyone. Obviously as the project manager, I would have a good idea of the risk assumed by each task involved in the development process going into the meeting. However, a big aspect of risk is that it can be easily overlooked. As the project manager I would want everyone working on my team, whether or not they are actually working on the specific project we are talking about risk relating to, involved in the meeting to properly get the big picture idea about risk, and hopefully not miss anything. This would lead to the most complete idea of risk involved in every aspect of the development process, and as a result, the least risk assumed, and least resources wasted.
In my opinion, we need to ensure that everyone in the team has a full understanding of the project, including the purpose, design, use method, etc. Only by fully understanding the equipment can we recognize the risks. The team needs to understand the risks of the product, the design of the product, and the manufacturing process of the product. Then, the team can determine the contents of the risk list and evaluate each risk. After the assessment, we can take four measures to deal with the risks, including avoidance, mitigation, acceptance and transference
I believe in the risk management meeting all the departments must be present and they should be educated with the functionality of the product being made. Then everyone can make a list of the possible risks that could occur according to them and all these risks are then discussed in next meeting and try to mitigate them. The 3 types of risks are very crucial which are risk from the end user, risk involved in design and risk involved in manufacturing. Then the risks involved should be checked throughout the entire process of manufacturing the product and the company should try to mitigate as many as they can and ensure it is safe.
