Info Tech Project
RUNNING CASE
Tony and his team identified some risks the first month of the Recreation and Wellness Intranet Project. However, all they did was document them in a list. They never ranked them or developed any response strategies. Since several problems have been occurring on the project, such as key team members leaving the company, users being uncooperative, and team members not providing good status information, Tony has decided to be more proactive in managing risks. He also wants to address positive as well as negative risks.
1. Create a risk register for the project, using Table 1 and the data below it as a guide. Identify six potential risks, including risks related to the problems described above. Include negative and positive risks.
1. Plot the six risks on a probability/impact matrix, using Figure 11-6. Also assign a numeric value for the probability and impact of each risk on meeting the main project objective. Use a scale of 1 to 10 in assigning the values, with 1 being low and 10 being high. For a simple risk factor calculation, multiply these two values (the probability score and the impact score). Add a column to your risk register to the right of the impact column called Risk Score. Enter the new data in the risk register. Write your rationale for how you determined the scores for one of the negative risks and one of the positive risks.
1. Develop a response strategy for one of the negative risks and one of the positive risks. Enter the information in the risk register. Also write a separate paragraph describing what specific tasks would need to be done to implement the strategy. Include time and cost estimates for each strategy, as well.
1. Summarize your findings in a 700 word minimum, APA formatted, Word document.
Any Excel documents and/or screenshots created to display your tasks need to be copied and pasted into the Word document at the end of the summary, and the assignment should be submitted as one document.
Table 1
Sample Risk register
Number | Risk area | Type | Risk score | Time and cost | Response strategy |
1 | Team composition | Positive | 60 | 2 months
Depends upon skill |
Proper staffing |
2 | High levels of attrition | Negative | 36 | ||
3 | Lack of team communication | Negative | 35 | ||
4 | Users not being cooperative | Negative | 15 | ||
5 | Communication protocols between
users and team not healthy |
Negative | 21 | ||
6 | Deadlines not being met due to
conflicts and frictions |
Negative | 80 | Weekly
Loss of project |
Project coordination and effective leadership |
Figure 11-6