Software Risk Management

Brief Introduction to Software Risk Management. (Teaching Materials)

Transcript

1. Software Risk Management Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
2. Why we need understand a risk management? • We need to minimize a loss? • Yes. But No. We need to minimize the “risk”. • S**t will happen. When it happen, it is cost. Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
3. Risk Example? Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
4. Risk Example • Software past due • Main Feature do not meet with Client Request • Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
5. Risk Management the process of identifying, analyzing and responding to risk factors throughout the life of a project and in the best interests of its objectives. Proper risk management implies control of possible future events and is proactive rather than reactive. https://bia.ca/risk-management-the-what-why-and-how/ Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
6. Risk on Software Development Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
7. Risk Management Risk and the associated cost to address the risk, varies over the project life cycle For initial phase there is high chance of risk events, but low cost impact For final phase there is low chance of risk events, but cost impact is high Identifying and managing risks will greatly affect project success Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
8. Routine in Risk Management Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
9. Risk Management Steps • There are four major steps to developing a risk management plan • Identify all the possible risk events that could affect the project • Assess each risk in terms of probability, impact severity and controllability • Develop a strategy and/or contingency for responding to each risk • Monitor and control risks dynamically A Risk Management Plan should be developed during the initial project phase and immediately implemented The plan should reviewed & revised as needed during each project phase Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
10. Step 1. Identify the project risks • Generate list of all possible risks by “brainstorming” among team members • Do not attempt to assess risk probability; that is for a later step • Focus on risk events, rather than risk consequences • For example, “instrument does not return correct data” is a consequence of events like poor circuit design, incorrect or failed components, poor software implementation • First focus on overall project risks, then identify specific risks • Use your WBS to help organize your risk identification process • Seek input from sources from outside your group • Emphasize critical thinking Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
11. WBS Work breakdown structure Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
12. Easy Step? SWOT Analysis Strength, Weakness, Opportunity, Threat Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
13. Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
14. Next Week: Step 2 - 4. Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.
15. Task SWOT Analysis. Chosen Software @ Project management Tools. Due date: next 72 hours Software Testing - Irwan A. Kautsar, S.Kom., M.Kom., Ph.D.