PPT SE SACHIN.ppt
- 1. Risk Management - Introduction - Risk identification - Risk projection (estimation) - Risk mitigation, monitoring, and management (Source: Pressman, R. Software Engineering: A Practitioner’s Approach. McGraw-Hill, 2005)
- 2. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?
- 3. Risk Mitigation, Monitoring, and Management
- 4. 4 EXPLANATION • An effective strategy for dealing with risk must consider three issues (Note: these are not mutually exclusive) – Risk mitigation (i.e., avoidance) – Risk monitoring – Risk management and contingency planning • Risk mitigation (avoidance) is the primary strategy and is achieved through a plan – Example: Risk of high staff turnover (see next slide) (More on next slide)
- 5. 5 Meet with current staff to determine causes for turnover (e.g., poor working conditions, low pay, competitive job market) Mitigate those causes that are under our control before the project starts Once the project commences, assume turnover will occur and develop techniques to ensure continuity when people leave Organize project teams so that information about each development activity is widely dispersed Define documentation standards and establish mechanisms to ensure that documents are developed in a timely manner Conduct peer reviews of all work (so that more than one person is "up to speed") Assign a backup staff member for every critical technologist Strategy for Reducing Staff Turnover Background (continued)
- 6. 6 Risk Monitoring • During risk monitoring, the project manager monitors factors that may provide an indication of whether a risk is becoming more or less likely • Risk management and contingency planning assume that mitigation efforts have failed and that the risk has become a reality • RMMM steps incur additional project cost – Large projects may have identified 30 – 40 risks • Risk is not limited to the software project itself – Risks can occur after the software has been delivered to the user (More on next slide)
- 7. 7 Risk Monitoring • Software safety and hazard analysis – These are software quality assurance activities that focus on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail – If hazards can be identified early in the software process, software design features can be specified that will either eliminate or control potential hazards that will be better
- 8. 8 The RMMM Plan • The RMMM plan may be a part of the software development plan or may be a separate document • Once RMMM has been documented and the project has begun, the risk mitigation, and monitoring steps begin – Risk mitigation is a problem avoidance activity – Risk monitoring is a project tracking activity • Risk monitoring has three objectives – To assess whether predicted risks do, in fact, occur – To ensure that risk aversion steps defined for the risk are being properly applied – To collect information that can be used for future risk analysis • The findings from risk monitoring may allow the project manager to ascertain what risks caused which problems throughout the project
- 9. 9 Seven Principles of Risk Management View software risks as a business problem that is intended to solve Maintain a global perspective Think about risks that may arise in the future; establish contingency plans Take a forward-looking view Encourage all stakeholders and users to point out risks at any time Encourage open communication Integrate the consideration of risk into the software process Integrate risk management Modify identified risks as more becomes known and add new risks as better insight is achieved Emphasize a continuous process of risk management A shared vision by all stakeholders facilitates better risk identification and assessment Develop a shared product vision Pool the skills and experience of all stakeholders when conducting risk management activities Encourage teamwork when managing risk
- 10. 10 Summary • However, the time spent in risk management results in – Less upheaval during the project – A greater ability to track and control a project – The confidence that comes with planning for problems before they occur • Risk management can absorb a significant amount of the project planning effort…but the effort is worth it
Editor's Notes
- #9: (Paragraph 5.19.1)