Project Risk Register using the provided Risk Register template Download Risk Register templatefor 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.

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:

1) Stakeholder Management - you have a client to keep happy... 2) Communication Management - Where are the risks to your communication plan?

• Each team member must identify at least FOUR individual risks associated with their area.
• he 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 Download 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. Example:
• Risk Register Template

Risk ID	Description	Impact on Project	Identified By	Probability	Impact	Risk Score	Response Type	Response Strategy	Owner	Date Last Reviewed	Assumptions
R1	No Network Architect is available for the next month	Network design cannot commence without an architect, which will delay project start	Jim	High	Medium	2	Mitigate	The Network Engineer can begin preliminary design. Network Architect can review periodically for general feedback			Assumes the Network Architect can find small blocks of time to do high level review.
R2	Building construction could be delayed, pushing back our start date	If the delay is long, team members might get assigned to other projects.	Jim	Medium	Medium	3	Transfer	Include a clause in the contract stipulating that Blue Suit will pay for staff time beginning on the planned start date, even if work cannot commence.			Assuming we decided on a DJ as the music provider instead of a band.