Download as pdf or txt
Download as pdf or txt
You are on page 1of 7

MPM664 PROJECT RISK ANALYSIS

Assignment 1
Contents
No table of contents entries found.
Disaster Recovery Control – How much has been lost; It is a measure of how much it takes to get back
on track
Unplanned catastrophes are always waiting just around the corner to derail your project. For this case
study you have been appointed project manager, or risk manager to prepare a risk management plan,
and a disaster recovery plan for the project office on an IT project. Your risk management planning
should consider how you would address natural disasters (flood, power cut, earth quake, fire). Your
presentation should include the following:

1. Identify the risks


2. Disaster recovery preparation – training
3. Disaster recovery control
4. Information back-up and post disaster retrieval
5. Post disaster communication plan

INTRODUCTION

A project of scale 3 million was proposed by the Client being ButterNet and the scope is to deliver a set
of Computers (12 Computers), 2 Printers, a fully furnished working Local Area Network Connection, a
100mb internet connection, 5 60inch interconnected LED TVs, Finger Print Access Lock
IT Project Risk Management Plan
Project Title: Project Number:

Anticipated Project Start Date:


Project Leader/Manager: T loanfa
08 March 2022

Sponsor: ButterNet Date Prepared: 27 February 2022

Estimated Completion Date: 08 July


Project Risk Level: Medium Risk / Complexity
2022

Team Members:
• T Loanfoa – Project Manager
• Yosh Hktam – SHE Manager
• Heicha – Risk Manager
• Sidgh – System Engineer
• M Vaas – IT Officer
• Doria – Configuration Manager

Purpose of Project: (high-level narrative regarding what this project is expected to accomplish & its benefits)
• As appropriate, include information from the IT Project Initiation form.

Examples of what could be included in the Purpose of Project section are:

• Give a concise goal statement.


• What is being accomplished?
• What are the major benefits expected from this project?

Background: (brief narrative regarding what led to this project proposal)


• A project of scale 3 million was proposed by the Client being ButterNet and the scope is to deliver
a set of, , , , ,
• As appropriate, include information from the IT Project Initiation form.

Examples of what could be included in the Background section are:

• Provide a brief project history.


• Justification of why this project should be done.
• What are the expected consequences of this project?
• What makes this project unique or special?

Deliverables:
• 12No. Computer
• 12No Microsoft Operating Systems running Microsoft Office 360
• A VPN Connection for Home Accessibility
• 2 Canon Printers
• Fully furnished working Local Area Network Connection
• 100mb internet connection
• 5No. 60inch interconnected LED TVs
• Fingerprint Access Lock

Project Risks: (those involved in or who may be affected by project activities)


• As appropriate, include information from the IT Project Initiation form and the IT Project
Resources and Staffing Plan.

Examples of what could be included in the Stakeholders section are:

• Communication risk
• Technology risk
• Scope creep risk
• Cost risk
• Operational risk
• Health and safety risk
• External hazards risk (flood, power cut, earthquake, fire)

• List all internal (IT) teams affected by the project (e.g., 4Help, DAA, CNS, OCS, AIS…)
• List university non-IT, individuals or organizations, involved in or affected by the project.
• Steering committee members.
• List other stakeholders and identify customers of this project or service.
• Please see Addendum 1 for a thorough list of potential project stakeholders.

Disaster recovery preparation – training: (define product ownership and who is responsible for product
maintenance & support)

• As appropriate, include information from the IT Project Communications Plan, the IT Project
Quality Management Plan, and the IT Project Training Plan.

Examples of what could be included in the Operations & Support section are:

• Identify responsibility for Knowledgebase & web documentation.


• Identify team responsible for production ownership & maintenance.
• Identify team responsible for product support (e.g., 4Help, functional team).
• Identify any needed training.
• Any communications and marketing of this product or service.
Disaster recovery control: (define product ownership and who is responsible for product maintenance & support)
• As appropriate, include information from the IT Project Communications Plan, the IT Project
Quality Management Plan, and the IT Project Training Plan.

Examples of what could be included in the Operations & Support section are:

• Identify responsibility for Knowledgebase & web documentation.


• Identify team responsible for production ownership & maintenance.
• Identify team responsible for product support (e.g., 4Help, functional team).
• Identify any needed training.
• Any communications and marketing of this product or service.

Information back-up and post disaster retrieval: (define product ownership and who is responsible for product
maintenance & support)

• As appropriate, include information from the IT Project Communications Plan, the IT Project
Quality Management Plan, and the IT Project Training Plan.

Examples of what could be included in the Operations & Support section are:

• Identify responsibility for Knowledgebase & web documentation.


• Identify team responsible for production ownership & maintenance.
• Identify team responsible for product support (e.g., 4Help, functional team).
• Identify any needed training.
• Any communications and marketing of this product or service.

Find attached a Risk Register of this project.

You might also like