Risk Plan

Version 0.1

Version History

Version	Author	Modification	Date
0.1	Leonardo	Document created and basic information added	30/03
0.2	Leoanrdo	Document updated and main identified risks added	30/03

1. Introduction

The success or failure of every and any project is depedent on many different factors such as team ability, client involvement, and costs control. Each factor that affects the project's well being, be it in a positive or negative way, is called a risk. In order to ensure the project is successful, those risks should be managed and monitored at all times, so that they bring the least amount of problems to the team. This document is responsible for identifying those possible risks and how each of them can be avoided.

2. Risk Analisys

The information of the indentified risks for this project will be displayed on a table in section 3 of this document. The informations present on the table are defined as follows:

• id: unique to every risk, it's the primary way of identifying each of them;
• Description: textual description of the risk;
• Probability: subjective measure of how likely each risk is of becoming concrete, ranges between LOW, MEDIUM and HIGH;
• Impact: subjective measure of how much the risk affects the project, ranges between LIGH, HEAVY and SEVERE;
• Action: textual description of how the risk should be tackled if it becomes concrete, or how to keep it from becoming concrete.

3. Risks List

id	Description	Probability	Impact	Action Descritption
1	Team member does not know his current reponsabilities in the project	MEDIUM	HEAVY	Ensure good communication amongst the team members
2	Team member does not have the required knowladge to fulfil his given task	HIGH	LIGHT	Ensure the rotation of knowladge amongst the team members through pair programming and dojos
3	Team member becomes unavailable for work during one or more sprints	LOW	HEAVY	Redistribute that member's tasks between the remaining members
4	Client alters one or more requirements	MEDIUM	SEVERE	Use requirements traceability to identify the ones impacted by the change, and make necessary adjustments
5	Requirements poorly prioritized	MEDIUM	HEAVY	Re-evaluate requirements' priorizations and redefine sprint backlog
6	Concrete risk is not communicated to the team	HIGH	HEAVY	Ensure good communication amongst the team members through daily meatings and open channels