risk register templatethe risk register template contains W r i t i n g

risk register templatethe risk register template contains W r i t i n g

Chapter 11 – Read Chapter 11 – Project Risk Management then review the material below and follow the instructions

Assignment Overview:

Your team will create a Project Risk Register using the provided Risk Register template for an IT infrastructure project. This assignment is a true Group Exercise and the project is not associated with or based on Case Study material in the textbook, but on the following scenario:

Your IT consulting firm (NetScan, LLC) was contracted to install the IT infrastructure (cabling, servers, workstations, wireless APs, other hardware, software, network equipment, and internet connectivity) in a new, 20,000 sq. ft. building for Blue Suit Consulting. The initial build-out includes 15 offices and a data center on a single floor with the building being ready to start the installation 4 months from now. Your CIO budgeted $32,000.00 for the project and expects completion in 3 months.

Your Assignment: As a team, develop an initial Risk Register for this project.

As you have learned in the preceding weeks, there are many aspects of managing a project, and risks can arise in any of them. For this assignment, it is recommended that each team member focus on identifying events that could occur that would impact one of these aspects:

Schedule – you have two target dates in the above description
Budget – how far does $32,000 go? (Note: your project is only to INSTALL the infrastructure, your client, Blue Suit Consulting, will pay for the equipment and materials)
Staffing – you will need a team. What can go wrong?
Stakeholder Management – you have a client to keep happy…
Communication Management – Where are the risks to your communication plan?
Procurement – Blue Suit is paying, but what can go wrong in the purchasing process?
Quality – what events or factors can result in unacceptable quality?
Integration – all of the above need to integrate and stay in synch.

Team Responsibility:

  • As a team, meet early in the week and determine which team member will focus on which of the above areas, or come up with your own categories.
  • Make sure everyone understands what is required
  • As a group, you can identify more details if you wish
  • Decide on a due date for submitting all contributions to the team leader. The group work MUST BE SUBMITTED BY THE TEAM LEADER and by the assignment deadline, so you should choose a due date BEFORE that for sending all team contributions to the team leader.

Team Member Responsibility:

  • Each team member must identify at least FOUR individual risks associated with their area.
  • The team member’s name should appear in Column D of their Risk Register template
  • The Risk Register template contains a few examples to help you; however, these examples must be REMOVED before submitting your completed document to the team leader.
  • Use the provided Risk Register template and fill in the risk register according to the following guidelines:
    • Risk ID: Continue the numbering scheme in the Risk Register template
    • Description: This should describe what the potential event is that could disrupt your plans should it occur.
      • Be SPECIFIC! Saying “We might go over budget” is NOT an appropriate entry. WHY would you go over budget? (Going over budget is a RESULT, not a cause.)
    • Impact on Project: Describe what will happen to the project should the event described in column B actually happen. Again, be specific!
    • Identified by: Enter your name in this column
    • Probability: What is the likelihood of the risk occurring Low, Medium, or High?
    • Impact: How serious will the impact be (Low, Medium, or High) if the risk occurs?
    • Risk Score: Multiply Probability * Impact
      • Low=1, Medium=2, High=3. Example: a Low Probability/Medium Impact risk has a risk score of 2 (1*2). Be sure there is a formula in the cell.
    • Response Type: Pick from the drop-down list. See Chapter 11 for explanations of each of the four response types.
    • Response Strategy: Explain exactly what you will do to Avoid, Transfer, or Mitigate the risk. If you are Accepting the risk, you should explain why you are taking no action.
    • Owner: In real life, this is required, so that each risk is assigned to someone. For our purposes, you can leave it blank.
  • Date last reviewed: Again, in the real world, you need to keep track of when you have reviewed each risk – which should be done regularly. For this exercise, you can leave it blank.
  • Assumptions: Use this to document any assumptions you made in coming up with the risk. This item is included because you don’t have a project plan to go by, so you may want to make up some assumptions and then identify risks based on them. See the examples included in the provided Risk Register template.