Risk Management: Naveen Prajulit Dang Symbiosis International Unversity, MBA (2010-2012)
Risk Management: Naveen Prajulit Dang Symbiosis International Unversity, MBA (2010-2012)
Risk Management: Naveen Prajulit Dang Symbiosis International Unversity, MBA (2010-2012)
Description Experienced staff will leave the project before it is finished. There will be a change of organisational management with different priorities. Hardware that is essential for the project will not be delivered on schedule.
Requirements change
Specification delays
Size underestimate
CASE tool underperformance
Technology change
Product competition
Business
Business
The underlying technology on which the system is built is superseded by new technology.
A competitive product is marketed before the system is complete.
Risk type
Possible risks
Technology
The database used in the system cannot process as many transactions per second as expected. Software components that should be reused contain defects that limit their functionality.
It is impossible to recruit staff with the skills required. Key staff are unavailable at critical times. Required training for staff is not available. The organisation is restructured so that different management are responsible for the project.
People
Organisational
Tools
Requirements
The code generated by CASE tools is inefficient. CASE tools cannot be integrated.
Changes to requirements that require major design rework are proposed. Customers fail to understand the impact of requirements changes.
Estimation
The time required to develop the software is underestimated. The rate of defect repair is underestimated. The size of the software is underestimated.
Risk analysis
Assess probability and seriousness of each risk. Probability may be very low, low, moderate, high or very high. Risk effects might be catastrophic, serious, tolerable or insignificant.
High
Catastrophic
Moderate Moderate
Serious Serious
Moderate
Serious
Probability
Moderate
Effect
Serious
High
Serious
High Moderate
Tolerable Tolerable
High
Tolerable
Risk planning
Consider each risk and develop a strategy to manage that risk. Avoidance strategies The probability that the risk will arise is reduced;
Minimisation strategies The impact of the risk on the project or product will be reduced;
Contingency (in contact) plans If the risk arises, contingency plans are plans to deal with that risk;
Risk monitoring
Assess each identified risks regularly to decide whether or not it is becoming less or more probable.
Also assess whether the effects of the risk have changed. Each key risk should be discussed at management progress meetings.
Risk indicators
Risk type Technology People Potential indicators Late delivery of hardware or support software, many reported technology problems. Poor staff morale, poor relationships amongst team member, job availability.
Organisational
Tools
Requirements Estimation
Organisational gossip, lack of action by senior management Reluctance by team members to use tools, complaints about CASE tools, demands for higher-powered workstations Many requirements change requests, customer complaints Failure to meet agreed schedule, failure to clear reported defects.
Risk indicators
Risk type Technology Potential indicators Late delivery of hardware or support software, Many reported technology problems.
Project Team
Poor staff morale, poor relationships amongst team members, job availability.
Organisational
Tools
Requirements Estimation
THANK YOU.