risk analysis · software risk analysis •complexity of the technology •technical knowledge...
TRANSCRIPT
![Page 1: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/1.jpg)
Risk Analysis
KANOKWATT SHIANGJENCOMPUTER SCIENCE
SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITY OF PHAYAO
![Page 2: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/2.jpg)
Contents
• What is risk?
• Risk Management
• Q & A
• References
2
http://corefn.com/projects/risk/
![Page 3: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/3.jpg)
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
![Page 4: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/4.jpg)
Risk
“ An expectation of loss ”
4
https://kidshelpline.com.au/young-adults/issues/risk-taking https://kidshelpline.com.au/teens/issues/taking-risks
![Page 5: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/5.jpg)
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
![Page 6: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/6.jpg)
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/
![Page 7: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/7.jpg)
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
![Page 8: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/8.jpg)
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
![Page 9: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/9.jpg)
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
![Page 10: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/10.jpg)
The effects of software engineering risk
• Development of poor quality software
• Terminations
• Schedule delays
• Increase in production cost
• Overrun of project resources
10
![Page 11: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/11.jpg)
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/
![Page 12: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/12.jpg)
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
![Page 13: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/13.jpg)
Types of risk in software project management
• New, unproven technologies
• User and functional requirements
• Application and system architecture
• Performance
• Organizational
13
![Page 14: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/14.jpg)
Software risk management
• Software risk identification
• Software risk analysis
• Software risk planning• Software risk monitoring
• Software risk mitigation
14
![Page 15: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/15.jpg)
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
![Page 16: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/16.jpg)
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
![Page 17: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/17.jpg)
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
![Page 18: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/18.jpg)
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
![Page 19: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/19.jpg)
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
![Page 20: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/20.jpg)
Q & A
20
![Page 21: Risk Analysis · Software risk analysis •Complexity of the technology •Technical knowledge possessed by the testing team •Conflicts within the team •Teams being distributed](https://reader034.vdocument.in/reader034/viewer/2022042111/5e8cb7a63adfec3dd0287ec9/html5/thumbnails/21.jpg)
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