Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.

Version:< 1.0> Date: 31 October 2011

TEAM-3

Coventry University Track Locate and Assemble Risk Management Plan Version <1.0>

CONFIDENTIAL

(C) TEAM-3, 2011

Page 1 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

Revision History
Date 31 October 2011 Version 1.0 Description Final copy Author Kishen Gajanan

CONFIDENTIAL

(C) TEAM-3, 2011

Page 2 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Overview 2. Risk Summary 3. Risk Management Tasks 4. Organisation and Responsibilities 5. Budget 6. Tools and Techniques 7. Risk Items to Manage 4 4 4 4 4 4 4 5 7 8 8 8

CONFIDENTIAL

(C) TEAM-3, 2011

Page 3 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

1. Introduction 1.1 Purpose The purpose of risk management plan document is to make a note of all the difficulties one might overcome during the development of the software, so that one can make a plan on how to overcome these risks. Tools and techniques that has to be used can be planned at the beginning itself so that we are well prepared in advance to handle the troubles. 1.2 Scope Team-3 have been assigned with the project for developing a tool for Coventry University, CUTLASS which is a tool that helps student to fine their lost or stolen devices, in this document we describe the various methods on how to overcome the risks and provide an efficient product. 1.3 Definitions, Acronyms and Abbreviations CUTLASS: Coventry University Track Locate and Assemble. 1.4 References None 1.5 Overview Further in Risk Management Plan documents, it consists of various tools and techniques that we will use to effectively plan the risk occurrence. We also define the organisations and their responsibilities involved for this projects activities. List of items that have to be managed and budget for this are few topics that will be covered in this piece of document. 2. Risk Summary We are designing a website for students safety of their electronic devices. While building this we might have to overcome a few hurdles or also called the risk. At this point of development the risks that we have come across are functionality risk, where there might be problem with our equipments, which might lead to total failure of the
CONFIDENTIAL (C) TEAM-3, 2011 Page 4 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

project. Generic risks, if the client informations regarding the project is misinterpreted and we might end up building a wrong tool for them and a few system specific risks, where one might find it hard to use on few outdated systems. 3. Risk Management Tasks Under risk management task we discuss various tasks that will be performed in project to identify risk, management strategy, status and reporting schedule. There are various methods to identify the risk; we try to keep the risk list as minimal as possible. We do so by keeping the design simple and not try to complicate any functions. There is a team to monitor the risks, so that we can have knowledge on the risk set. There will be frequent checks on the system and we update periodically, we also maintain a database of the set of risks that has been overcome and status report is maintained. The risks are prioritized based on the damage it might cause to our system. They are prioritized as high, intermediate and low. High risks are the one that might lead to total failure, intermediate risks are the ones that can be overcome with few changes of causing minimal damage. Low risks are the one that might cause less threat for the project and can be solved with minimal changes. There are various strategies that can be used to for managing risks. Different risks have different strategies based on their magnitude. Here are list of top 10 risks, how they can be avoided. 1. Functionality risk can be identified by the tool that monitors the functionality of the servers. If the servers are weakening then a warning appears on the screen so that the team can save the datas with respect to the project. 2. Generic risks can be identified by keeping a constant track of the projects progress and discuss with clients regularly to make sure all the requirements of the clients are fulfilling. 3. System specific risks are based on users computer, if they are using an outdated version of operating system or if the system is not compatible. This can be prevented by specifying the system requirement for the software to work effectively.

CONFIDENTIAL

(C) TEAM-3, 2011

Page 5 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

4. Budget risk, this is most common risk where a team crosses the budget limit due to various reasons. To avoid this risk, there has to be a well structured plan for the budget and always add another 10% for the original estimation and keep it as a buffer. 5. Employee risks, while building a software there are various number of people who work on the project, when an employee is unable to work or takes leave or maybe there is a conflict, all these factors affects the development, to avoid this we must always make sure we have back up for the above concerns. 6. Equipment risks, this is also a major concern, if the equipments are faulty then it would be difficult to complete the project on time, we must have regular checks of the equipments and also check and replace immediately if any fault is found on the equipments to keep a smooth flow of the project. 7. Design risk, during the time of development there might be a small error with the design that might lead to build wrong software. To avoid this particular risk what we can do is to keep a check on the design and make sure the design is approved before the building process begins. 8. Test risk, occurs during the time of testing. This might occur due to usage of wrong tool. To avoid these test risks, we need to use the proper test cases and the belonging tool rather than compromising on existing tool. 9. Performance risks, as time passes by, the performance reduce, to overcome this issue, we need to update the systems periodically and erase the unwanted data from the system to keep it efficient and productive. 10. Deadlines risk, during development due to various reasons there might be a chance of extending our promised deadlines. If there are constant changes from client end or more functionality required are all reasons for extending deadline. To avoid this, like we do in the estimation risk, we need to have a buffer time period so that we do not face this issue. During documentation we give a 10% time buffer for the product launch date.

CONFIDENTIAL

(C) TEAM-3, 2011

Page 6 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

We have developed a tool to make a list of all the risks occurred and how the issues have been solved. When the risk occurs, we make note of it in a table and in successive column we write the status of the risk and how it was solved. They will be monitored by the team during the Corse of the project and gives information to the team of development about the causes of the risk and how it was examined.

RISK MANAGEMENT PROCESS

ANALYSE THE RISKS AND PROCESS THE RISK TO MITIGATE AND MAKE A RECORD OF THE RESOLVED ISSUE.

EVALUATE THE RISKS

PROJECT

From above figure we can see that the risks are processes and analysed, we make a record of the risks and evaluate the risks. We compare it with the project to see if the risk are realised or if any more changes are required. Once the process is completed, we make the note back into the list of risk management process for further use. The database holds the status updates. So if in future part of development one comes across same risk, the solution can be found from the previous evaluation. 4. Organisation and Responsibilities There are specific group of individuals who are in charge of the risk management motion. Here are a few of the members who are responsible Project Manager: handles the risk management plan by providing possessions for the document. He is also in charge of approving the risk handling techniques and give decisions for the team.
CONFIDENTIAL (C) TEAM-3, 2011 Page 7 of 8

Coventry University Track Locate and Assemble Risk Management Plan CUTLASS-Risk Management Plan-1.0

Version:< 1.0> Date: 31 October 2011

Risk handler: handles the risk management plan by making a note of the risks, when they occurred and what was the solution for the particular risk. He checks the action taken and provides a status report for the risk. He also tracks for the risk and make a note of its magnitude. He is also responsible for training individuals to handle the risks.

Clients participation: by keeping a up to date record of the progress, the project is discussed with the client regularly to make sure we are meeting their needs and providing them a good product. They also help us overcome the generic risk.

5. Budget As risk management plan is part of the entire project, a considerable amount is assigned for this particular task. 8% of the total project budget is assigned for the risk management team. 6. Tools and Techniques There are various types of equipments to record all the necessary informations regarding the risks. These tools are used to assess and prepare a report for the risk management team. 7. Risk Items to Manage Risks can be managed in various methods. What we can do is, make a list of the artifacts and give a link to a note stating the risks in the project. To manage the risks in the project, a considerable amount is required to manage these risks. The best method would be to make a list of the top 10 risks and submit it to the organisation so that we can make estimation for risk management. We can also list more risks if asked by the organisation. The risks that are encountered in the project are realized using various methodologies. The organization asks thr team to make a list or make a note of the risks that were mitigated, avoided or prevented. Few of them are detailed onto a report for the organisation to use.

CONFIDENTIAL

(C) TEAM-3, 2011

Page 8 of 8