solved Discussion Forum Week 6The chapter on project risk planning discusses

Discussion Forum Week 6The chapter on project risk planning discusses the risk planning process and the associated tools and techniques. Risk planning consists of two types: quantitative risk planning and qualitative risk planning. Risks could be positive or negative based on their intended impact. Positive risks are termed as opportunities and negative risks are termed as threats. Additionally, it is important for the project manager to determine the risk propensity of the organization and the employees and use the knowledge to develop risk strategies. Learning about the top risks in software management was important and can be used as a checklist while developing a Risk Management Plan (RMP) for software projects (Kloppenberg et al, 2019).Dinner Party Risks & Triggers:Risk is an uncertain or unintended event that can impact the project. A trigger is a circumstance that might invoke the risk. In this case the organization must commence the risk action or strategy (Kloppenberg et al, 2019). In the given scenario, a major risk could be that the dishes might get burnt or inedible. A trigger for that is losing the recipe. Another risk could be that the guests don’t arrive on time. A possible trigger could be sudden unforeseen weather conditions like flood or a storm. Risk Acceptance:In some cases, organization choose to accept the risk as a risk management strategy. Risk acceptance is usually done for minor risks that have a lesser probability of occurring. We developed a health insurance coding product for doctor offices and accepted the risk of regulatory changes. We kept monitoring for the trigger, which is a change to the Medicare and Chip policies. We decided to accept the rik as it wouldn’t impact the product much and we could have tweaked the existing code to change the reimbursement cost according to the new regulation. The expected change did not happen, and it was a good strategy to accept that risk. Integrating quality within project planning:All software projects integrate quality management within the project planning process. Test planning is the guide which is used to validate the quality of the product increment that is being developed. It is imperative to embed quality in project planning, so that the team is aware of how to validate the work being performed and raise red flags in case of defects which can be then triaged and fixed.Common Cause Variation (CCV) & Special Cause Variation (SCV):CCV is also termed as the noise of the process. Noise of the process is the process deviations that are imbedded in the process and are natural to the process. CCVs cannot be avoided unless process is re-engineered. However, SCVs are those variations in the process that exceed the predetermined control limits. These control limits are usually three standard deviations away from the mean. A major healthcare issue in the country is the Emergency Room (ER) wait times. The ER wait times cause a backlog that prevents clinicians from helping critically ill patients. I used to work in the process improvement team of a healthcare organization. The average acceptable wait time is 35 minutes. However, there were many common cause variations that occur due to the nature of the process. The CCVs are wait times that exceed 35 but are within 60 minutes. However, SCVs are those process variations that exceeded the 60 minutes limit. When SCVs occur, the process improvement team will visit the floor and work with the clinical and nonclinical team to determine the root cause by performing Root Cause Analysis (RCA). ReferencesKloppenborg, T. J., Anantatmula, V. S., & Wells, K. N. (2019). Contemporary project management, 3rd edition (3rd ed.). Cengage.