Scribd
Upload
25 views9 pages

190 - Risk Management SE

Presentation on Risk Management in Software Engineering

Uploaded by

prathameshacharekar98
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
25 views9 pages

190 - Risk Management SE

Presentation on Risk Management in Software Engineering

Uploaded by

prathameshacharekar98
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

RISK MANAGEMENT

Prathamesh Acharekar - 190


SOFTWARE ENGINEERING
Risk Management
Risk management is an essential part of software engineering. It is the process of
identifying, assessing, and addressing potential risks that could impact the success of
a software project.

By effectively managing risk, software engineering teams can improve the likelihood of
project success and reduce the likelihood of project failure.
Types of Risks

Project Risk
They Threaten the Project Plan
If they become real, it is likely that the project schedule will slip and that costs will
increase

Technical Risk
They threaten the quality and timeliness of the software to be produced
If they become real, implementation may become difficult or impossible

Business Risk
This type of risks contain risks of building an excellent product that no one need,
losing budgetary or personnel commitments, etc.
Types of Risks

Known Risk
Those risks that can be uncovered after careful evaluation of the project plan, the
business and technical environment in which the project is being developed, and
other reliable information sources (e.g., unrealistic delivery date)

Predictable Risk
Those risks that are extrapolated from past project experience (e.g., past turnover)

Unpredictable Risk
Those risks that can and do occur, but are extremely difficult to identify in advance
Risks Management Process
1. Identify Potential Risks:
The first step involves brainstorming and identifying potential risks
that could arise during the project's lifecycle. This can be done
through techniques like interviewing stakeholders, reviewing project
documentation, and analyzing past projects.

Example: In a software project to develop a new e-commerce


platform, potential risks could include:

• Unclear requirements leading to scope creep


• Integration issues with existing systems
• Delays in third-party dependencies
• Security vulnerabilities
2. Assess Risk Probability and Impact:
Once potential risks are identified, the next step is to assess their
likelihood of occurrence and the potential impact they could have
on the project. This involves assigning probability and impact
ratings to each risk.
3. Risk Mitigation Strategies:
For each prioritized risk, develop mitigation strategies to reduce the
likelihood of occurrence or the potential impact if the risk
materializes.

Example:
Unclear requirements: Conduct workshops with stakeholders to
clarify requirements thoroughly

4. Monitor and Update Risks:


Risk management is an ongoing process throughout the project's
lifecycle. Regularly monitor risks to assess their status, identify new
risks, and update mitigation strategies as needed.

Example:
Conduct regular risk reviews to assess the effectiveness of
mitigation strategies
Thank You!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy