Ppt on risk management in software engineering

SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy. See our Privacy Policy and User Agreement for details. Create your free account to read unlimited documents. The SlideShare family just got bigger. Home Explore Login Signup.

Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. Next SlideShares. You are reading a preview. Create your free account to continue reading. Sign Up. Upcoming SlideShare. Risk management. Embed Size px.

Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Show More. Views Total views. Actions Shares.

No notes for slide. Risk management software engineering 1. Risk strategies Reactive risk strategy Proactive risk strategy 5. Monitors the project for likely risks. Then ,the team attempts to correct the problem ,this iswrong. Then ,the team attempts to correct the problem ,this is often called a fire fighting mode. Better than reactive risk strategy.

Begins long before technical work is initiated. Software team establishes a plan for managing risks. When risks are analyzed ,it isWhen risks are analyzed ,it is important to quantify the level ofimportant to quantify the level of uncertainty and the degree ofuncertainty and the degree of loss associated.

Threaten the project plan. If the risks become real, it is likely that the project schedule willIf the risks become real, it is likely that the project schedule will slip and the costs will increase. Degree of structural uncertainty. Market risk :building an excellent product or system that no one really wants.

Strategic risk :building a product that no longer fits into the overall business strategy for the company. Management risk :losing the support of senior management due to change in focus or a change in people. Budget risk :losing budgetary or personnel commitment. Known risksKnown risks Those that can be uncovered after careful evaluation ofThose that can be uncovered after careful evaluation of the project plan, the business and technical environmentthe project plan, the business and technical environment in which the project is being developed ,and otherin which the project is being developed ,and other reliable information source.

Predictable risks:Predictable risks: Risks that ere extrapolated from past project experience. Unpredictable risks:Unpredictable risks: Risks that are extremely difficult to identify in advance joker in the desk. Probability that the risk is real. Consequences of the problems associated with the risk. Risk tableRisk table A risk table provides simple techniques for risk projection.

As time passes and more is learned about risk ,it may be possible to refine the risk into a set of more detailed risks each somewhere easy to monitor and manage. BasedFor ex, assume that high staff turnover is noted as a project risk r1. Based on past history and management intuition, the likelihood l1 of highon past history and management intuition, the likelihood l1 of high turnover is estimated to be 0.

To mitigate this risk, you would develop a strategy for reducingTo mitigate this risk, you would develop a strategy for reducing turnoverturnover After risk mitigation ,risk monitoring activity commence.

Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Technology , Business. Download Now Download Download to read offline. Risk analysis Download Now Download Download to read offline. Software Risk Analysis. Powerpoint Risk Assessment. Risk analysis and management. Risk assessment presentation. Risk assessment principles and guidelines. Related Books Free with a 30 day trial from Scribd. Related Audiobooks Free with a 30 day trial from Scribd.

Elizabeth Howell. I don't have enough time write it by myself. Sanjana Balaji. Raksha Sharma , Vishal Gupta. Dinesh K. Seung-Kyu Sung. Show More. Views Total views. Actions Shares. No notes for slide. Risk analysis 1. Reactive strategy Software team does nothing till the risk becomes real. Proactive strategy Risk management begins long before technical work starts. Risks are identified and prioritized by importance. Then team builds a plan to avoid risks if they can or minimize their probability of occurrence or establish plan if risks become real.

Technical risk o Threatens the quality of the software to be produced.