"Risk Management" in cmmi4 process domain"

Software risks refer to the possibility that the Project software cannot meet the expected objectives in terms of schedule, cost, function, real-time performance, reliability, and use of key computer resources. Risk management activities include early identification of high-risk projects, identification of events that generate or increase risks, prototype or advance implementation for high-risk modules, and close monitoring of critical project risks.
This procedure should cover the following aspects:
(1)
Establish software risk management plan documents to identify and manage software risks. The software risk management plan document covers the following resources, including personnel and tools, and risk management methods, including
Analysis, priority assignment, planning, monitoring, and solutions; identified risk list, including evaluation, priority, status and plan; Risk Management Schedule; responsibilities and powers; exchange risk status and
Activity method and frequency.
(2) define alternatives for each software risk and guidelines for alternative selection.
(3) When the software risk management plan is promulgated for the first time and major changes to it in the future, the software risk management plan should be reviewed at the same level.
(4) manage and control software risk management plans.
(5) The software risks should be tracked at the selected project milestones, the specified risk check points, and during the planning that will affect significant changes to the software project, and reevaluate and re-plan it. This process should review and revise the risk priority and software risk management plan, and refine risk assessment using the monitored information.
(6)
Software Risk, software risk management plan and risk mitigation results should be announced to software engineering groups and other related groups and individuals. These related groups and individuals include customers, subcontractors, end users, software estimation groups, and System Engineers.
Process Group, system test group, Software Quality Assurance Group, Software Configuration Management Group, Contract Management Group, document support group, etc. The end user here refers to the end user or end user representative specified by the customer.