Risk Analysis

KANOKWATT SHIANGJENCOMPUTER SCIENCE

SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY

UNIVERSITY OF PHAYAO

Contents

• What is risk?

• Risk Management

• Q & A

• References

2

http://corefn.com/projects/risk/

Risk

“ A situation involving exposure to danger ”

3

https://kidshelpline.com.au/young-adults/issues/risk-taking https://kidshelpline.com.au/teens/issues/taking-risks

Risk

“ An expectation of loss ”

4

https://kidshelpline.com.au/young-adults/issues/risk-taking https://kidshelpline.com.au/teens/issues/taking-risks

Risk

“ Opportunities cannot move forward without risk”

5

https://kidshelpline.com.au/young-adults/issues/risk-taking https://kidshelpline.com.au/teens/issues/taking-risks

Types of risk

• internal risks: that are of the project manager.

• external risks: that are of project manager.

6https://executiveresumerescue.com/158/improve-your-job-search-results-with-swot-analysis/

SWOT

•Strengths: Characteristics of the business that give it

•Weaknesses: Characteristics of the business that place the

business or project at a

•Opportunities: Elements in the environment that the business or

project could

•Threats: Elements in the environment that could

for the business or project

7

Software Risk

• A potential problem that may or may not occur in the future

• A possibility of “ suffering ” from “ loss ” in software development process is called a “ ”

• Software risk exists because the future is uncertain and there are many “ ” and “ ” things that cannot be incorporated in the project plan.

8

Types of software engineering risks

• The manager has to deal with risks from 3 possible cases:• Known knowns are software risks that are

such as not enough number of developer can delay the project delivery.

• Known unknowns are risks that the project team is that such risk exists in the project or not. For example, it

is not possible to capture the requirement properly if we cannot interview with the truly user.

• Unknown Unknowns are those kind of risks about which such as working with new technologies or tools

that you have no idea about

9

The effects of software engineering risk

• Development of poor quality software

• Terminations

• Schedule delays

• Increase in production cost

• Overrun of project resources

10

Risk Management

• Risk management means risk containment and mitigation

• First, you ‘ve got to identify and plan

• Then, be ready to act when a risk arises,

drawing upon the experience and

knowledge of the entire team

to minimize the impact to the project

11http://www.transformsales.com.au/to-win-the-sale-focus-on-risk/

Risk Management

• Identify risks and their triggers

• Classify and prioritize all risks

• Plan that links each risk to mitigation

• Monitor for risk triggers during the project

• Implement the mitigating action if any risk occurs

• Communicate risk status throughout project

12

Types of risk in software project management

• New, unproven technologies

• User and functional requirements

• Application and system architecture

• Performance

• Organizational

13

Software risk management

• Software risk identification

• Software risk analysis

• Software risk planning• Software risk monitoring

• Software risk mitigation

14

Software risk identification

15

Current Project

Review the Past Project History

Assess the practices that are being followed in the present project

Come up with creative ideas for

future projects

Software risk analysis

• Complexity of the technology

• Technical knowledge possessed by the testing team

• Conflicts within the team

• Teams being distributed over a large geographical area

• Usage of poor quality testing tools

16

Software risk planning

• Defining preventive measure that would lower down the likelihood or probability of various risks.

• Define measures that would reduce the impact in case a risk happens

• Constant monitoring of processes to identify risks as early as possible

17

Software risk monitoring

• Publish project status and risk management issues

• Revise risk plans to any major changes in project schedule

• Review and reprioritize risks

• Brainstorm on potentially new risks after changes to schedule or scope

18

Software risk mitigation

• Accept: Acknowledge that a risk is impacting the project.

• Avoid: Adjust project scope, schedule, or constraints to minimize the effects of the risk

• Control: Take action to minimize the impact of the risk

• Transfer: Implement an organizational shift in accountability, responsibility to stakeholders that will accept the risk

• Continue Monitoring: Often suitable for low-impact risks, monitor the project environment for potentially increasing impact of the risk.

19

Q & A

20

References• https://www.test-institute.org/What_Is_Software_Risk_And_Software_Risk_Management.php

• http://www.castsoftware.com/research-labs/risk-management-in-software-development-and-software-engineering-projects

21