Risk Management Plan

List the risks, assess their severity and probability, and try to consider measures on how the most serious / probable risks could be prevented in advance. In addition, it would be good to have a plan of how to act if the risk materializes. Attach the following section here:

Record the risks to the project in the table below and maintain them as needed. Each risk is given a unique identifier, eg RIS007, as this facilitates their handling in different situations.

RISK ID	Description	Severity	Mitigation & Notes
RIS001	Deadline risk	S1	Regular progress checks (e.g. Scrums), evaluation on what can and cannot be done within given time
RIS002	Labranet Downtime	S2	Alternative work environment
RIS003	Insecure data handling	S2	Already existing security issues are to be mapped early in order to estimate allocated time spent on fixes. Possible scope creep
RIS004	Team Member Illness	S3	Communicate with team, possible re-structuring of weekly tasks if necessary
RIS005	Miscommunication	S4	Workflow channels only to be used for work
RIS006	Scope Creep	S2	Define clear objectives and review and compare progress to given scope
RIS007	Low Team Morale	S3	Keeping up with team members, creating a way to better guide team members on their workflow

Severity descriptions

The severity class should be defined according the project

Severity class	Description	Other
S1	Total show stopper
S2		Major issue
S3	Possible issue
S4		Inconvenience
S5	No immediate affect, to be observed