0% found this document useful (0 votes)
3 views3 pages

Software Engineering Risk Management Guide

The document outlines various types of risks associated with software engineering, including staff turnover, management changes, hardware unavailability, and requirement changes. It categorizes these risks into project and product risks, as well as business risks. The information is presented by Kashif Asrar, a lecturer at NED University of Engineering & Technology.

Uploaded by

arhamk30082005
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
0% found this document useful (0 votes)
3 views3 pages

Software Engineering Risk Management Guide

The document outlines various types of risks associated with software engineering, including staff turnover, management changes, hardware unavailability, and requirement changes. It categorizes these risks into project and product risks, as well as business risks. The information is presented by Kashif Asrar, a lecturer at NED University of Engineering & Technology.

Uploaded by

arhamk30082005
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

Module: Software Engineering

Topic: Risk Management

Kashif Asrar
Lecturer, Final Year Project Coordinator
Computer & Info. Systems Engineering
NED University of Engineering & Technology
Email address: kashifasrar@[Link]
1
Identify the Type of Risk
1. Staff Turnover
2. Change in Management
3. Unavailability of hardware
4. Change in requirements
5. Delay in specifications
6. Underestimation of software size
7. Case Tools under Performance
8. Technology Change
9. Product Competition

2
Identify the Type of Risk
1. Staff Turnover (Project)
2. Change in Management (Project)
3. Unavailability of hardware (Project and
Product)
4. Change in requirements (Project and Product)
5. Delay in specifications(Project and Product)
6. Underestimation of software size (Project and
Product)
7. Case Tools under Performance (Product)
8. Technology Change (Business)
9. Product Competition (Business)
3

You might also like