Risk Analysis Action Plan

If you haven’t already, register a username for yourself so you can discuss this topic in our Outsourcing Risks forum.

The following is a risk analysis plan that’s usually applied to software development, but certainly appropriate for outsourcing projects since both depend on collaboration. Use it to develop appropriate responses to things like delays, budget cuts, and/or non-participation.

Risks To Schedule Estimates

• Action to take if you discover your project can’t be completed in the specified time:
• Action to take if a delay in one task delays other tasks:
• Action to take if marketing results in development decisions that lengthen the schedule:
• Action to take if budget cuts occur:
• Action to take if equipment is not available, or, is available – but inadequate:
• Action to take if development tools do not work as expected:

Risks To End-User Involvement

• Action to take if end-user input is not solicited:
• Action to take if end-user refuses to participate:
• Action to take if end-user is unable to participate due to incompatibly issues:
• Action to take if end-user’s feedback response time is slower than anticipated:
• Action to take if end-user insists on new requirements:
• Action to take if end-user has expectations you can’t meet:
• Action to take if end-user finds project to be unsatisfactory:

Risks To Using Contracted Work

• Action to take if qualified service provider is not available:
• Action to take if qualified service provider does not want the job:
• Action to take if qualified service provider is available only part-time:
• Action to take if qualified service provider works slower than expected:
• Action to take if qualified service provider delivers components of low quality:
• Action to take if qualified service provider delivers components that have to be improved:
• Action to take if qualified service provider does not deliver components on time:
• Action to take if qualified service provider quits:
• Action to take if qualified service provider is hired late in project:

Risks To Requirements/Development

• Action to take if additional requirements are added:
• Action to take if requirements continue to change:
• Action to take if project will run in an unfamiliar environment:
• Action to take if multiple compatibility routines are required:
• Action to take if development tools are not in place on time:
• Action to take if project is dependent upon technology still under development:
• Action to take if development tools need work-arounds, or if new tools are needed:
• Action to take if technology repeatedly causes errors:

External Resources:

1. Assessing Uncertainties Beyond Expected Values and Probabilities
2. Risk Assessment And Decision Making In Business And Industry
3. The Essentials of Risk Management